A Laravel Forge alternative for servers you already rent
Provisore and Forge both set up Ubuntu servers you rent yourself and deploy Laravel, PHP and Node apps to them. Forge Hobby is $12 a month for 1 external server, plus unlimited Laravel VPS servers. Provisore Solo is $12 a month for 3 servers on any provider. From 4 servers, Forge Growth costs less. Provisore rolls a deploy back when its health check fails, uses atomic releases on every site, and has server metrics on every plan, with alert rules from Pro.
When Laravel Forge is the better choice
Your servers are Laravel VPS machines
Hobby covers unlimited Laravel VPS servers for $12 a month, and Forge bills those machines by the hour in the same account. Past 3 servers, Provisore needs a larger plan for the same fleet.
laravel.com/forge/pricinglaravel.com/forge/docs/servers/laravel-vps
You run 4 servers or more
Growth covers unlimited servers for $19 a month. Provisore Pro is $29 a month for 4 servers, so on the subscription alone Forge costs less from there up.
You want the Laravel team's own tool
Forge is made by the people who make the framework, and it comes with a CLI and a PHP SDK for its API. If your team already scripts Forge, that tooling does not have to be rewritten.
What Provisore does differently
A health check that rolls back on its own
After the symlink switch Provisore requests the site. On a server error, a refused connection or a timeout it points the symlink back at the previous release and reloads.
Atomic releases on every site
Every deploy builds in a new release directory while the old one serves, then goes live with one rename. There is no deploy mode to pick when a site is created, and no plan that leaves it out.
Monitoring in the same subscription
Server metrics on every plan, then alert rules, uptime checks and log search across servers from Pro, and on-call rotations from Scale.
Deploys that wait for GitHub checks
A site can hold each push until the commit's GitHub checks pass and then deploy exactly that commit, or skip it when a check fails. A staging site can promote the commit it runs to production.
Each site under its own Unix account
A site's files, its PHP-FPM pool or systemd unit and its environment file belong to an account of its own, so on a shared server each site can read only its own files.
Swift beside PHP and Node
Vapor and Hummingbird apps are built with swift build on the server and run under systemd behind Nginx. The toolchain is downloaded, verified and installed for you.
What it costs
The cheapest plan on each side, worked out from the published prices.
| Per month | 1 server | 3 servers | 5 servers | 10 servers | 20 servers |
|---|---|---|---|---|---|
| Provisore | $12Solo | $12Solo | $29Pro | $29Pro | $59Scale |
| Laravel Forge | $12Hobby | $19Growth | $19Growth | $19Growth | $19Growth |
- Laravel Forge costs less at 5, 10 and 20 servers, the same at 1 server and more at 3 servers.
The subscription only: your provider bills the servers on every side. Provisore’s figures assume every server runs the metrics collector, because monitored servers are what the plans count. A server you only deploy to counts against nothing on Pro and Scale.
Moving from Laravel Forge
Provisore reads a Forge server through Forge's API and a read-only SSH scan, then recreates its sites, databases, scheduled commands and daemons on a new server, with repositories and deploy scripts filled in. The old machine is only read and keeps serving until you change DNS. Moving the data and uploaded files is yours, and it is the long half.
Frequently asked questions
Can I keep Forge running while I try Provisore?
Yes. The migration builds a new server beside the old one, and the old machine is never provisioned or deployed to. Both run until you point DNS at the new one.
Does Provisore deploy one site to several servers?
No. A site lives on one server. A staging site can promote the commit it runs to a production site on another server, built there with that site's own environment.
What happens to a site whose deploy fails its health check?
The symlink goes back to the previous release and Nginx reloads, so the site keeps serving the code it ran before. Database migrations are not reversed, so a destructive migration needs a fix rolled forward.
Which PHP versions and Ubuntu releases?
PHP 8.1 to 8.5, chosen per site, on Ubuntu 26.04 and 24.04 LTS.
Every fact, with its sourceTheir figures as published on 21 October 2026. Each cell links to the page it was read on.ShowHide
| Compared | Provisore | Laravel Forge |
|---|---|---|
| Pricing basis |
|
|
| Entry price |
|
|
| Servers |
|
|
| Runtimes |
|
|
| Zero-downtime deploys |
|
|
| Deploy health check |
|
|
| Backups |
|
|
| Monitoring |
|
|
| Team seats |
|
|
Put one Forge site on it and see.
14 days free on any plan, card required. Nothing on your servers changes if you leave.