Multi-tenant backup for service providers
One Osiris installation can serve many isolated tenants: an organization is a tenant, PostgreSQL row-level security keeps every tenant's data separated at the database level, and the Service Provider edition adds delegated tenant administrators and per-tenant reporting on top of that isolation, so a provider runs backup for many clients from one console without one client ever seeing another's data.
How tenants get populated
For a Microsoft 365 tenant, users, mailboxes and OneDrives come in automatically through Entra ID directory sync, with the protected scope controlled per tenant: everyone, a specific group, or an exclusion list. IMAP-only tenants are added by a manual mailbox list or CSV import instead.
Running it for clients
Delegated tenant administrators handle their own client day to day; a Provider Admin can act across tenants when needed, always as logged impersonation. A REST API with per-tenant API keys and scopes (plus, in the Service Provider edition, a provider-wide key for cross-tenant queries) lets an RMM, PSA or ticketing system pull backup/restore/verify status, jobs, storage, archive evidence and a clean per-tenant user/mailbox directory for billing, instead of someone checking a dashboard by hand. White-labelling for this edition is planned, not built yet. See theroadmap.
Frequently asked
Can one Osiris installation serve multiple clients?
Yes, under the Service Provider edition. Community and Business are single-tenant (one organization); Service Provider adds multiple tenants, tenant management, tenant reporting and a provider-wide API key, with no limit on how many tenants or mailboxes.
Is tenant data actually isolated, or just filtered in the interface?
Isolation is enforced by PostgreSQL row-level security at the database level, per tenant, not only by the application hiding rows in the UI. Encryption keys are also separate per organization, which limits the impact of a bug in the application layer rather than making cross-tenant exposure structurally impossible.
How do provider technicians restore data for a client without direct database access?
Through delegated tenant administration: a Provider Admin can act on a tenant's behalf, and every such action is impersonation, logged to the tamper-evident, hash-chained audit log (who, when, for whom, from which IP), the same rule that applies to any other restore on someone else's behalf.