Private by architecture
Your data stays
in your building.
Hemicule runs on infrastructure you own. There is no shared cloud, no data export, and no third party sitting between your systems and your AI employee.
What that means in practice
Four boundaries, written down.
-
01
Where it runs
Your server, your VPC, or a machine in your office. We deploy there and hand over the keys. Nothing is mirrored back to us, and there is no control plane we can reach into.
-
02
What it can reach
Only the systems you name, with the permissions you grant. Connections are explicit and reversible.
- Each integration uses a credential you issue and can revoke at any time.
- No blanket admin access. Scope is set per workflow, not per company.
- Anything not on the list is unreachable by design, not by policy.
-
03
Who can see what
Access follows your org chart, not ours. Every run leaves a record you can read.
- Role-based access for the people on your side.
- A run log for every action: input, output, timestamp, and which system was touched.
- Approval gates on anything irreversible — sending, filing, paying, deleting.
-
04
What we run on
An open-source stack with no vendor lock: Postgres, a vector store, and a workflow engine you can inspect. The code and configuration live in your repository.
- Readable source. Nothing hidden behind a proprietary runtime.
- If we disappear tomorrow, your system keeps running.
- If you leave, you take the code, the data, and the history with you.
We don’t hold SOC 2 or ISO 27001. Here’s what we do instead.
We are a small team, and we won’t pretend to be a large one. Buying a certificate is not the same as earning it. So we compete on a different argument: data that never enters our boundary cannot be leaked by a breach on our side, and there is no subprocessor for you to audit.
No subprocessors
Your data is not passed to a model vendor, an analytics tool, or a hosting partner we chose.
No vendor-side blast radius
A breach at Hemicule exposes our laptops, not your invoices. The systems holding your data are yours.
Auditable by you
You can read the code, the logs, and the configuration at any time, without asking us for a report.
Want to see the boundary before you commit?
Book a 30-minute audit and we will draw where each system sits, what the AI employee can touch, and what stays out of reach.