Skip to main content

Cloud, Dedicated Tenancy & Self-Host

Most teams use Kadaikodi as a managed cloud service — there's nothing to deploy beyond the storefront and integrations you build on the headless API. For teams with stricter isolation or compliance needs, Kadaikodi offers dedicated tenancy and self-host on Enterprise plans.

Managed cloud (SaaS)​

The default and fastest path. Kadaikodi is run for you as a managed cloud service — sign up and start building against the hosted API.

  • No infrastructure to manage — the commerce backend, storage, and API are operated for you
  • Multi-tenant by default — every merchant, offering, order, and review is workspace-scoped
  • Isolated environments — staging and production are fully separated, each with its own isolated configuration and secrets
  • Encrypted — TLS in transit; stored data and secrets encrypted at rest
  • Global edge — static assets are served from a global CDN

You integrate by:

  1. Authenticating with OAuth (device-code for apps and CLIs; client credentials for service-to-service)
  2. Driving cart, catalog, order, merchant, and fulfillment operations over GraphQL
  3. Building your storefront, kiosk, or agent on top

Dedicated tenancy​

For teams that need stronger isolation, Enterprise plans offer a dedicated tenant — strict per-tenant boundaries while still running on the managed platform. This suits regulated marketplaces and large catalogs.

Self-host​

Where policy or jurisdiction requires it, Enterprise customers can self-host Kadaikodi in their own environment. A self-hosted install runs the same container images and exposes the same GraphQL API as the managed service, so storefronts and integrations built against the hosted API work unchanged.

Self-host engagements are scoped with our team: we supply the images, the configuration and secret requirements, the database and object-storage prerequisites, and the upgrade process for your environment.

Security & governance (all models)​

  • Role-based access control — every operation is permission-checked against the caller's role before it runs
  • OIDC SSO with OAuth device-code flows for apps and CLIs
  • Encrypted secrets — sensitive configuration is flagged and protected
  • End-to-end audit — every action recorded with actor, target, and result
  • Quota enforcement at the mutation layer

Getting started​

For most teams, "deployment" means building on the managed API — no infrastructure required.