EU Infrastructure · AI-native

Ship your full stack effortlessly.
On European infrastructure.

Apps, databases, sign-in, files, and functions. In one platform, on EU infrastructure. One push manual set-up, or plug it into Claude, Lovable, or any AI agent for one-prompt deploys.

For AI agents →
EU-only infrastructure One push or one prompt AI-safe by default GDPR DPA on paid plans
CLI Claude Code PREVIEW
$olaia deploy ./my-app
→ web service · live at my-app.olaia.eu
$olaia db create
→ postgres · ready · DATABASE_URL injected
$olaia auth init
→ email + magic links · ready
$olaia compute deploy ./send-welcome
→ function · live · triggered by new user
✓ stack ready · all EU · no glue code
$

Everything your app needs.

Five building blocks, one platform, all in Europe. They know about each other. Connect a database to a project and the connection is wired automatically.

📦

Projects

Deploy apps in one push.

🗄️

Databases

Postgres in one click.

🔐

Auth

Sign-in, ready to use.

📁

Storage

Files, kept in Europe.

Compute

Functions and jobs.

AI does the work.
You hold the keys.

When you plug Olaia into Claude, Cursor, Lovable, or another AI agent, the agent ships apps, spins up databases, and wires functions together. Anything sensitive stays with you. You stay in control of the choices that matter, without slowing down the ones that don't.

Secrets and keys

Olaia auto-wires its own services. External keys are never visible to the agent. Only you manage them directly.

Production deploys

AI ships to staging freely. Promoting to production needs your approval.

Payments

AI hits a paid feature, you get a one-click approval link. Agent continues once you confirm.

Built for Europe.
Operated in Europe.

Every project container, database, auth session, uploaded file, and function invocation runs on EU-based cloud infrastructure. No US hyperscaler in the critical path.

For EU companies, this isn't just a nice-to-have. Your users' data should stay under the legal framework they were promised.

ℹ We use GitHub for repo access and Stripe for billing, and we're transparent about this. Your deployed applications, databases, files, and logs: EU-only. We'll always tell you exactly what touches what.

  • 🇪🇺 EU data residency
    European cloud providers only. Multi-provider, EU-incorporated.
  • 🚫 No US hyperscaler in the path
    Not AWS, Azure, or GCP. EU-based cloud providers, all the way down. Multi-provider by design, never tied to one.
  • 📄 GDPR DPA on every paid plan
    Required for most EU businesses. Included, not an add-on.
  • 💶 Priced and invoiced in Euro
    Invoice billing available on Team. No FX surprises.
  • 🏢 EU incorporated and operated
    EU law governs. Not subject to US CLOUD Act on core infrastructure.

Generous Free. More, coming soon.

Build a real app on Free. No card needed. Pro and Team coming soon for when you scale.

Pro
From 9/mo
For serious indie builders.
  • More of everything in Free
  • Custom domains
  • Priority builds
  • 30-day log retention
  • GDPR DPA included
Team
From 49/mo
For teams on EU infrastructure.
  • Everything in Pro
  • Team seats
  • 90-day log retention
  • Invoice billing (EU VAT)

All plans · EU data residency · Auto TLS · GDPR-native analytics

Questions.

For Projects: Next.js, Astro, SvelteKit, Node.js, static sites, and any app with a Dockerfile. Framework detection is automatic. Beyond apps you get managed Postgres, our own Auth (email, magic links, Google), S3-compatible Storage, and a Compute runtime for functions, jobs, and workers, out of the box.
Your application containers, databases, auth sessions, uploaded files, function invocations, build artifacts, environment variables, and logs all run on EU-based cloud providers, in EU data centres, operated by EU-incorporated entities. No US cloud provider is in the compute path. We use GitHub for repo access and Stripe for billing and we're transparent about that. Your apps and their data stay entirely in the EU.
Not really, and this is the trap. EU regions from US hyperscalers offer data residency, not data sovereignty. The US CLOUD Act compels any US-headquartered company to hand over data to US authorities on request, regardless of where the data physically sits. An EU region doesn't change which jurisdiction the parent company is under.

This isn't a hypothetical. On 10 June 2025, Microsoft France's legal director Anton Carniaux testified under oath at the French Senate. Asked whether he could guarantee that French citizens' data stored in EU data centres would never be handed to US authorities without French consent, he answered: "Non, je ne peux pas le garantir". No, I cannot guarantee that. AWS has made similar admissions. The same applies to Google Cloud and any other US-controlled provider.

Olaia runs on EU-incorporated cloud providers. No US parent company in the chain. Same workflow as the hyperscalers, with sovereignty that actually holds up.
Just deployment is fine. Start with a project. Add a database when you need one. Add auth when users show up. Each block is independent but they wire together cleanly when you want them to. Connect a database to a project and the connection string is injected automatically.
Anything that speaks MCP: Claude, Cursor, Lovable, Windsurf, and others. We provide an MCP server you plug into your AI tool of choice. The agent gets the same actions you'd get in the dashboard, with sensible guardrails on sensitive operations.
Yes, safely. AI agents can ship apps, provision databases, and wire things together, but anything sensitive routes back to you. Payments come back as a one-click payment link. External API keys (Stripe, third-party services) are never visible to the agent and only you can save them. Production deploys need your nod. The AI does the work; you hold the keys.
Yes. Upload a zip file directly from the dashboard. Olaia detects your framework, runs the same build pipeline, and gives you a generated URL and custom domain support. Zip projects support everything except PR preview deployments (there's no git context). Re-deploy any time by uploading a new zip.