Feature: On-Premises
Self-hosted option.
On-premises deployment option
Self-hosted Nova for customers with regulatory or sovereignty requirements that cloud SaaS cannot meet.
Same product surface as the SaaS offering; deployed in customer infrastructure. K8s-native; standard Helm or OperatorHub installation.
Available on enterprise tier. Quarterly software updates; customer-controlled rollout.
Customer requirements
Kubernetes 1.27+ (any vendor). Minimum 3-node cluster for HA.
PostgreSQL 14+ for metadata storage. Customer-managed; we provide schema.
Object storage S3-compatible: AWS S3, MinIO, on-prem alternatives. For audit logs and snapshots.
Customer operates the platform
Updates: customer applies new versions on their schedule. Vendor provides release notes and migration guides.
Backup and disaster recovery: customer responsibility. We provide guidance; customer chooses tools.
Support: dedicated TAM for enterprise customers; quarterly architecture reviews.
On-prem vs SaaS trade-offs
On-prem: data sovereignty, compliance posture, full control. More operational work.
SaaS: lower operational burden, faster updates, integrated support. Some compliance limits.
Most customers choose SaaS. On-prem is for specific regulatory or data-locality requirements.