Deplane is the secure cloud for apps and AI agents. It builds any app from a folder or a GitHub repository, runs it in its own microVM, and gives it HTTPS, Postgres, logs, metrics and alerts. No config files, no servers to look after, no shared kernel with strangers.
Deploys, previews, databases, background jobs, domains, metrics and alerts come built in and work together. You write the app; Deplane runs it.
Push to deploy. A preview for every pull request.
Connect a GitHub repository once. Every push to your branch ships to production; every pull request gets its own live URL, and if you want, its own empty database, posted as a comment and removed when the PR closes.
Deploymentsmy-shop
v14 · Add Apple Pay to checkoutLivemain · 41s
Preview · pr-212 · New pricing tableBuildingpr-212 · 12s
v13 · Fix cart total roundingReadymain · 2h ago
v12 · Upgrade to Next.js 15Readymain · yesterday
Zero-downtime rollouts
A new release takes traffic only when it is healthy. If its errors spike in the first 10 minutes, Deplane rolls it back for you. Or roll back to any version in one click.
$deplane rollback 13
✓ Rolled back to v13 as v15.
Managed Postgres 17
Create a database and attach it. Your app gets DATABASE_URL, no downtime. Backed up continuously: restore it to any second of the last 7 days.
$deplane db create main
$deplane db attach main --app shop
$deplane db restore main --at -10m
Workers and cron jobs
Run queues and scheduled tasks next to your web app, from the same code and the same variables.
Add a domain, set one DNS record, and the certificate is issued and renewed for you.
shop.example.comActive
www.shop.example.comActive
eu.shop.example.comChecking DNS
Metrics without a setup
Requests, errors, p95 latency, CPU and memory for every app, from the first request. Live logs from every instance, in the dashboard and the CLI.
Requestslast 24h
184krequests
0.04%errors
86 msp95
Alerts before your users notice
Know when an app goes down, starts erroring, slows down or fails to deploy. Alerts go to Slack, Discord or any webhook (email is not set up yet), and close themselves when things recover.
Alertsmy-shop
p95 above 800 ms for 5 minutesSlack · 14:02
Resolved: error rate back under 1%Slack · 13:47
Deploy of v12 failed: health checkDiscord · Mon
Encrypted secrets
Every value has its own encryption key. Values are never shown again, never logged, and build secrets never end up in images.
Teams and an activity log
Invite people by link. Every change, by a person, the CLI, CI or the assistant, is in the activity log with who and when.
A CLI that scripts well
Every command has --json, stable exit codes and errors that say how to fix them. Built for CI, and for AI agents.
How it works
From folder to production in three steps.
01 · Connect
Bring the code
Pick a GitHub repository in the dashboard, drop a folder in the browser, or run one command in your project.
$deplane launch
02 · Build
We work out the rest
Deplane detects the language, framework, version and port. A Dockerfile is used if you have one. Every build step is cached for the next build.
Detected FastAPI, Python 3.12, port 8000
03 · Run
Live, isolated, watched
Each instance starts in its own microVM behind HTTPS. Add instances under load and sleep when idle, on their own. Add a database, a worker or a domain whenever you need them.
✓ https://api.deplane.dev
Deploy your way
Browser, terminal, Git, or an AI agent.
Four ways in, one platform. Everything you do in one place shows up in the others, and in the activity log.
Dashboard: pick a repo or drop a folder, see the build live, then the app's metrics, logs and settings.
CLI:launch, deploy, logs, scale, rollback. Signed in with your passkey.
GitHub: push to deploy, previews for pull requests, commit statuses on every build.
AI tools and agents: connect Claude, ChatGPT or Cursor and ask them to deploy; or use JSON output, CI tokens and docs at /llms.txt.
# deploy the current folder$deplane deploy# follow logs from every instance$deplane logs# two medium instances$deplane scale 2 --size medium
# a variable, rolled out with no downtime$deplane secrets set STRIPE_KEY=sk_live_...
# back to the last good release$deplane rollback
# connect a repository once in the dashboard, then push$ git push origin main
✓ Deplane v15 is live at https://shop.deplane.dev
$deplane github
Repository: acme/shop
Branch: main (every push deploys)
Previews: on, for pull requests from the repository
#12 Faster checkout https://shop-pr-12.deplane.dev Running
# an agent deploys and checks its own work$deplane deploy --json --yes
{ "app": "notes", "version": 7, "status": "running",
"url": "https://notes.deplane.dev" }
$deplane logs --json --tail 50
# exit code 4: the deploy failed, the previous
# release keeps serving; read logs, fix, retry
Security
Your own virtual machine. Not someone else's kernel.
Most app platforms run customers side by side in containers that share one Linux kernel. One kernel bug and the walls are gone. On Deplane, every app, every build and every database runs in its own microVM with its own kernel.
A microVM per app, build and database, on servers that hold no platform secrets.
Passkeys and a second factor on every login. No passwords to leak or reuse.
Network rules outside the sandbox: apps cannot reach our servers, cloud metadata or other teams.
185 isolation checks run against the live servers after every kernel, sandbox or orchestration upgrade. Last run: 0 failures.
firewall rules · enforced on the host, outside every VM
Deplane data center · Europe
AI
Built for the code AI writes, and the agents that ship it.
More and more code reaches production without anyone reading every line. That is exactly when isolation matters. And the platform should be as easy for an agent to drive as for a person.
An assistant that knows your apps (beta). It reads the real logs, metrics and builds, explains what broke, and proposes the fix. Nothing changes until you press Confirm.
Agent-ready by design. JSON everywhere, scoped CI tokens, and docs agents can read at /llms.txt.
Deploy from your AI tool. Connect Claude, ChatGPT or Cursor with one URL, and ask it to build and host an app. It never deletes anything.
Coming next: sandboxes that start in about a second, for agents that run code.
p95 latency on my-shop went from 90 ms to 1.4 s at 09:12, right after v14 rolled out. The logs show 2,318 connection timeout errors to Postgres since then, and both instances are at 97% memory.
v14 added a query per cart item. The quickest fix is to go back to v13 while you look at it.
Roll back my-shop to v13Creates v15 from v13's build. No downtime.
Confirm
Never outgrow it
Start small. Grow to your own cloud. Never migrate.
Teams usually leave their app platform at the worst possible time: when they get big. Deplane is built so you never have to. The same deplane deploy, the same dashboard and the same API, from your first side project toward your own dedicated servers.
01
Start
Shared servers, every app in its own microVM. Live in minutes.
Beta today · Pro $15 soon
02
Team
More apps, memory and databases, members, alerts and an uptime SLA.
Team · $99 · soon
03
Scale
Dedicated servers just for you, inside our cluster. One setting, not a migration. Roadmap
Enterprise
04
Big
Your own cluster or region on bare-metal servers, with a private network. We run it.
Enterprise
05
Largest
Private Deplane: the whole platform in your own account or data center, managed by us.
Enterprise
Steps 3, 4 and 5 are on the roadmap (4 and 5 in 2027). Today there is the Beta plan on shared servers. See Enterprise.
185live isolation checks, 0 failures on the last run
1 VMper app, per build and per database
0passwords. Passkeys and a second factor only
EUservers and data, in our own data centers
Pricing
Simple plans. The whole product on every one.
The beta is free today. Pro and Team are coming soon. Plans will differ in how much runs and how many people work together, not in which features you get.
Anything that serves HTTP on a port: Node (Next.js, Remix, Express, NestJS and more), Python (Django, FastAPI, Flask), Go, Ruby on Rails, PHP and Laravel, Java and Spring Boot, static sites, or any project with a Dockerfile. Background workers and cron jobs run next to it.
Do I need a Dockerfile or a config file?
No. Deplane detects the language, framework, version and port, and builds it for you. If you have a Dockerfile, it is used. deplane.toml is optional and every field has a working default.
How is this different from Vercel?
Vercel is built around front-ends and serverless functions. Deplane runs full, long-running apps: servers, WebSockets, queues, cron jobs and Postgres, each in its own microVM. You get Vercel-style simplicity for the whole backend.
Fly.io also isolates apps with microVMs and is very capable, but expects you to write config and work in the terminal. Deplane needs no config, has a complete dashboard, managed Postgres attached in one click, and an assistant that operates your apps with you.
Where does my data live?
In our own data centers in Europe. Deplane does not run on AWS, Google Cloud or Azure. Choosing the region and servers used by no one else are on the Enterprise roadmap.
What happens if my app gets really big?
You stay. Add instances and sizes as you grow, then move to dedicated servers, and later to your own cluster, on the same platform with the same commands. How growing works.
Is there a free plan?
The beta is free: no card needed, up to 3 apps and 1.5 GB of memory running. Pro and Team are coming soon, and we tell you before anything is billed.
Can I try it today?
Deplane is in an invite-only beta. Request access and tell us what you want to run; we approve people every day.
Your next deploy could be this one.
Bring a repository or a folder. Deplane takes it from there.