Documentation menu

Docs / Deployment

Choosing a deployment

kymeer runs as SaaS in a regional cluster, on-prem or air-gapped in your own environment, or as a multi-tenant service run by an MSSP.

kymeer can be deployed in three ways: as SaaS in a kymeer-run regional cluster, on-prem or air-gapped inside your own environment, or as a multi-tenant service operated by an MSSP. Whichever you choose, you buy and receive support through a certified partner.

How do the deployment options compare?

SaaS On-prem and air-gapped MSSP multi-tenant
Who runs the platform kymeer You Your MSSP
Where your data sits India, Singapore or the EU Inside your environment Where your MSSP runs the platform
Sign-in app.kymeer.com Your own installation Users invited by your MSSP
Licence Enforced on kymeer's servers Ed25519-signed, verified offline Allocated by your MSSP from its envelope

Which option suits me?

  • Choose SaaS if you want kymeer to run the platform and a regional cluster suits your residency needs.
  • Choose on-prem or air-gapped if the platform must stay inside your network, including networks with no internet path.
  • Choose an MSSP if you want a managed SOC, or want to run your own SOC on a provider's platform.

How does AI fit each option?

The AI analyst is advisory in every deployment, and every AI call is audited. It can use a local OpenAI-compatible model (such as Ollama, vLLM or llama.cpp) or a cloud provider (Anthropic, OpenAI, OpenRouter or Unoblox), and outbound AI traffic is closed unless it is turned on. On-prem installs can keep AI entirely inside the network or switch it off. See AI analyst.

Where next?

Last updated 31 October 2026Report an error in this page