Partner with VSHN on OpenBao
You bring the customer relationship and secrets management expertise: strategy design, Vault-to-OpenBao migration, policy design, application integration. VSHN brings OpenBao cluster operations, HA setup, HSM integration, monitoring, upgrades, and 24/7 operations. Together you deliver a complete OpenBao solution without either side building capabilities you don't have.
Why this works
Running the OpenBao cluster around the clock is the business VSHN is in, not strategy work or migration planning. About 86% of our revenue is that recurring operation, the rest support and change requests, so your policy design and migration mandates stay yours.
- Nothing to gain from competing: our revenue depends on the cluster staying up, not on taking your strategy work
- Your customer, your relationship: VSHN operates the cluster behind it
- Self-service for your customers: instances are provisioned from a Kubernetes custom resource, the Servala portal or the Open Service Broker API, so your team's hours go into policy and integration, not into standing up the cluster
How we collaborate
Lead Partner model. For each project, one of us is the customer's single point of contact. Who leads depends on the project, agreed per engagement. The Lead Partner drives the project, handles invoicing, and owns first-level support. If you are evaluating VSHN directly as the accountable party, rather than as a delivery partner, see the sovereignty page for how VSHN handles data residency and legal accountability on its own.
Joint delivery. You handle consulting, integration, and project management. VSHN handles infrastructure operations, monitoring, backups, and SLA. Or the other way around, depending on the project. Roles are agreed per engagement, not locked into a rigid structure.
Flexible billing. Invoice the customer together or separately, agreed per project. Both models are supported: each party invoices their share directly, or one party invoices the full amount and redistributes.
Protected relationships. No undercutting. Your customer stays your customer. Existing relationships are respected on both sides, with contractual protections for both parties.
Division of labor for OpenBao
| Your role | VSHN's role |
|---|---|
| Secrets management strategy | OpenBao cluster operations |
| Vault-to-OpenBao migration | HA setup and failover |
| Policy design | HSM integration |
| Application integration | Monitoring, alerting, and 24/7 incident response |
| Project management and customer relationship | Upgrades and SLA |
Keep the client relationship. Hand over the secrets store.
You designed the policies and connected the applications to OpenBao. The cluster itself stayed with you: unsealing, upgrades, and the call when applications cannot fetch their secrets.
The Lead Partner model covers this: you keep the client and the invoice, VSHN takes the cluster and the pager, under a contract between the two of us.
We operate what we know. OpenBao has to be set up to the VSHN standard before we can run it around the clock, because the engineer who answers at 03:00 has to know the system. An existing cluster is brought to that standard first.
Partners delivering OpenBao
bespinian. Cloud-native consulting firm specializing in bespoke solutions. Delivers secrets management strategy and Vault-to-OpenBao migrations on VSHN-operated infrastructure.
See all VSHN partners at servala.com/partners.
Become a partner
Interested in delivering OpenBao secrets management together? Let's explore how we complement each other.
Book a partnership discovery call or start a partnership conversation.