Skip to main content
KaireonAI is a proprietary, commercially licensed platform. There are three ways to run it:

Cloud

Hosted SaaS — the default. We run KaireonAI for you on shared infrastructure. Sign up, pick a plan by decision volume, and go live — no servers to maintain. See Licensing & Plans.

Dedicated

Private cloud, single-tenant. An isolated instance we operate for you, with dedicated compute, storage, and networking. For teams with data-isolation or compliance requirements. Contact sales.

Enterprise on-prem

You run it, under a commercial license. Deploy inside your own VPC or air-gapped cluster. Available on the Enterprise plan only — not free, not open, not self-serve. Contact sales.
The operational guides in this section (Docker Compose, Kubernetes / Helm, cloud infrastructure) apply to Enterprise on-prem deployments and internal development. Image and source access is provisioned as part of an Enterprise agreement. Most customers run on the fully hosted Cloud plan and never touch these.

Enterprise on-prem topologies

Enterprise licensees can run KaireonAI in whichever topology fits their infrastructure:

Local / evaluation

Run on a workstation with PostgreSQL and optional Redis. For licensed development and evaluation.

Managed cloud (App Runner)

Deploy to AWS App Runner with Supabase (PostgreSQL) and Upstash (Redis).

Kubernetes (Helm)

Deploy to any Kubernetes cluster using the provided Helm chart.

Comparison of on-prem topologies

Docker Images

KaireonAI builds two Docker images: The API Dockerfile lives in the platform/ directory, so build from there. You push images to Amazon ECR and tag them with the git SHA plus latest:

Environment Variables

All deployment methods use the same core environment variables. The platform validates these at startup and will fail fast if required values are missing in production.

Core (Required)

Security (Required in Production)

Authentication

Infrastructure

Observability

Security Headers

Decisioning Tuning

The following decisioning defaults are currently compiled-in constants rather than environment variables. To change one, edit the corresponding constant in the circuit-breaker module or the decision-flow engine module and redeploy:

Tenant Configuration

Worker

Next Steps

Local Development

Get started with a local PostgreSQL and Redis setup.

Cloud Deployment

Deploy to AWS App Runner with Supabase and Upstash.