Where the business stands, and where new people are coming from.
Today's standing, whatever the period below.
| Day | Signups | Audit requests | Waiting list |
|---|
The site that linked here, or a campaign's name
| Source | Signups | Audits | Waiting list | Paying |
|---|
No leads in this period.
Newest first
| Who | Kind | Source | When |
|---|
No leads in this period.
From the questions after signup
Nobody has answered in this period.
People who came to us and have not yet asked for a call or signed: the waiting list, new accounts, and the ones trying the product. Where each one stands comes from what they did. A call or a contract this console cannot see, you mark.
Who is trying it is not known right now. Everybody is still listed; accounts show as signed up.
| Who | Company | Stage | How far | Came from | Came on | Last seen |
|---|
Every customer, and the licence each one is currently on.
| Tenant | Owner | Plan | Expires | Came from |
|---|
No tenants yet. Creating one issues its free licence at the same time.
Every key ever issued, newest first. Superseded ones are kept — a signed statement outlives the row describing it.
| Tenant | Plan | Issued | Expires | State |
|---|
Nothing issued yet.
How far the people who signed up actually got. Signups do not tell us whether the product works for them; these steps do, because each one is hard to do by accident. Counted live from Mosaic's own tables — the seeded Demo workspace and the offline mock are left out of every number, or a trial that never touched a real system would read as a finished funnel.
Accounts, and whether they proved the address.
Their own workspaces, never the Demo. Each step counts a workspace once.
Sold on top of a plan rather than inside one. A pack is an entitlement, not a deployment — the code shipped with the customer's download, and the licence is what permits it to run.
What the download page shows. The files stay wherever they are served from — this holds the address, the notes, and whether anybody outside can see it yet.
| Version | Channel | Assets | Published |
|---|
Nothing yet. A release here is what the download page offers.
Every security control Mosaic has, where it lives in the code, and which SOC 2 criteria and ISO/IEC 27001:2022 Annex A controls it serves. Read from docs/SECURITY-CONTROLS.md on each deployment, so this page is wrong only when that document is.
Not a certification. Mosaic has not been audited against SOC 2 or ISO 27001, and nothing here says otherwise — this is the readiness record an audit would start from. A claim on the public site may point only at a row that reads Implemented.
The nine parts of the register, each bar to the same scale as the rest.
Every criterion any row cites, and how many of those rows are implemented. A criterion nothing cites is not shown — this is what is claimed, not what exists.
Every row in the document, in its order.
| Control | Domain | Status | SOC 2 | ISO 27001 | Evidence |
|---|
No control matches.
What Mosaic runs on, what it calls, and what data crosses each connection. Select a box to see its connections. Suppliers, regions and agreements are kept in docs/policies/supplier-register.md.
How you appear to the team.
Signing in to a console that can issue licences for anybody.
Kept in this browser.
Where you are signed in. End any you do not recognise.
Everybody who can sign in to this console. Admins issue licences, publish releases and manage the team; staff work the leads and ask the strategist.
| Person | Role | Two-factor | Last sign-in |
|---|