DEPLOY

Ten frameworks, one server you own.

Depfloy deploys Next.js, Nuxt, Remix, React Router, Astro, Laravel, Symfony, Statamic, WordPress and plain PHP. All ten get the same release mechanism: the build happens beside the version currently serving, and goes live with a symlink flip — so a failed build never reaches a visitor.

JAVASCRIPT

Built beside the running release, served by a Node process behind nginx.

Next.js

Deploy Next.js without a usage meter.

Nuxt

Deploy Nuxt to your own machine.

Astro

Deploy Astro to a server you own.

Remix

Deploy Remix without renting a platform.

React Router

Deploy React Router to your own server.

PHP

Served by PHP-FPM, with the release swapped under it rather than restarted.

Laravel

Deploy Laravel to a server you own.

WordPress

1-click WordPress, on a server you own.

Symfony

Deploy Symfony to hardware you control.

Statamic

Deploy Statamic without losing your content.

PHP

Deploy PHP without adopting a framework.

THE SAME FOUR STEPS

The mechanism does not change with the language.

A standby port gets the new process. A health check runs against it. The release soaks while a probe fires every five seconds. Only then does nginx switch upstream and the old process drain. Every framework page describes this same chain, because every framework goes through it.

What the list does not include. There is no TanStack Start support today. Node rollback rebuilds rather than flipping back to a kept artifact, which makes it slower than the PHP path. And build memory is real: a 2 GB VPS cannot build a Next.js app, which is a floor rather than an estimate — how many builds can run at once on one VPS has the measurement method.

QUESTIONS

Before you pick a machine.

Which framework is heaviest to build? +
Next.js, by a distance. Two Node projects are not the same size — Astro builds light enough that an 8 GB machine can take four at once, where Next.js on the same machine is a different number. A 2 GB VPS cannot build a Next.js app at all; that is a floor we have measured rather than estimated.
Can I run more than one framework on one server? +
Yes, and most people do. A server carries as many projects as its memory allows. The one rule that applies regardless of framework or plan is that two deploys of the same project never run in parallel — they would write to the same release directory and flip the same symlink, and the last one to finish would win.
Do I need a Git repository? +
To deploy, yes: all ten build from a branch on GitHub, GitLab or Bitbucket. There is one other way onto a server — the one-click catalog installs WordPress or phpMyAdmin directly, with no repository, no branch and no build step. Those two applications are the entire catalog, and an installed application is updated in place rather than deployed.

Push one of the ten and watch it go live.

7 days free, no credit card. Connect a server, pick the framework you already build with, and deploy it.

Start free trial How releases work