Build on the vault instead of building one.
Compliant Swiss healthcare storage takes a year to build and a permanent team to operate. Partners embed MediVault as their storage, access and audit layer and ship their actual product instead.
- Certified partners
- 18
- Sandbox setup
- < 5 min
- Certification
- ~4 weeks
- Deprecation window
- 12 months
Embed the vault.
Don't build one from scratch.
Certification follows a working sandbox integration, not a partnership deck — most partners reach the certified tier within about four weeks of their first API call.
- 18
- Certified partners
- < 5 min
- Sandbox setup
- ~4 wks
- Typical certification
- 12 mo
- API deprecation window
Six kinds of
working relationship.
EHR & HIS vendors
Add Swiss-resident, audit-grade storage to your product without building a vault. Your customers get residency; you keep the clinical workflow.
Healthtech ISVs
Ship a compliant product in weeks. We carry the residency, encryption and audit burden while you focus on the application.
Systems integrators
Deliver MediVault deployments for hospital groups and public-sector clients, with certified engineers and shared delivery methodology.
Clinical consultancies
Advise on governance and data protection programmes with a platform that generates the evidence your recommendations require.
Infrastructure partners
Swiss hosting and network providers supporting on-premise and private-cloud deployments inside customer estates.
Research institutions
Secure, auditable storage for clinical research data, with consent tracking and defensible provenance for ethics review.
Three tiers,
no entry fee.
You start by building, not by signing. Certification follows a working integration, and commercial terms follow certification.
- Registered
- Sandbox access, documentation, community support and listing in the directory once a first integration is live. No fee, no commitment.
- Certified
- Passed conformance and joint security review. Named engineering contact, advance notice of API changes, and a public certification mark.
- Strategic
- Joint roadmap input, co-selling into Swiss providers, shared marketing and quarterly business reviews with our leadership team.
- Commercial model
- Usage-based partner pricing, billed to you or passed through to the healthcare provider. Both are supported; most partners begin with pass-through.
- Data protection roles
- The healthcare provider remains controller. You and MediVault are both processors under a three-party agreement, with responsibilities defined rather than assumed.
- API commitments
- Date-based versioning, a minimum 12-month deprecation window and written notice to every affected partner. Breaking changes never ship silently.
Who builds
alongside us.
We hold suppliers to the standards we ask of ourselves, and we name them rather than hiding them behind a generic statement about our ecosystem.
ST Comp Holdings Sdn. Bhd.
AI-engineered software · Southeast Asia
ST Comp Holdings is our engineering partner for platform and web development. They work under the same access controls, background-check requirements and confidentiality obligations as our own staff, and they hold no standing access to customer data or production key material.
Visit STCEvery sub-processor is listed publicly, with 30 days' notice of any change.
See the sub-processor register.
Start in the
sandbox.
Provision a tenant, build against the API and only then talk to us about certification. We would rather see working code than a partnership deck.
partners@medivaultzurich.site · Response within 2 business days