How it works
Each customer gets their own cell.
Each customer gets its own environment, which we call a cell, on Amazon Web Services in Dublin. The cell holds the chat application, the admin panel and every database. The AI models are called through Amazon Bedrock using EU-only routing.
From your staff to the AI and back
1. Your staff
Browser
- Sign in with Entra ID or Google
- Your own web address
2. Shared layer, Dublin
Shared between customers
- Load balancer and web firewall
- One web page fetcher: public addresses only, no customer data
3. Your cell, Dublin
Dedicated to you
- Chat app and admin panel
- Database, search index, document vectors
- Your own encryption key
- Separate code server
- Backups: hourly snapshots, nightly copies
4. Amazon Bedrock
AI models, AWS EU Regions
- EU inference profiles only
- AI prompt logging switched off
You hold the switches. We run the services.
Your admins
- Decide, per role, whether web search, the code runner and the Outlook or Gmail connector are on
- Build AI assistants and share them with staff
- Read and export the admin audit log
- Control who can sign in, through your own Entra ID or Google
TenCrown
- Runs your environment and the services behind each switch
- Sets budgets and the allowed AI models, and changes them when you ask
- Takes backups and keeps them for no more than 35 days
- Provides business-hours support
- Hands over the admin controls and trains your admins
Want the full architecture document?
We send the architecture overview, security summary and sub-processor list to your compliance lead on request.