Data Residency, Security & Isolation

If you're moving real business operations onto a platform, you're right to ask where your data physically lives, who can reach it, and what happens if you ever want to walk away with everything. Here are clear, straight answers.

The short version: your app runs on European servers, in its own isolated database that no other customer can reach. You can lock down access with IP restrictions, 2FA, audit logging, and role-based permissions — and you can take a full export of your code and data with you at any time.

1. Where your servers live

European data residency. Our infrastructure runs in Helsinki, Finland and Falkenstein, Germany — your application and its data stay within the EU.
Dedicated to your app. Your application runs in its own isolated environment on that infrastructure (see ring-fencing below), not pooled with other customers' data.
Need a specific region or a dedicated host? For commercial deployments we can discuss pinning your app to a particular location or running it on dedicated infrastructure — just ask.

2. Security controls

We can layer several controls on top of your application to match the security posture your organization needs:

Geographic / IP restrictions. We can limit access by IP address or geography, so the app is only reachable from the locations and networks you approve.
Audit logging of user activity. A record of who did what and when, so you have accountability and a trail to review.
Two-factor authentication (2FA). We can require a second factor at sign-in to protect against compromised passwords.
Role-based access control. Granular roles and permissions so each user only sees the data and workflows they're authorized for — preventing unauthorized access to sensitive data or operations.

These are configured per app to fit your requirements. Tell us your security needs and we'll map the right combination of controls to them.

3. Ring-fencing & isolation

"Ring-fencing" means your app and its data are walled off from every other customer on the platform. Concretely:

Your own isolated database. Your data sits in a database that is inaccessible to any other LlamaPress user — it is not shared or co-mingled with anyone else's.
Fully exportable. You can pull a complete export of your data at any time, and we run automated backups with on-request downloads. (See Downloading Your App's Data.)
Your own URL or domain. Your app can run on its own dedicated URL or custom domain rather than a shared address. (See Connecting Your Custom Domain.)
Your own dedicated email address. We can set up a dedicated email address for the application, so notifications and correspondence come from your own identity.

4. Source code & your right to leave

You own your application's code. The app-specific code built for your business is yours, and we can make it available to you — as a downloadable export or a GitHub repository invite. (See Getting Your Source Code.)
A standard, portable stack. Your app is a normal Ruby on Rails + PostgreSQL application, so it isn't trapped inside a proprietary black box — it can run independently of LlamaPress.
Self-hosting under a licensing agreement. If you ever want to take full control, you can eventually self-host the application under a licensing arrangement, running it on your own infrastructure. We'll help with the handoff.
No lock-in by design. Between the full source export and the complete database export, you're never solely dependent on us — your exit path is simple and documented. (See You Own Your App.)

The honest framing: some of these controls (dedicated regions, formal SLAs, advanced access policies) are part of a dedicated or enterprise setup rather than the default plan. We're glad to put the specifics in writing for your deployment — the point is that nothing here locks you in, and your data stays in the EU, isolated, and exportable.

Want a dedicated-infrastructure, formal-SLA, or licensing/self-host option mapped out for your organization? Email support@llamapress.ai and we'll walk through it with you.