One deployment per client
Each client has its own deployment in its own cloud account. The account is the boundary between clients. There is no shared production system.
Security and data
Designed so that each client's content stays in that client's own environment, under that client's control.
In development The platform is in development. This page describes its design.
How clients are kept apart
Platform domain: one DNS pointer per client. No traffic, logs or content pass through it.
Client A
Own cloud account
- Studio and review
- Public pages on the client's domain
- MCP endpoint
- Database, media and logs
Client B
Own cloud account
- Studio and review
- Public pages on the client's domain
- MCP endpoint
- Database, media and logs
Nothing runs in a shared production system. At hand-off, the client takes its account with everything in it.
Your domain, your pages
Public pages are served by your own deployment, on your domain. A subdomain of the platform domain is only a DNS pointer to it: no client traffic or logs pass through the platform.
Public only by your choice
A topic becomes public only when every source behind it is marked releasable by your administrator.
A full hand-off
You can take over the account, the code, the signed releases and a full export of your data, with a checksum for every file. A signed record documents the separation.
Nothing shared between clients
Code, templates and general know-how are reused. Your content, voices, branded assets, analytics and credentials are not.
Region and providers
Each deployment runs in a region chosen with you, in the EU by default. Each AI provider is approved per client, with its processing region recorded.
Logs
Logs carry identifiers, never manual text, prompts or media.
AI providers and your content
Open item
A statement on which AI models run where, and on how your content is handled by AI providers, will appear here once it is settled.