Auris for MSPs: one console, one tenant per customer

Auris is Altovar's identity and access product: single sign-on, adaptive multi-factor authentication and granular role-based access, built specifically for managed service providers who run many customers from one operations team. For an MSP, the pitch has two parts that are easy to blur together: one console to run everything from, and a hard boundary between what each customer can see. Auris keeps those two ideas separate, and the separation is the part worth understanding before evaluating the product.

Tenant versus organization, defined

In Auris, a tenant is the hard security and data-isolation boundary that corresponds to a customer. An organization is a grouping that exists inside a tenant — for teams, roles or departments — and it is a soft structure, not a substitute for isolation. Two organizations inside the same tenant can share visibility by design; two different tenants should never be able to see each other's data by any path. Access policies, roles and audit logs defined for one tenant do not leak into another's.

Why the boundary sits at the tenant, not the org

One tenant per customer gives an MSP a predictable blast radius: if something goes wrong inside one customer's tenant, the damage is structurally contained to that tenant rather than spreading through shared org-level plumbing. It also simplifies two error-prone MSP workflows. Access reviews get simpler, because a reviewer only has to reason about one tenant's membership at a time. Offboarding gets simpler too, since removing a customer means retiring one clearly-bounded tenant rather than untangling organization memberships that may have been shared across customers.

One console for the MSP, not one shared directory

The other half of the pitch is operational: a single console lets one operations team manage sign-on, provisioning and access across every customer tenant without switching tools. Auris documents SSO via SAML 2.0 and OIDC, SCIM-based provisioning from identity providers such as Okta and Azure AD, and relationship-based access control modeled on Google's Zanzibar approach. None of that changes the tenant boundary described above — it is how the MSP administers many isolated tenants from one place, not a way around the isolation. Full technical detail sits on the Auris product page.

Where the data sits

Altovar, headquartered in Genoa, Italy, runs Auris on dedicated servers in data centres in Germany. The "sovereign" part of the pitch describes where processing and storage happen; it is a configuration choice, not a third-party certification.

What this is, and what it isn't

This is a description of what Auris is built to do, not an independent product review. Altovar has not published third-party audits or customer win-rate figures for this MSP positioning, and none are claimed here. For MSPs evaluating identity tooling, the tenant-per-customer model is a design choice about where Auris draws its hardest line, not a guarantee that supersedes an MSP's own access controls.

What to do

• Verify tenant isolation in an actual access review, not from the marketing description — of this vendor or any other.
• Treat organizations as a convenience for structuring a customer's teams, never as a security perimeter.
• Map SSO and SCIM provisioning per tenant before onboarding a new customer, so identity sources stay separated from day one.
• Plan offboarding at the tenant level, so removing a customer retires one clean boundary instead of unwinding shared organization memberships.

Sources: Altovar — European infrastructure, real security, Auris documentation.