Your own private server single-tenant
Your own deployment, your own database, your own filesystem. No shared database, no pooling of data, and no other customer's agents on the same box.
Security & ownership
Your server. Your data. Nobody else on the machine.
Lucy runs on your own server, with your own database. One deployment serves one customer, so there is no other business alongside you and nobody else can see your data.
For the technical reader: this is single-tenant by design. There is no organisation ID anywhere in the database, because there is only ever one of you on the machine. Tenancy is the deployment boundary, not a WHERE clause.
How it holds up
Built to be trusted with your data
Invite-only access
Public sign-up is switched off where accounts are actually created, not merely hidden on the page. Access is by invite code, limited in how often it can be tried, with modern password protection.
One agent cannot read another's private notes
An agent never receives another agent's private memory. Enforced in code, and covered by an automated test that fails the build if it ever leaks.
You choose what each one can touch per-agent allowlists
Each agent is given a list of the tools it may use, enforced at the filesystem level. A tool that is not on its list is invisible to it, so there is no instruction for it to ignore.
Logins kept encrypted
Connection logins and bot tokens are encrypted while stored, and handed only to the processes allowed to use them. They are never written into the connection files themselves.
New connections are checked before they install
Every connection is verified as it is imported. One that is unsigned or has been tampered with is refused, and nothing is written to disk. Attempts to escape the target folder from inside the archive are refused too.
Audit log
Logins, taking on and letting go of agents, completed messages, token changes, errors and memory writes are all logged by ID and action, never by content.
No markup on AI usage
Models are called through your own account with the AI provider, under their terms, so you pay them directly for what you use. We do not train on your data, and your conversations and memory never leave your deployment.
Runs alongside what you already host
Docker, non-root, on a single local port behind your own reverse proxy. It sits happily beside whatever else is on your server, with no port or domain conflicts.
Cyber EssentialsCertified. Verify →
UK & EU GDPRData protection
EU data residencyHosted in your region
Microsoft PartnerPartner programme
Straight talk
What we don't claim
We are pre-launch and single-operator. Cyber Essentials is certified, and verifiable above. We are not SOC 2, ISO or HIPAA audited, so you will not see those badges here. When we hold them, we will say so, with the paperwork to back it.