Built so you can hand work to AI — and still know who did what
A plain-language overview of how Zeze is built. We say what exists today and what is still on the roadmap.
One workspace, one server
- Each organization runs on its own messaging server and gateway, with a separate database, media store, search index and AI audit log.
- Our control plane handles accounts, workspaces and invitations. It does not store message content.
- Tokens are only valid on the workspace that issued them.
Where your data lives
- Managed workspaces are hosted on AWS in Singapore by default.
- Additional regions (such as the EU, US and Japan) are planned for Business and above, at no extra charge once available.
- Enterprise: dedicated instance in the region you choose, or operated in your own cloud account.
- Private deployment: run the full stack in your own cloud or data center.
Sign-in and accounts
- Passwordless sign-in with one-time email codes; each workspace session is exchanged for a 60-second single-use token.
- Deactivating a member takes effect immediately on every device.
- Google and Microsoft sign-in, SAML and SCIM are on the roadmap.
AI governance
- Every AI action is decided on the server as Auto, Ask me or Never; admins set minimums individuals can’t lower.
- Messages to other companies, outside links and large groups always need a human’s approval.
- Each AI is a separate device that can be paused or revoked instantly, with a complete audit trail.
- Your AI won’t answer above a colleague’s clearance: when it replies on your behalf, the server checks what it recently read against each recipient’s own permissions (reviews, approval amounts, files, chats) and holds anything they couldn’t see for your approval.
- Defenses against prompt injection and data exfiltration are documented on the AI access page.
Working with other companies
- Two workspaces connect only after both admins agree; either side can end it.
- Each side chooses exactly which members the other can see. Members not shared can’t be found or messaged.
- Conversations with outside members carry a visible banner; servers only federate with connected organizations.
Calls and meetings
- Meeting access tokens are issued by your workspace’s gateway only to members of the conversation, and expire after 10 minutes.
- Host actions (mute, remove, lock, end) are verified by the server, not the client.
- People outside the conversation must knock and be admitted by the host.
A note on encryption
Traffic between apps and servers is encrypted with TLS.
Messages are not end-to-end encrypted. This is deliberate: search, audit logs and server-side AI rules need to read messages on your workspace’s own server. If you need full control over that server, choose a dedicated instance or private deployment.
Compliance status
We do not yet hold SOC 2 or ISO 27001 certification. Preparation is on our roadmap; we will publish status here rather than make claims early.
We design for Singapore’s PDPA and the GDPR. Data processing terms will be published with our legal documents.
Report a vulnerability
Found a security issue? Email security@zeze.com. Please give us a reasonable time to fix it before disclosing publicly.