Partner with VSHN on Managed MariaDB
You bring the customer relationship and database expertise: migration from MySQL or Oracle, query optimization, application integration. VSHN brings 24/7 managed operations, Swiss data residency, and a 99.99% SLA. Together you deliver a complete managed MariaDB solution without either side building capabilities you don't have.
Why this works
VSHN's business is the recurring operation, not the migration project: about 86% of VSHN's revenue is that recurring operation, and the rest is support and change requests, not consulting mandates we'd want to take from you.
- No reason to compete: there is no revenue model under which winning your migration work would pay off for us
- Your customer stays yours: VSHN operates the database behind the relationship you keep
- 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 spends its hours on the database's content rather than on provisioning it
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 Managed MariaDB
| Your role | VSHN's role |
|---|---|
| Database architecture and design | MariaDB instance provisioning and operations |
| Migration from MySQL or Oracle | High availability and replication management |
| Query optimization and tuning | Backup, PITR, and disaster recovery |
| Application integration and testing | Monitoring, alerting, and 24/7 incident response |
| Project management and customer relationship | Upgrades and security patches |
Keep the client relationship. Hand over the database.
Some firms never wanted the database. You hold the application contract with a cantonal office, a federal agency or an enterprise client, and MariaDB came with it. Nobody on your team was hired to be on call for it, and the hours it takes come out of the application work the contract pays for.
In that case the Lead Partner model runs in one direction. You stay the client's single point of contact and invoice them. VSHN operates the database behind you under a written service agreement with you, with an SLA of up to 99.99% and 24/7 incident response, so the service level in your client contract has one behind it.
Two conditions apply:
- We operate what we know. MariaDB 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 setup is brought to that standard first.
- Where the data runs and who may access it is written into the agreement. A public-sector client has to document exactly that. The sovereignty assessment covers it, including the Switzerland-only support option.
See all VSHN partners at servala.com/partners.
Become a partner
Interested in delivering managed MariaDB together? Let's explore how we complement each other.
Book a partnership discovery call or start a partnership conversation.