Guides
Deploy anything on your own server.
Step-by-step guides for the stacks people run most, and for moving off the platforms they run them on today.
Deploy a framework.
Deploy Next.jsRun your Next.js app as a long-lived Node server on a machine you choose, with previews for every pull request and no per-function billing.→Deploy DjangoDeploy Django with Gunicorn on your own server: migrations before every release, Postgres next to the app, and HTTPS on your domain.→Deploy RailsDeploy Rails with Puma on a server you own: db:migrate before each release, zero-downtime rollouts and one flat plan for the whole app.→Deploy LaravelDeploy Laravel on your own server: artisan migrate before each release, queue workers and the scheduler as their own services, and Postgres alongside.→Deploy GoDeploy a Go service on your own server: a binary built for you, health-checked releases with no downtime, and HTTPS on your domain.→Deploy DockerBring your Dockerfile or a prebuilt image and run it on your own server, with zero-downtime releases, previews and automatic HTTPS.→Deploy BunDeploy a Bun server on your own machine: installs with Bun, Postgres through Bun’s built-in SQL client, and health-checked releases with no downtime.→Deploy DenoDeploy a Deno app on your own server: tasks from deno.json, npm packages for Postgres, and zero-downtime releases with HTTPS on your domain.→Deploy PhoenixDeploy Phoenix on a server you own: a mix release, migrations before each release, and LiveView sockets served over HTTPS on your domain.→Deploy RustDeploy a Rust service on your own server: a release binary built for you, health-checked rollouts with no downtime, and HTTPS on your domain.→Deploy .NETDeploy an ASP.NET Core app on your own server: EF Core migrations before each release, Postgres alongside, and zero-downtime rollouts.→Deploy Spring BootDeploy a Spring Boot app on your own server: a jar built for you, Flyway migrations on startup, and health-checked releases with no downtime.→
Move from another platform.
Migrate from RailwayMove each Railway service to a server you own. The concepts map one to one, so the move is mostly copying settings and your data.→Migrate from RenderMove each Render web service, worker and database to a server you own, and stop paying for every one of them separately.→Migrate from HerokuMove your Heroku app off dynos and onto a server you own. Web and worker process types become services, and the release phase becomes a pre-deploy command.→
Own your infrastructure again.
Plans from $1 a month, billed per server, never per service.
Early access · We’ll set up your workspace
Or talk to us →