deplane
Start deploying
PlatformAISecurityEnterpriseTemplatesPricingCompareDocsChangelog Sign inStart deploying
Changelog

What's new in Deplane.

We ship every day. Here is everything that changed for you, newest first.

Community templates

  • Publish your repository as a template. A team on a paid plan claims its public GitHub repository, puts the code it gets in deplane.template.json, and submits a branch or tag from New app → Community → Publish your own or deplane community submit. See Community templates.
  • Checked, then reviewed. Every version gets a licence check, a secret scan, a sealed test deploy with no internet and a scan of its image for known flaws, and a person approves it before it is listed. What deploys is the exact image that was checked.
  • Deploy one. Community templates sit in their own tab beside Deplane's gallery, on deplane.io/templates/community and in deplane launch --community ID, each marked "Community — not made or endorsed by Deplane", with a Report link.

Import from six platforms in the dashboard

  • Paste once, pick, import. New app → Import from another platform now moves an app from Heroku, Render, Railway, Fly.io, Vercel or Netlify without the CLI: paste one token, pick the app from the list of what it can see, and the report, the repository (or the public image the platform runs) and the app's name are filled in. Import asks for your passkey. See From the dashboard on each platform's page.
  • Secrets the platform never returns. Fly.io secrets and Vercel and Netlify secret variables cannot be read by anyone, so the import stops at a form with their names, you fill in the values, and one click deploys.
  • Undo. A failed or cancelled import has Delete what it created: the app, database and Redis it made, nothing else, so you can import again.
  • Rolling out. Each platform goes live in the dashboard after a check with a real account; until then its CLI command works as before, and Heroku is live today.

    • Deploy any public repository with a Deploy to Deplane button

    • Your repository as a template. Put a deplane.template.json at the root of a public GitHub repository, saying the port, the variables (secrets generated, never in the file) and the Postgres, Redis, MySQL, ClickHouse or disk it needs. Anyone can then deploy it in one click from New app, from deplane launch --repo OWNER/REPO, or from a Deploy to Deplane button in your README. See Templates.
    • Pinned and yours. Each deploy is pinned to the commit you checked, so Retry never builds a newer one; the app is an ordinary app in your team from then on.

    Move in from Docker Compose, Fly.io, Vercel and Netlify

    • Docker Compose. deplane import compose reads your docker-compose.yml and turns each service into an app, a worker, a managed database, a Redis or a disk, then deploys. A one-app file also imports from the dashboard, under New app. See Moving from Docker Compose.
    • Fly.io. deplane import fly moves an app's variables, workers, cron jobs and release command, read from Fly.io and your fly.toml. See Moving from Fly.io.
    • Vercel. deplane import vercel moves a project's production variables and creates a cron job for each Vercel cron. Crons your app can't answer on Deplane are listed with the command to add them later. See Moving from Vercel.
    • Netlify. deplane import netlify moves a site's production variables and build settings. See Moving from Netlify.
    • Heroku from the dashboard. The Heroku import now also runs from the dashboard, with the same report before anything is created.
    • Switch DNS on Cloudflare. deplane domains switch points your domain at Deplane, shows the exact record changes first, and can undo them. See Domains.
    • Safe to try. Every import runs on your computer with your own token, which never leaves it, reads the old platform without changing it, and has --check to see the whole report first.

    Move from Heroku, Render and Railway, new plans, Postgres 18 and our own domains

    • Heroku, Render and Railway. deplane import heroku, render and railway create the Deplane app with its secrets, workers and release command, copy your Postgres database, add a Redis, and deploy your code. The old platform keeps serving until you switch. See Moving from Heroku.
    • Five plans. Free, Hobby ($7), Pro ($20), Team ($99) and Enterprise. Free needs no card. Paid plans are not on sale yet, and we tell you before anything is billed. See Pricing.
    • Postgres 18. Create a database on Postgres 18 with deplane db create NAME --version 18 or in the dashboard. New databases stay on 17 by default.
    • Our own domains. Apps now live at <app>.deplane.app under one certificate, the dashboard at app.deplane.io and the API at api.deplane.io. The old addresses keep working for now.
    • Langfuse. LLM observability as a template, on Team and Enterprise.

    Managed MySQL and ClickHouse

    • MySQL. MySQL 8.4 with nightly backups, Back up now and restore, from the dashboard, deplane mysql and your AI tool. See MySQL.
    • ClickHouse. A managed ClickHouse for analytics, with backups and restore, on Team and Enterprise. See ClickHouse.
    • Plausible. Privacy-friendly web analytics as a template, on ClickHouse.
    • Patient health checks. A slow app now stays in service for about 30 seconds before it is taken out, instead of failing after a few seconds.

    Import a database, release commands and private networking

    • Import a Postgres database. Bring a database from any Postgres URL into a new managed one, by copy or by live sync with a one-step finish, from the dashboard, deplane db import or the API. See Importing a database.
    • Release commands. Run a command such as your migrations once for each new build, before it serves. If it fails, the old release keeps serving. See Release command.
    • One-off runs. deplane run -- CMD runs a command once in the live release and returns its exit code.
    • Deploy an image. deplane deploy --image REF --port P deploys a public Docker image.
    • Private networking. Turn it on and your team's other apps reach the app at http://<app>. Previews and other teams never can. See Private networking.

    Managed Redis

    • Redis. A managed Redis (Valkey) for caches and queues, with backups and restore, set as REDIS_URL on the apps you attach. See Redis.
    • More templates. Docmost, Ghostfolio and Vikunja join the template gallery.

    App disks

    • A disk for your app. Give an app a 5 GB disk at a path you choose, kept across deploys and restarts, backed up every night and on request, and restorable. See Disks.

    Automatic rollback, preview databases and faster builds

    • Automatic rollback. If a new release's error rate spikes in its first 10 minutes live, Deplane rolls back to the previous release and tells your team. It is on for every app; turn it off in Settings or with deplane config --auto-rollback off. See how it decides.
    • A database for each preview. Turn on "Give each preview its own empty database" and every pull request preview gets an empty Postgres as DATABASE_URL. Free, up to 3 per team, and deleted with the preview. Your production data is never copied.
    • A second copy of every backup. A separate backup server now pulls a copy of all database backups every 15 minutes. The platform's servers hold no key to it.
    • Faster builds. Images are now stored with zstd and base layers are no longer compressed again. Measured first deploys: a static site in 56 s, Express 1m12s, Go 1m16s, Flask 1m17s, FastAPI 1m20s, Next.js 2m03s.

    Database backups and point-in-time restore

    • Continuous backups. Every database's changes are streamed as they happen, with a full copy every night, encrypted with that database's own key.
    • Restore to any second. Pick a moment in your plan's backup window, or the latest one, and Deplane restores it into a new database. The original is never changed.
    • Switch apps in one step. Move every app from the old database to the restored one, each with a new release and no downtime.
    • Restore deleted databases. A deleted database can be restored from Recently deleted for your plan's backup window.
    • Everywhere. In the dashboard, with deplane db backups, restore and switch, from your AI tool, and as an assistant action. See Databases.

    Autoscaling and sleep when idle

    • Autoscaling. Set a maximum and Deplane adds instances when CPU is high and removes them when load drops, with deplane scale 1 --max 5 or the Scale card.
    • Sleep when idle. An app can sleep after 5, 15 or 60 minutes without requests. The next request wakes it, in about 10 seconds. Workers and cron jobs keep running.
    • From your AI tool and the assistant. Both can set autoscaling and sleep. See Scaling.

    Deploy from your AI tool

    • Deploy from your AI tool. Connect Claude, ChatGPT or Cursor to Deplane with one URL. Ask it to build and host an app, and it creates, deploys and runs it for you. See how to connect.
    • You stay in charge. It signs in with OAuth and a passkey, never deletes anything, never creates tokens or manages your team, and is limited to your team's plan.
    • Connected AI tools. The Tokens page lists the tools you connected, with Disconnect to end one's access at once. Activity marks every change with the tool's name.

    A new website, and the assistant can create apps

    • deplane.io. A new site with pricing, security, enterprise, AI and a comparison with other platforms, and this changelog.
    • Request access from the site. The beta request form now lives at /beta, linked from the sign-in page.
    • The assistant creates apps. Ask it to deploy a repository and it proposes the whole setup: the app, the GitHub connection, a database and the first deploy, one Confirm away.
    • More assistant actions. It can propose creating, attaching and detaching databases, adding workers and cron jobs, removing domains, and setting or unsetting variables (you type the values). It never deletes.
    • Clearer scale feedback. Saving the Scale card says what changed ("now runs 5 small instances, was 4"), or that nothing changed.
    • Messages above the Ask button. Confirmations no longer hide behind the assistant button in the corner.
    • Better answers. The assistant keeps answers written next to its tool calls and trusts its earlier answers in follow-ups.

    Ask about your apps

    • The assistant. Ask in plain words about your apps from the dashboard or with deplane ask. It reads real logs, metrics and builds and acts only when you confirm.
    • On every page. The Ask button, or ⌘K, opens the assistant with the page you are on as context.
    • Grounded answers. It knows how Deplane works: zero-downtime deploys, sizes and alerts.

    Alerts

    • Alerts for apps. Know when an app goes down, errors, slows down or fails to deploy.
    • Channels. Send alerts to the dashboard, Slack, Discord and webhooks. An email channel exists but does not send until email is set up.
    • Readable activity. Every activity event is now a plain sentence, including domains and processes.

    Deploy from GitHub

    • Push to deploy. Connect a repository and every push to the branch deploys, with a commit status on GitHub.
    • Pull request previews. Every pull request gets its own live address and one comment that shows its state. Previews are deleted when the pull request closes.
    • Sign in with GitHub. Through the same Deplane GitHub App.
    • Clear errors. When a GitHub deploy cannot start, for example an empty repository or a missing branch, the dashboard says why.
    • Redeploy and Deploy latest commit, from the dashboard and the CLI.

    Postgres, teams and faster builds

    • Managed Postgres 17. Create a database, attach it to an app, and it gets DATABASE_URL. Each database runs in its own microVM.
    • Databases page and a Notes + Postgres template that creates and attaches its database for you.
    • Teams. Invite people by link, with members and owners. Owners can rename the team from the team menu.
    • Faster builds. Plans are made in about a second, every build step is cached for next time, and base images come from our own registry.
    • Builds say when they wait. When the build servers are busy, the build tells you, and fails clearly if it cannot run.
    • Docs in the dashboard. The documentation is served at /docs, in the dashboard's design.
    • Brand. The new Deplane mark, favicons and link previews.

    The dashboard, domains, workers and cron

    • A new dashboard. A light design with live metrics: requests, errors, p95 latency, CPU and memory for every app.
    • Custom domains. Add your own domain with a DNS check of ownership and automatic HTTPS, from the dashboard or the CLI.
    • Workers and cron jobs. Run background and scheduled processes next to your app.
    • Deploy from the browser. Drop a folder on the New app page; Deplane detects the stack and shows it.

    A microVM for every app

    • Kata Containers. Every app and build now runs in its own lightweight virtual machine with its own kernel.
    • Your full memory. The VM's own overhead no longer counts against the memory your app gets.
    • Safer rollouts. Instances get a 5-second pause before stopping, so rollouts drop no requests.
    • A clearer CLI. deplane deploy waits until the address answers, status says when an app was never deployed, and launch never deploys over an existing app.
    • Zero-config Python. Python apps build with no configuration.
    • Rolling security reboots. Servers patch and reboot one at a time, moving apps away first.

    Docs, abuse handling and limits

    • The docs site. Every command, limit and error code, checked by tests, with Markdown twins and llms.txt for agents.
    • Report abuse. A form to report phishing, malware or spam, and suspension of abusive apps and teams.
    • Deploy limit. Up to 10 deploys per hour per app, to keep the build servers fair.
    • Agents never get prompted. Without a terminal, the CLI never waits for input.
    • Secrets stay hidden. --debug never prints secret values.

    Builds and launch

    • deplane launch and deplane deploy. From a folder to a live HTTPS address in one command.
    • Zero-config detection. Deplane works out the language, framework and port.
    • Sandboxed builds. Builds run in their own sandbox, with a fair queue and quotas per team.
    • Safe uploads. .env files and .git are never uploaded, and links that escape the project are refused.
    • Live build and app logs, streamed to the CLI.
    • Images are checked before a release is created.

    Sign-in and apps

    • Passkeys. Sign in with Touch ID, Face ID, Windows Hello or a security key, with a mandatory second factor.
    • Scanner-proof sign-in links that email security scanners cannot use up.
    • CLI login with approval. deplane login shows a code you approve in the browser with your passkey.
    • CI tokens for scripts and pipelines, and one-click revoking of a CLI login.
    • Apps, releases and rollback. Create apps, scale them within your plan, set encrypted secrets, and roll back to any release.
    • An activity log for every change.

    Day one

    • The design. Deplane's plan: a secure, simple app platform on our own infrastructure, with an AI assistant and plans you can grow through.

Try what shipped today.

Request access Read the docs