A dedicated instance.
Operated by us.
Your own isolated deployment — separate instance, separate database, your choice of region — but we handle the patching, monitoring and backups so your team doesn't have to.
Co-hosted at a glance
- Dedicated instance and database, isolated from every other customer
- Your choice of data region to satisfy residency requirements
- We patch, monitor and back up — no operations burden on your team
- Custom modules built to spec into your instance
- Direct engineering escalation rather than a shared support queue
- Annual platform fee rather than per-seat pricing
What you get out of it
Every deployment model runs the same platform. What differs is who operates it and where the data sits.
- Isolation without the operations — the middle ground most partners want
- Performance you don't share — no noisy-neighbour risk
- Your branding throughout, with no Zephyr footprint your customers can see
- Scale without re-architecting — the instance grows with you
Co-hosted questions
How is this different from hosted?
Hosted puts you on shared infrastructure under your brand, which is faster and cheaper to start. Co-hosted gives you a dedicated instance and database with your own region and performance envelope, while we still run it.
Can we move between models later?
Yes. Partners commonly start hosted to prove the market, move to co-hosted as volume grows, and some go self-managed later. Migration between our own models is straightforward because it's the same platform.
Who has access to our instance?
Our engineering team for operations, under audit logging. Your data is not accessible to other customers, and we don't use it for anything beyond running your service.
What's the SLA?
The same availability commitment as our own platform, with dedicated capacity behind it. See the SLA.
Talk it through with an engineer
Bring your infrastructure constraints and your current licence terms. We'll tell you honestly which model fits.