Feature: On-Premises
Self-hosted option.
On-premises deployment option
The on-premises option meets customers where their compliance or sovereignty rules sit. Same product surface; customer infrastructure; no compromise on features.
- Self-hosted Nova. In-cluster install per customer; built for regulatory or sovereignty requirements cloud SaaS cannot meet.
- Same product surface. Identical SaaS feature set; the deployment target is the only thing that differs.
- K8s-native. Helm or OperatorHub installation; matches modern customer infrastructure expectations.
- Customer-controlled rollout. Quarterly software updates the customer chooses to apply on their own cadence.
Customer requirements
On-prem requirements are explicit. Kubernetes, PostgreSQL, object storage; all customer-managed; we provide the schemas and configuration.
- Kubernetes 1.27+. Minimum 3-node cluster for HA; per-customer cluster ownership.
- PostgreSQL 14+. Metadata store, customer-managed; we provide schema and migration scripts.
- S3-compatible storage. AWS S3, MinIO, on-prem alternatives; for audit logs and snapshots.
- Network policy. Per-cluster egress rules; supports the customer's compliance posture.
Customer operates the platform
On-prem shifts operational responsibility to the customer. Updates, backup, support; all defined; we provide guidance, customer executes.
- Updates. Customer-controlled rollout schedule; vendor provides release notes and migration guides.
- Backup and DR. Customer responsibility; we provide guidance; customer chooses tools that fit their environment.
- Support. Per-enterprise-customer dedicated TAM; quarterly architecture reviews; named escalation path.
- Local runbook. Per-customer operations runbook; supports the customer's team without leaking our internal docs.
On-prem vs SaaS trade-offs
On-prem and SaaS are different operating models. The choice is driven by compliance, not preference; most customers should choose SaaS unless rules force otherwise.
- On-prem. Data sovereignty, compliance posture, full control; more operational work falls on the customer.
- SaaS. Lower operational burden, faster updates, integrated support; some compliance regimes still preclude it.
- SaaS-default. Most customers choose SaaS; the operational-burden trade-off favours speed and simplicity.
- On-prem niche. Regulated industries (banking, healthcare, government) where data-locality requirements are not negotiable.