For MSPs & partners
Run every client’s program from one place
Managed-service providers and consultancies use Keel to stand up and operate compliance programs for many clients at once - each in its own isolated workspace, all visible from a single console. Each client workspace on a partner or Enterprise plan, or carrying the Trust Center Pro add-on, white-labels its trust center to read as your brand, and you hand off audit-ready deliverables as your own.
Worth being plain about what that means, because it is the whole shape of the thing: each client is a separate workspace, not a sub-account inside yours. A book of clients is that many distinct programs, each one complete on its own. How the separation works →
Every client workspace is a full Keel program - controls, risks, policies, evidence, and a trust center - that you manage from the console.
Multi-client console
Every client, at a glance
The client console rolls up each workspace you manage - coverage, open risks, open tasks, and vendors - so you always know where every engagement stands, and can drop into any of them in one click.
-
One cross-client console
See readiness, open risks, open tasks, and vendors for every client workspace in a single table - averages up top, per-client rows below.
-
One-click switch
Jump straight into any client to work in their program, then hop back. No re-login, no separate accounts to juggle.
-
Spin up a client in seconds
Create a fresh, isolated workspace for a new client from the console. You own it, run guided setup, and it appears in your list right away.
-
Isolated by default
Every client’s data lives in its own tenant, separated at the database level by row-level security. One client can never see another’s data.
The console is included on the MSP / Partner plan (and Enterprise). Client workspaces you create start on the free plan and can be upgraded like any other.
White-label
Deliver it as your own
-
Custom trust-center domains (coming soon)
Soon you’ll be able to publish each client’s trust center on their own domain (trust.theirbrand.com). Today a client workspace entitled to white-label reads as your brand, at a Keel address.
-
Remove Keel branding
White-label the trust center so it reads as your client (or your practice), not Keel. Included on the MSP / Partner and Enterprise plans, or via the Trust Center Pro add-on.
-
Branded reports & policies
Every readiness report and policy PDF carries the client’s name and logo - deliverables you can hand off as your own work product.
A real program per client
Not a dashboard - a working GRC platform
Each client workspace has the complete toolkit, so you’re delivering an actual compliance program, not a status page.
- Controls crosswalked across SOC 2, ISO 27001, HIPAA, PCI DSS, NIST CSF and more
- Risk register with likelihood × impact scoring and treatments
- Framework-mapped policy templates with branded PDF export
- Vendor risk with review cadences and questionnaire portals
- Employee directory sync + periodic access reviews
- Security-awareness training with certificate evidence
- Readiness reports and a public, branded trust center
How it works
From zero to managing clients
Get on the MSP / Partner plan
Unlocks the console and unlimited client workspaces at partner pricing. White-label is entitled per client workspace, not by your own plan (custom domains coming soon).
Add a client
Create an isolated workspace from the console and run the guided setup.
Build the program
Apply starter controls, seed risks, add vendors, and invite the client’s team.
Prove it
Publish the client’s trust center - white-labeled once that workspace is on a partner or Enterprise plan, or carries Trust Center Pro - and hand off readiness reports.
Separate tenancy
One client, one workspace - not sub-accounts
Keel has no sub-account model, and that is the detail to check before you put a book of clients into any platform. Adding a client from the console stands up a new workspace: its own tenant in the database, its own members and roles, its own plan, its own trust center. So what you operate is that many separate programs, each one whole - not one program with the clients held apart by a filter.
-
A tenant, not a folder
Adding a client from the console creates a whole new workspace in the database, with its own controls, risks, policies, evidence, vendors and people. There is no parent record it hangs off - the only thing tying it to you is your own membership of it.
-
Separated in Postgres, not by a query filter
Every tenant table has row-level security forced on, and each read and write runs inside one client’s tenant context. A query that arrives without a tenant context matches no rows at all, so the separation does not rest on the application remembering to add a condition.
-
Its own people, its own roles
Members, invitations, roles and the seat allowance belong to a single workspace. There is no all-clients role: someone reaches a client’s program by being a member of that client’s workspace, and of no other.
-
Its own evidence, served through Keel
Uploaded files are keyed to the workspace that owns them, and there are no public file URLs. Every download goes through the app, which re-checks ownership under row-level security before a byte is sent.
-
Its own plan and trust center
Each client workspace carries its own plan, its own seats and its own trust center at its own address. Upgrading one client, or publishing one client’s trust center, changes nothing for any of the others.
-
Handover is a membership change
When an engagement ends, make the client an owner of their workspace and take yourself out of it. Their program stays exactly where it is, entire, because it was never sitting inside yours.
One thing it does not mean: you are a member of every client workspace you manage - that is what makes the console work at all. The separation is between your clients, and between each client and everyone outside it. It is not a wall between you and the client whose program you are running for them.
Partner pricing
Let’s tailor a plan to your book
The MSP / Partner plan is priced per client workspace, not per seat - so what you pay scales with your book, not your headcount. The unit is the separate client workspace described above, each one a program in its own right. Tell us how many clients you run and we’ll put together partner pricing that fits how you work.
Framework names (SOC 2, ISO 27001, HIPAA, PCI DSS, etc.) are referenced factually. Keel is not affiliated with or endorsed by their respective owners.