IN SHORT
- The platform, the database and the systems you build run in Frankfurt, in the EU.
- The exception: model processing may happen outside the EEA under standard contractual clauses.
- Every customer gets their own project and their own prepaid balance — no shared database.
- Traffic is HTTPS only; the database is reached over TLS.
The physical answer
The platform itself, the managed Postgres database behind it and the systems built in the studio all run in the European Union, in Frankfurt. Files stored by your system sit in the same place.
If the platform offers more than one region you are asked which one at the moment a system is created, and the choice is permanent — the cloud resources are created there and cannot be moved afterwards.
The exception, stated plainly
The AI model processing may happen outside the EEA, under the European Commission’s standard contractual clauses. That is the one place data leaves the EU, and it is worth knowing before someone in your compliance function asks rather than after.
Everything else — storage, the database, the running system, the backups — stays in Frankfurt.
How customers are kept apart
- Each customer gets their own project and their own prepaid balance. There is no shared application database that everyone’s records sit in together.
- Traffic to the site, the platform and what you build is HTTPS only.
- The database is a managed Postgres reached over TLS, with continuous backup and point-in-time restore.
- Passwords are stored as scrypt hashes with a per-account salt. Sessions are signed tokens, checked on every request.
Who else touches it
The processors involved are the platform and AI provider behind the studio, Stripe for payments, Google for sign-in when you choose that route, and AWS for the infrastructure. The security page names them and says what each one is for.
Payments never touch our servers: card details are entered on Stripe’s own hosted page, and the webhook that credits your account is signature-checked and idempotent, so a retry cannot double-credit.
Support access
Support can open a customer’s studio from the admin panel. We say so because a supplier that quietly has that ability and does not mention it is the one to worry about. The admin panel is not linked from anywhere on the public site and sits behind its own separate login.
If something goes wrong
A breach that affects you is notified within 72 hours. The clock starts when the infrastructure provider tells us — we cannot know sooner than the layer beneath us does, and the security page says that rather than implying otherwise.
RELATED
Security — the full page, with everything above in its original wording
Exports and backups — getting a copy out, and what happens if you leave
Privacy — what is collected about you, as opposed to where it sits