How do you deploy a Claude Code app with Postgres in Europe?
Claude Code writes and runs code on your computer; it does not host anything. The app needs a place that runs its web process and its database, keeps secrets out of the code and serves it over HTTPS. On Codara Cloud every service runs in Helsinki, Finland, and the database, its backups and the container images stay in the EU.
1. Put the code in a GitHub repository and install the Codara GitHub App on the account that owns it. 2. Connect Claude Code to Codara Cloud: paste the setup prompt from the MCP page into Claude Code, which installs the codaracloud CLI and the local MCP server and opens the browser to sign in. 3. Ask Claude Code to create a project, the app, a Postgres database, the connection between them and the first deploy, or run the same commands yourself:
codaracloud projects create my-app --client my-workspace --name "My app"
# The app, from your GitHub repository (apps create does not build yet)
codaracloud apps create web --client my-workspace --project my-app \
--repo you/my-app --branch main
# Postgres, connected to the app: DATABASE_URL and DATABASE_DIRECT_URL are injected
codaracloud databases create main-db --engine postgres --client my-workspace --project my-app
codaracloud apps connections add web main-db --client my-workspace
# Secrets at runtime, never in the repository or the frontend bundle
codaracloud env set web SESSION_SECRET=...
# First build and release, then open the HTTPS address
codaracloud deploy web --client my-workspace --project my-app --source
codaracloud open web4. Run your migrations as the app’s pre-deploy command with DATABASE_DIRECT_URL, for example npx prisma migrate deploy or alembic upgrade head; it runs once before traffic moves to the new release. 5. Add your own domain when the app works on its codara.cloud address. From then on, every push to the branch deploys a new version.
Agent tokens are development-only by default, and actions that change or delete resources return a preview until confirmed, so you stay in charge of what the agent does in production.
How can you deploy a vibe-coded app without managing servers?
Choose a host that builds your code, runs it, renews certificates and patches the machines for you. Which one fits depends on where the app was made and what it needs. Lovable and Bolt publish apps themselves, so staying there is the least work. Code from Claude Code, Cursor or Codex is a normal repository that any platform for your framework can run.
The last row is not server-free: Coolify is free open-source software, but you rent, secure and maintain the machine it runs on. The other rows leave the servers to the provider.
| Option | What it runs | Best for |
|---|---|---|
| The builder’s own hosting (Lovable, Bolt) | The app on a lovable.app or bolt.host address, with a Supabase-based backend; custom domains on paid plans | Apps that still live in the builder and fit its backend |
| A managed app platform (Codara Cloud, Render, Railway, Fly.io) | Web services, APIs, Postgres and scheduled jobs from your repository | Full-stack apps with a server and a database |
| A frontend host plus a hosted database (Vercel or Netlify with Supabase or Neon) | Frontend and serverless functions, with the database elsewhere | Frontend-heavy apps with light server work |
| A server of your own with Coolify | Anything in containers, on a VPS you rent | People who are happy to patch and back up a server |
What does your app actually need to run?
A working preview is a useful start. Before choosing hosting, ask your coding agent to describe the app without changing it: what starts the web process, where data is stored, and which external services it calls. Check that description against the repository.
A frontend and API in one process can be one service. An API in another process needs its own service. A database, queue worker and scheduled task have different lifecycles; writing down those boundaries makes deployment and debugging much easier.
| Part | What to record |
|---|---|
| Web app / API | Repository, build and start commands, listening port, health endpoint. |
| Database | Engine and version, migration command, connection variable, backup requirement. |
| Background work | One-off task, cron schedule or continuous worker; what happens if it runs twice. |
| User uploads | Persistent volume or external object storage; what must survive a redeploy. |
| External services | AI model, email, payments and OAuth providers; secrets, quotas and separate bills. |
Can someone build it from a clean checkout?
Install from the committed lockfile and run the production build locally. A development server working on your laptop does not establish that the production start command will work. Keep a Dockerfile when you need explicit control; otherwise check the detected builder and its logs.
Codara Cloud supports GitHub repositories, container images and file uploads, with Dockerfile, Railpack, Nixpacks and static builds. Make the app listen on the configured port and on an address reachable from outside its process, rather than only localhost. Start with the documented quickstart for the exact console flow.
Where do secrets and production data go?
Put server secrets in runtime environment variables. Values embedded in a frontend bundle are public, even if their source file was called .env. A public API base URL can be build configuration; a database password or model API key cannot.
Provision the database, link its connection settings to the service and run the required migrations deliberately. Test migrations against disposable data first. Enable and verify backups for supported databases, and rehearse a restore before you depend on it. Codara restores to a new database rather than overwriting the source.
Container files are not a substitute for durable storage. Use a persistent volume where the application needs a durable filesystem. Object storage is available on Codara by separate agreement; it is not an included self-serve bucket allowance.
What should you test before sharing the URL?
Use a staging environment to exercise the real user journey with test data. A healthy process is only one check: it does not prove that sign-in, permissions or payments are correct. Keep test credentials and callback URLs separate from production.
Review CPU, memory and restart metrics while exercising the app. Web services, replicas, databases and other workloads share finite plan capacity. A service-count limit is not a promise that every service can run at its maximum size simultaneously.
- Create two test users and confirm that each can access only their own data.
- Write a database record, redeploy, and confirm the record and uploaded files survive.
- Run a scheduled or one-off task and check its output and retry behavior.
- Check sign-in callbacks, HTTPS, error logs and the path back to a known working release.
What does Codara Cloud include, and what does it not?
Codara Cloud is managed app hosting from Codara Solutions SL in Madrid, with fixed monthly plans from €5 to €100 before tax. The plan covers the app’s services, managed databases, cron jobs, custom domains and traffic under fair use, with no automatic usage overage. It runs in one region, Helsinki, and is in beta by invitation.
It runs the app you bring. It does not include your coding-agent subscription or the bill from an external AI model provider, and it does not review your application code for you.
| Plan | Price / month | Service ceiling | Shared runtime | Persistent storage |
|---|---|---|---|---|
| Starter | €5 | 10 | 0.5 vCPU / 512 MiB RAM | Up to 10 GiB persistent storage |
| Standard | €20 | 50 | 1 vCPU / 2 GiB RAM | Up to 20 GiB persistent storage |
| Pro | €50 | 100 | 2 vCPU / 4 GiB RAM | Up to 50 GiB persistent storage |
| Scale | €100 | 250 | 6 vCPU / 12 GiB RAM | Up to 150 GiB persistent storage |
Questions
- Does Claude Code host my app?
- No. Claude Code is a coding agent that works in your terminal, IDE, desktop app or browser. It can deploy to a host through that host’s CLI or MCP server, but the app runs on the host you choose.
- Which region does Codara Cloud use?
- Helsinki, Finland (Hetzner Cloud). Apps, databases, volumes, backups and container images are stored in the EU; Cloudflare’s global network carries app traffic and may cache served content.
- Do I need Docker?
- No. Without a Dockerfile, Codara detects the build with Railpack or Nixpacks, or serves a static site. Keep a Dockerfile if you want exact control of the image.
- Can I keep my Supabase database instead?
- Yes. Set its connection URL as a runtime environment variable on the app. Supabase then bills and backs up the database on its own terms, and you choose its region there.
Sources
Other providers’ figures were checked on their own pricing and documentation pages on 28 September 2026. Prices change, so check them before you decide.
- Claude Code overview ↗code.claude.com/docs/en/overview
- Claude Code and MCP ↗code.claude.com/docs/en/mcp
- Render regions ↗render.com/docs/regions
- Railway deployment regions ↗docs.railway.com/reference/deployment-regions
- Fly.io regions ↗docs.fly.io/reference/regions/
- Lovable publishing ↗docs.lovable.dev/features/publish
- Bolt Cloud ↗support.bolt.new/cloud/bolt-cloud
- Coolify installation and server requirements ↗coolify.io/docs/get-started/installation