Sign in
Running Monofor as an MSP: the business model

What changed

Every content update is versioned. Select a version to compare it with the one before.

Version 1 → 2

Small fix
2 lessons updated

Small corrections such as typos or translation fixes. Learners are not notified.

Three ways to serve a customer
A managed service provider (MSP) runs Monofor for several customers at once. Each customer is a **tenant**: its own users, policies, vault and audit trail. With Monopam v2026.09 there are three ways to give a customer its tenant, and the choice shapes what you sell. ### Hosted, shared database The tenant lives in your installation and keeps its data in the installation database, next to other tenants. It is the quickest to open and fits small customers. ### Hosted, dedicated database The tenant still runs on your installation, but its data is in a database of its own. Choose it when the customer needs its own backup and restore, placement or maintenance window. The choice is made when the tenant is created and cannot be changed later. ### Remote tenant The customer runs Monopam in its own environment and connects it to you. The connection is opened outward by the customer; you never connect in. The customer keeps its database, its keys and a switch that cuts your access at any moment. It fits customers that will not hand over their data. ### What stays the same In all three, your staff work in a customer tenant only through an access you grant from your main tenant, with a role and an optional end date, and every entry is audited on both sides. ::diagram msp-three-tenant-models > Tip: Decide the model per customer early. A hosted tenant cannot be moved between the shared database and a dedicated one afterwards.
What is counted
Billing follows usage, so know what the products count. ### Monopam Every 15 minutes Monopam counts each tenant's modules and sends the numbers to that tenant's Monosign: - **Concurrent users**: the highest number of different people online at the same time during the day (UTC). One person is one user, however many sessions they open. A short spike counts for the whole day. Vendor users count too. - Vault items, certificates, EPM workstations and servers (only agents seen in the last 30 days), AD-bridged servers, machine identities, database resources, vendor users, and AI agents that used the MCP server in the last 30 days. Only numbers are sent: no names, no contents, no personal data. ### Monosync Monosync reports its number of active integrations every 15 minutes. ### Monosign From v2026.11 Monosign lists its own modules with a count of enabled users (for MFA: enabled users with a verified MFA method). In v2026.10 these rows show the licensed quantity only. ### From daily to monthly The monthly figure adds up, for each tenant and module, **the highest day of the month**. Two consequences: - One busy day sets the month for that module. - Customers peak at different times, so the sum of their peaks is not the number of people online at the same moment. ::diagram msp-usage-to-month > Warning: A period without a report stays unknown. It is shown as unknown, not as zero, and it is not filled in later.