Requirements

Software prerequisites

Dependency	Minimum version	Notes
Docker	24.x	Required for all deployment methods.
Docker Compose	2.x	Required for single-machine deployments.
PostgreSQL	15.x	Primary datastore and job queue. Can be an external managed instance (RDS, Cloud SQL, etc.). Bootstrapping needs one privileged setup step; the running application does not need a superuser.
S3-compatible storage	—	Optional — for large job results/artefacts (AWS S3, MinIO, Cloudflare R2, or equivalent).

Minimum hardware

Development / testing

Resource	Minimum
CPU	2 cores
RAM	4 GB
Disk	20 GB

Production (single-machine)

Resource	Recommended
CPU	4 cores
RAM	8 GB
Disk	50 GB SSD

Production (Kubernetes)

Cluster sizing depends on workflow volume and concurrency requirements. As a starting point:

• API server: 2 × (1 CPU, 512 MB RAM)
• Worker pool: scale horizontally based on concurrent run targets; each worker uses ~256 MB RAM at idle.
• PostgreSQL: managed instance recommended (RDS, Cloud SQL); also serves as the job queue, so size it for your concurrency.

Networking

• The API server must be reachable from your users’ browsers and from worker nodes.
• Workers need outbound internet access if workflows call external APIs.
• All internal component communication can stay on a private network.

Outbound access to the licence service (required)

A licensed self-hosted instance must be able to reach https://license.orvanta.cloud over HTTPS on port 443. This is not optional and there is no offline licence key: every validation is a live request to that host, and the instance revalidates every 6 hours. Allow it through your egress firewall or proxy before you deploy.

Orvanta does not shut down when it cannot reach the service. It escalates instead, measured from the first failed validation:

Elapsed	What happens
0 h	Failure logged; a support signal is emitted locally.
24 h	In-product warning to instance admins.
48 h	Every instance admin is emailed.
72 h	The instance degrades to read-only and falls back to trial limits.

Read-only means running and scheduled flows continue to completion and everything stays readable, but new deploys, edits and resource changes are rejected with 503. Logging in, and the licence actions that get you back out (re-validate, test a key, renew a key), keep working. The instance recovers on the next successful validation — degradation is lifted automatically, with no restart.

Orvanta cannot run fully air-gapped. Individual features are built to work without outbound access — bundled editor assets, seeded workspace templates, and the Orvanta Hub toggle — but licence validation is the one connection you cannot switch off. If you have a genuinely isolated network, talk to us before you buy rather than after.

Next steps

• Configuration: Environment variables and secrets.
• Running without a Postgres superuser: Required roles, grants, and extensions on managed PostgreSQL.