Infrastructure Requirements
The Vault runs on Kubernetes for on-premises and hybrid deployments. This page outlines, at a high level, the infrastructure areas you should plan for.
SaaS customers — none of this applies to you. Skip to SaaS Onboarding.
Areas to Plan For
An on-premises or hybrid deployment depends on the following:
- Kubernetes cluster — a conformant cluster with dynamic persistent storage
- PostgreSQL — a relational database (one logical database per service)
- Message broker — RabbitMQ for inter-service events
- Cache — Redis, used by the policy engine
- KMS — AWS KMS, GCP KMS, or HashiCorp Vault for key-share encryption at rest
- Networking — an ingress controller, TLS, DNS, and outbound access to your blockchain nodes
- Mobile devices — recent iOS/Android devices with hardware-backed secure elements for mobile signers
Detailed infrastructure requirements — exact versions, node and resource sizing, storage and networking configuration, KMS setup, and deployment tooling — are provided to your team on request as part of the on-premises onboarding package. Contact us to receive the current requirements for your target environment and scale.
Next Steps
- On-Premises Installation — deployment overview and what’s in the onboarding package
- SaaS Onboarding — getting started without infrastructure
- Mobile App Setup — enrolling mobile signer devices