Platform layer — Ozone
Ozone — the multi-tenant platform behind every Protium service.
Tenant isolation, credential management, API-first, MCP-ready. The foundation our certified iSHARE trust services run on — and the foundation you can build a regulated multi-tenant SaaS on.
What Ozone delivers
Multi-tenant by design
Complete tenant isolation. No cross-contamination, ever.
Identity & credential management
Built-in credential issuance, keystore management, identity context per tenant.
Service registry & configuration
Plug-and-play service onboarding, configuration per tenant, runtime governance.
API-first architecture
Ready for MCP, OID4VCI, iSHARE v3 out of the box. Webhooks, REST, event streams.
Real-time communication layer
Event-driven, production-grade real-time messaging between tenants and services.
Frontend utilities
Reusable UI layers for tenant administration, credential UX, consent flows.
Use case patterns
Regulated multi-tenant SaaS
When each customer needs isolated data, configurable governance, and credential-based access — Ozone is the foundation.
Ecosystem applications
When multiple participants need to share data under governed access — Ozone provides the tenant model, the credential layer and the real-time backbone.
AI-enabled data services
When AI agents need to act on data under identity, rights and audit — Ozone's API surface and credential management make this the default deployment target.
For platform engineering teams
API surface
REST and event-driven. OID4VCI, iSHARE v3 and MCP-compatible interfaces out of the box.
Deployment model
Managed by Protium in EU sovereign cloud, or licensed for deployment in your environment.
Isolation guarantees
Tenant-level isolation in data, credentials and configuration. Built in, not bolted on.
Observability
Telemetry per tenant. Audit logs per credential operation. Production-grade SLA monitoring.
Licensing
Ozone is licensable per tenant for partners and customers who want to deploy it themselves or build their own SaaS on top of it. Pricing is discussed under NDA in a licensing conversation.
Licensing inquiry →