Your data, your server, your rules.
This page is written for whoever signs Eve off from the IT side. No marketing — what runs where, what leaves the building, and what happens if we part ways.
Where Eve runs
Three options. The only difference is whose server it is — functionally they're identical.
In our cloud
We handle operations; you don't deal with updates or backups. Servers are in the European Union, specifically «fill in: provider and location, e.g. Hetzner, Germany».
In your cloud
The same deployment, but under your account and your invoice. We only have the access you grant, only for as long as we need it.
On your own server
Eve runs in Docker with its own Postgres database. If you don't want data leaving the building, that's this option — and it isn't a special mode, it's how we run it too.
What leaves your company
This is the question everyone should ask. Eve doesn't send data anywhere on its own — but to draft a reply or read an invoice, it has to send that text to a language model. That is the only place anything goes out.
The models we use are «fill in: list of providers, typically Anthropic and OpenAI». They receive the content of the specific task — the text of an email, the lines of an invoice — not your database. Nothing is retained for training; that's covered contractually.
If even that is too much, Eve can run against a model hosted on your own hardware. It costs more in machines and gives somewhat weaker results, but then nothing leaves at all.
We sign a data processing agreement as standard, before any pilot starts. «fill in: link to the DPA or a contact».
Technical details
For whoever needs this in a table.
- Runtime
- Docker, separate containers per installation
- Database
- PostgreSQL on a dedicated volume
- Data separation
- Each company gets its own instance and its own database
- Admin access
- Company VPN only, never the public internet
- Credentials
- Stored outside the application, never in source code
- Backups
- «fill in: frequency and retention»
- Availability
- «fill in: SLA, if you offer one»
- Data location
- «fill in: country»
Who can reach what
The admin console isn't on the internet
The interface Eve is configured from is reachable only over VPN. Even with the password, nobody gets to it from a public network.
Credentials sit outside the application
Passwords for email, accounting or your warehouse live outside the application code, in a file readable only by the process that needs them. They never reach source control.
Our people don't browse your data
Running the service doesn't require reading your content. When something needs fixing it happens at your request and there's a record of it. «fill in: describe your formal process if you have one».
If you decide to leave
The data is yours and it leaves with you. You get a complete database dump in standard Postgres format plus the files Eve processed — not a spreadsheet export, the actual contents.
The rules you taught Eve are written in readable sentences, not buried inside a model. Those come with you too, and they can be read without us.
«fill in: notice period and how soon you delete the data».
Most common questions
Can Eve send something to a customer without us?
Only if you explicitly allow it. By default it waits for approval on every action that leaves the company. Permission is granted per activity and can be withdrawn at any time.
What if Eve gets something wrong?
You'll see where it happened — the whole run is recorded step by step. If a rule was wrong, you fix the rule. That's exactly why approvals stay on until you're comfortable with a given activity.
Does the model train on our data?
No. Eve remembers your rules, but they're stored with you as text, not trained into a model. Model providers are contractually barred from using your content for training.
We're a small company — isn't this too much for us?
You build it brick by brick, starting with one. If it only ever handles your email, that is your complete build — nothing else has to be switched on.
More information