For everyone building with Claude Code, Codex & Cursor
Your agent writes the app in an afternoon. Then comes the part that eats days: servers, database, migrations, secrets, TLS, staging. Sovyn gives your agent tools for exactly that — as an MCP server. Deploying becomes one sentence in the terminal you already work in.
Free analysis · setup is one command · your code stays in your GitHub
Deploy this app to Sovyn.
sovyn_import_repo
Repo imported, analysis running. Node, Postgres, Drizzle migrations, 4 custom secrets.
sovyn_confirm_deploy_plan
Deploy plan confirmed: DATABASE_URL, migration on start, port 3000.
sovyn_set_env
I need STRIPE_SECRET_KEY and RESEND_API_KEY from you — I don't make those up.
sovyn_provision
Creating Postgres, container, domain and TLS. Hardware in Germany.
Your app is live — its own database, its own domain, European infrastructure. Without typing ssh once.
No Dockerfile evenings, no Terraform, no Kubernetes tutorial at 11 pm.
Why Sovyn?
Between “runs on localhost” and “runs in production” still sits the work you never wanted to learn DevOps for.
The feature was done in two hours. Then: Dockerfile, Postgres, migrations on deploy, reverse proxy, certificates, backups, env vars in three places. None of it is your product — yet all of it sits between you and your first real user.
The moment your first customer has a works council or a data protection officer, “US provider, EU region” no longer cuts it. DPA, TOMs, subprocessors — Sovyn puts your app on European infrastructure and ships the paperwork with it.
It knows your code better than any dashboard: which env var the database reads, which command migrates, which port listens. Via MCP it gets real tools for that — not just instructions you end up typing out yourself.
How a deploy works
Analyzing costs nothing. You only pay once your app is actually running — and setup is included in the subscription.
Create an API key in the Sovyn app, paste one line into your agent — with Claude Code it's a single command. From then on your agent knows Sovyn in every project you open.
“Deploy this app to Sovyn.” Your agent imports the repo, has it analyzed and confirms the deploy plan: which env var the database reads, which command migrates, which port listens. What it knows for sure, it fills in itself — for the rest it asks you. It never invents secrets.
Staging deploys automatically on every push. Production doesn't: it's pinned to a fixed commit and only moves when you promote. No accidental live deploy right before you call it a day.
What you get: a dedicated container and database per app on Hetzner hardware in Germany, domain and TLS automatic, secrets encrypted, backups included. Prefer clicking over chatting? The same flow works in the Sovyn app too.
Setup
The Sovyn MCP server runs remotely over HTTP — there's nothing to install and nothing running on your machine. All you need is the URL and your API key.
One command in your terminal — applies to this project from then on.
claude mcp add --transport http sovyn \
https://app.sovyn.eu/api/mcp \
--header "x-api-key: sovyn_your_api_key"
In ~/.codex/config.toml
[mcp_servers.sovyn]
url = "https://app.sovyn.eu/api/mcp"
http_headers = { "x-api-key" = "sovyn_your_api_key" }
In your client's mcpServers configuration
{
"mcpServers": {
"sovyn": {
"type": "http",
"url": "https://app.sovyn.eu/api/mcp",
"headers": { "x-api-key": "sovyn_your_api_key" }
}
}
}
You create the API key in the Sovyn app under “API keys” — it's shown exactly once. If you'd rather keep secrets out of config files: Codex can read the header from an environment variable (env_http_headers).
Every one of these tools asks you before it changes anything — your agent never makes an expensive call on its own.
Backups
Your code lives in GitHub — nothing happens to it. What hurts is the data: orders, accounts, everything your users have entered. Sovyn backs it up automatically — and restores it at the push of a button.
Every 6 hours, daily, or weekly — you pick the rhythm and how many snapshots to keep. Configurable per environment. And in between, one click on “Back up now” is all it takes.
Every backup is encrypted with AES-256 and gets its own key. Delete a backup and the key is gone — the archive becomes permanently unreadable. Exactly the answer you need when a user insists on deletion.
Pick a snapshot, confirm, done. The current state is automatically backed up first — in case you change your mind after all. No terminal, no database commands, no support ticket.
Backups go to European object storage — the same infrastructure your app runs on. No copy of your data ever leaves the EU.
Sleep easy
An “EU region” at a US provider soothes your conscience, not your legal position. Sovyn puts your app on infrastructure run by European companies — from the data center to the signature on your contract.
No US parent company, no legal boilerplate from Delaware. When your customer asks where their data lives, you have an answer that feels good — and holds up.
DPA, TOMs, subprocessor list — the documents B2B customers ask for are ready and waiting for every app. The Pro plan adds an audit log and status page on top.
A moving company that locks you in would be absurd. You can take your code, data, and files with you anytime, free of charge — and if you don't want a commitment, take the monthly-cancelable option.
FAQ
It gives your coding agent tools for everything that comes after the code: import and analyze the repo, confirm the deploy plan, set secrets, provision a European stack, add staging and go live. The agent calls these tools itself and is told after every step what comes next — you watch and decide at the points where there's actually something to decide.
Yes. Sovyn is a remote MCP server over HTTP — any client that can add MCP servers via URL and header works: Claude Code, Codex CLI, Cursor, Cline, Windsurf, VS Code and others. There's no extension to install and no local process that has to keep running.
No — hand-built repos are the normal case. The analysis reads your code and proposes a deploy plan; for the fields it can't derive with confidence — the env var for the database, the migration command, the port — your agent or you confirm. If Sovyn doesn't find a viable path, it says so openly instead of trying blindly.
They're stored encrypted on the project and only injected into the running app — they're never returned, not even to your agent. Job logs are truncated and scrubbed before delivery so no credentials end up in a chat transcript. And your agent never invents secrets: whatever it doesn't know, it asks you for.
Staging deploys automatically on every push to the branch. Production deliberately doesn't follow the branch — it's pinned to a fixed commit and only moves when you promote. Nothing gets merged and nothing gets pushed: exactly the state you tested on staging goes live.
Yes. For Postgres a pg_dump export is enough — either as a public download URL your agent passes along, or as a file upload on the project page in your browser. If the app comes from a platform with a reachable MySQL database, Sovyn takes the data over directly from there.
Analysis and deploy plan are free — so you see up front what Sovyn intends to do with your app. After that you pay a subscription per app, including hosting, database, backups and setup. The details are in the pricing overview on the home page.
No — that's one of the things you'd otherwise have to bolt on when self-deploying. Per environment you set the interval (every 6 hours up to weekly) and the retention, Sovyn does the rest: pg_dump or the matching dump for your database type, AES-256 encryption before upload and storage on European object storage. Restoring is one click, including an automatic snapshot of the current state beforehand. Every archive has its own key — delete the backup and it's cryptographically destroyed, not just removed from a list.
No. Your code stays in your own GitHub repo and you keep developing as usual — with the agent of your choice. You can take code, data and files with you at any time; Sovyn deploys from your repo, it doesn't own it.
Connect your repo and see within minutes how Sovyn would deploy your app — which stack gets created, what it costs, and what you no longer have to build yourself.
Free · no credit card · no strings attached