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, runs, scripts, and audit logs. |
| Message broker | Redis — queues runs and coordinates worker pool. |
| Object storage | S3-compatible — stores script source files and run 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.