Solution · MSPs & service providers

Run PAM for every customer.
From one provider team.

A service provider’s reality is one team and many customer environments. Monopam makes that a first-class model: your engineers carry one identity into every tenant they are granted, each customer keeps its own environment, and everything your team does there is approved, scoped, and audited.

  • One provider team, many tenants
  • Scoped roles with approval
  • Outbound-only link for self-hosted customers
What you get

Multi-tenant operations, without multi-tenant shortcuts.

The usual MSP workarounds are shared logins in customer systems and a spreadsheet of VPNs. Monopam replaces them with granted, time-aware access that both sides can see.

One team, every tenant

Provider engineers are granted into customer tenants by group, with an approval step in front and a central view of who holds access where. Inside the tenant they work under built-in roles.

  • Group-based grants with an approval step
  • Built-in roles: Tenant Admin, Operator, Auditor
  • Auditor is read-only, enforced on the server
  • A central provider-access view across tenants

Customers keep their own environment

Each customer tenant runs on its own database with pinned application servers. Provider sign-in into a tenant uses a signed, single-use, 60-second assertion, and the session is re-checked on every request.

  • A dedicated database per tenant
  • Pinned application servers per tenant
  • Signed, single-use, short-lived sign-in assertions
  • Re-validated on every request, not just at login

Shared accounts, never copied secrets

Rotated vault accounts the provider shares are referenced by tenants, not duplicated into them. When the password rotates on the main tenant, the tenant reads the new one on its next request.

  • Shared vault accounts stay in one place
  • Rotation propagates without copy jobs
  • No per-customer password spreadsheets
  • Session use is recorded in the tenant it happens in

Works when customers host Monopam themselves

A customer running its own Monopam links it to your provider installation over a channel the customer opens outward. No inbound port, no shared database, and the customer approves every provider user itself.

  • Outbound-only WebSocket from the customer side
  • Enrollment with a one-time code; keys are generated on the tenant and never leave it
  • Every message signed, timestamped, and single-use
  • An opt-in "sign in as service provider" entry on the tenant’s own sign-in page
How it works

From a new customer to governed operations.

01

Link the tenant

Create the customer tenant on your installation, or enroll the customer’s self-hosted Monopam with a one-time code over its outbound-only link.

02

Grant your team

Grant provider groups into the tenant with the right built-in role. Grants pass an approval step, and the customer side approves provider users on a linked installation.

03

Operate and audit

Engineers work inside the tenant under its policy and recording. You watch provider access centrally; the customer sees everything that happened in their own audit trail.

Ready to start managing
identities the right way?

Spin up a fully-loaded trial tenant in under five minutes. No credit card. No sales gate.