Subtwin twins are free across your entire fleet — 1 client or 50, the price is the same (zero). You can run them yourself (DIY MSP) or apply to the Subtwin Partner program and receive customer referrals. Pick the track that fits how you already work.
Same product. Same free per-client economics. Different relationship with Subtwin. Skim the comparison; the rest of this page goes deeper on each track.
You operate. No application. No directory listing.
You're listed publicly. Subtwin routes customer leads to you.
Subtwin onboards your partner tenant; you onboard each client using our scripts and runbooks. We never market to MSP-managed tenants without your invitation.
Every client tenant gets its own container, secrets, and audit. Run 50 twins and each is its own blast radius. No shared multi-tenant database that touches any client's credentials.
Sam at one client, Robin at the next, Alex at a third. The twin's display name, avatar and UPN are whatever you and the client choose. You can present it as your own service.
Every action lands in the client's own M365 audit log. Their compliance team reviews their log, the way they already do. You aren't asked to forward a third-party "AI activity" report.
Twins are free across your entire fleet — 1 client or 50, the price is zero. Bake the value into your client MRR; we don't take a cut.
~15 minutes at the client + ~5 minutes on our side. No portal projects. No client-side install. Your techs deploy a new twin in a coffee break.
The twin handles the well-defined work. Anything genuinely unusual escalates to your team — by design. You stay the relationship; the twin handles the toil.
Applies to both DIY MSP and Subtwin Partner tracks. We get this question on every MSP call; here's the actual posture so your E&O / cyber-liability conversations don't stall.
Cyber liability: $5M aggregate (rep. carrier on file)
E&O: $3M per claim / $5M aggregate
Notice of incident: 24 hours from detection
Survival: through twin offboarding window
Every confirmed twin action emits a webhook with a normalized payload (requester, client, action, status, audit link). Your PSA gets a ticket; your RMM gets a record; your billing reconciles. Applies to both tracks.
Outbound webhook per action. JSON payload includes requester UPN, client tenant ID, action summary, M365 audit Operation ID, and confirmation timestamp. Wire it into any PSA that accepts a webhook.
ConnectWise Manage, Autotask, HaloPSA, NinjaOne — native connectors with ticket-create, status-sync, and SLA tagging. Design partners welcome; we ship in the order of demand.
Beta · 2026
For partners using Granular Delegated Admin Privileges, the twin provisions inside the client tenant (not your partner tenant) — preserving the client's audit posture and not exposing your other clients to its scope.
A typical MSP tech spends 6–10 minutes on a license/group/password ticket. A twin handles those in 5 seconds. On a typical 200-seat client, that's a few hours a week of high-frequency toil you stop billing your techs against.
Plug in your own numbers during the walkthrough — these are placeholders for a typical 200-seat client.
| Request type | Volume | Handled by twin |
|---|---|---|
| License grants / changes | ~12 | Most |
| Group add / remove | ~18 | Most |
| Password / MFA resets | ~14 | Most |
| Distribution list / shared mailbox | ~6 | Most |
| Directory lookups | ~25 | All |
| Novel / unclear | ~5 | Escalate |
Numbers are placeholders, not measurements. We'll size against your real fleet during the walkthrough.
We provide a kit — pre-written client email, employee FAQ, compliance one-pager, opt-out language — so you can introduce the twin to your clients without reinventing the wording each time.
Plain-English explainer covering what the twin is, what it can and can't do, who has access, and where the audit log lives. Branded with your MSP, not ours.
For the client's IT comms — for their end users opening Teams and wondering who Sam is. Confirmation gate explained, opt-out path documented.
For the client's compliance officer / CISO. Audit posture, sub-processor list, data flow diagram, BAA availability.
One pane of glass across your fleet: per-tenant status, action volume per twin, escalations pending, credentials rotating, version drift. Currently in beta; gated on MSP partner program.
Rename a client's twin (Sam → Robin) without breaking history. App secrets and tokens rotate on a schedule — one operator command, zero client involvement.
Enable/disable tools per client. Some clients want license + group only; some want the full catalog. Some want compliance-restricted scopes.
One command tears the container down, revokes tokens, and disables the twin user. We retain nothing.
peasyCloud regions for data-residency clients. EU container for EU clients, US for US.
A real human, a real Slack channel, an SLA that maps to your client SLAs. Direct line to an engineer for Sev-1, 24/7.
30 minutes. We'll size your fleet, walk the onboarding script, show the audit shape your clients will see, and hand you the MSA + insurance certificate. Choose DIY or apply to be a Subtwin Partner during the call.