Self-hosting Overview
Orvanta can be deployed on your own infrastructure, whether that’s a single VM, a Kubernetes cluster, or a managed container platform. Self-hosting gives you:
- Data sovereignty. Your workflow data never leaves your infrastructure.
- Custom networking. Run behind a VPN or private network.
- Compliance. Meet regulatory requirements that prohibit third-party data processors.
- Cost control. Predictable infrastructure costs for high-volume workloads.
Architecture overview
Section titled “Architecture overview”A self-hosted Orvanta deployment consists of the following components:
| Component | Description |
|---|---|
| API server | Core REST API and webhook receiver. |
| Worker pool | Executes workflow nodes (polyglot runtime). |
| Editor | Web-based node editor (served as a static SPA). |
| Database | PostgreSQL — stores workflows, scripts, audit logs, and the job queue (workers poll Postgres; no separate broker required). |
| Object storage | S3-compatible (optional): stores large job results and workspace artefacts. |
Deployment options
Section titled “Deployment options”| Option | Best for |
|---|---|
| Docker Compose | Single-machine deployments, local testing. |
| Kubernetes (Helm) | Production, high-availability deployments. (Coming soon) |
| Managed PaaS | Render, Railway, Fly.io. (Community guides coming soon) |
Next steps
Section titled “Next steps”- Requirements: hardware and software prerequisites.
- Configuration: environment variables and config options.