Deployment options overview

Orkena ships as a single Helm chart, with feature parity across all three deployment modes. Two of them are available today; the managed tier is on the roadmap. The choice is about where your data has to stay.

Customer VPC#

The Helm chart installs into your Kubernetes, using your Postgres, your KMS, your network. Orkena provides the software; you run the operations. Best when your security review requires data to stay inside your boundary while you still get managed delivery.

• Install timeline: typically 1–2 days after your environment is provisioned
• Operations: yours; Orkena provides software-level support
• No sub-processors — Orkena operates nothing on your behalf

Managed tier, region-pinned (roadmap, 2027)#

Orkena operates the infrastructure; you consume the API. Data at rest never leaves the region you select. Design partners first — GA follows the first VPC deployments and SOC 2 Type II. Best when your team wants zero operations and the region option satisfies your data-residency rules.

• Availability: roadmap (2027+); design partners first
• Sub-processors: cloud infrastructure provider, per the trust centre
• Model providers: bring-your-own-key

Air-gapped#

The same Helm chart, with no outbound connectivity required, ever. Local models for embeddings and classifiers ship in the bundle. Best for public-sector engagements and any environment with a hard network boundary. See Air-gap deployment for the install walkthrough.

• Install timeline: 1–2 days; offline bundle transferred by your process
• No auto-updates, no telemetry back to Orkena, no external model providers unless you host them locally
• Verification story unchanged: verify.py was designed for exactly this — dependency-free and offline-first

How to choose#

If your requirement is…	Choose
Fastest path to production today, data stays in your boundary	Customer VPC
No outbound connectivity, sovereign operations	Air-gapped
Zero operations, region pinning is enough	Managed tier (roadmap, 2027)

Pricing is an annual platform licence scaled by deployment mode and governed volume. All public-sector engagements begin with a scoping conversation.