What the demo can't do — and why that protects everyone

The four things that are off

Uploads. Every upload button is present and, when pressed, says uploads are off in the demo. A demo that accepted files would be storing strangers' files on our servers within a day.

Sending. Emails and WhatsApp messages are composed and shown to you, and stop there. Otherwise the demo would be a way to send anything to anyone with our name on it.

AI reading of IDs. The feature that reads an uploaded ID and proposes field values uses a paid service. In your own workspace it uses your own key; the demo has none.

Export. The demo data is ours and you can see all of it on screen; there is no reason to hand out archives of it, and an export button on a public demo is a load test waiting to happen.

What is private about it

Each visitor gets a fresh copy of the demo database — your changes exist only in your copy, and nobody else's appear in it. The copy is put away after about six hours, or sooner if it grows very large. No account is created, so there is nothing about you to keep. Try the demo walks through the lifecycle.

Judging the real thing from it

Everything else is live: raise and void invoices, move tenants, change the rota, rearrange pages, switch roles with View as, break things. The four switched-off actions are the ones that reach outside the workspace, and they are the least interesting part of a building's month anyway.