Moss.sh Alternative for the Servers and Sites Moss Used to Manage

Is moss.sh down?

On 27 and 28 September 2026, yes: moss.sh did not resolve, and Google Public DNS reported that the domain's nameservers were not responding. With the domain unreachable, the dashboard, sign in, webhooks and the Moss API are unreachable too, whatever the state of the company behind it. We have not seen a shutdown notice, so treat this as an outage of unknown length rather than a confirmed closure.

The last public copies of the site, archived in January and March 2026, still showed the full pricing page and sign up buttons, but the article archive ended at December 2025. Moss announced a shutdown once before and was rescued by an acquisition, so it may come back. The practical question for a business is not whether it returns, it is whether you can ship a fix to a client site tomorrow morning. If the answer depends on Moss, plan the move now while the servers are still running normally.

Will my websites stop working if Moss goes away?

No, not immediately. The sites keep serving because Nginx, PHP-FPM, the database and cron all run on your own server, not inside Moss. What breaks is everything that needed the panel to act: deploys started from Moss or from a git webhook pointing at Moss, alerts from the monitoring add-on, and any change you would normally make through the dashboard, such as adding a site, a database or a worker.

Three things deserve a check this week. First, certificates: run systemctl list-timers and crontab -l as root and confirm something on the server renews Let's Encrypt certificates, because they expire 90 days after issue. Second, security updates: confirm unattended upgrades are enabled on the server itself. Third, access: make sure your own SSH key is on every server, since keys added through a panel can be tied to a panel user. Once those three are covered, you have time to migrate properly.

How do I migrate servers from Moss to another panel?

Build a new server with the new panel, deploy each site from git onto it, copy the database and uploads, then switch DNS one site at a time. Do not try to import a Moss configured server into another panel. Panels expect to own the Nginx, PHP and Supervisor layout they created, and a half adopted server is the kind of setup that fails at 2 a.m.

A clean order that works for most fleets: inventory each old server (sites in /etc/nginx, databases, crontab -l for each user, programs in /etc/supervisor), create the replacement server in the same region, add the sites from their repositories with the same PHP version, restore each database with mysqldump or pg_dump, copy uploads with rsync, then test against the new IP. Lower the DNS TTL to 300 seconds a day ahead. On switch day, put the old site in maintenance mode, run a final database dump, restore it, and change the record. Our guide to deploying Laravel to a VPS covers the per site steps, and the queue worker Supervisor setup covers workers.

What is the best alternative to moss.sh?

For most Moss users the closest match on price is Ploi or Laravel Forge; for mostly WordPress fleets it is RunCloud or SpinupWP; DeployManage fits teams that need multi server atomic releases and many seats. Moss was unusually cheap: unlimited servers, sites and teammates for $9 to $49 a month. Nothing mainstream matches that exactly, so choose by the feature you relied on most.

If you mainly used git deploys on a few Laravel servers, Laravel Forge at $19 or Ploi at $10 to $36 cover it. If your sites are almost all WordPress, RunCloud starts at $9 for one server and $19 for up to 50, and SpinupWP is built only for WordPress. Free self hosted panels exist too, but then you run and patch the panel yourself, which is the job you hired Moss to do. DeployManage starts at $59 and is the right pick when you need one release to land on several servers at once, 10 or more seats with an audit log, or one panel for Laravel, WordPress and Node.js across several clouds.

How much did moss.sh cost?

Moss had four plans: Free at $0, Starter at $9, Professional at $19 and Unlimited at $49 a month, every one with unlimited servers, sites and users. The plans differed in integrations (1, 2, 3 or unlimited), git deploys per month (25, 50, 150 or unlimited) and support level. Monitoring was an add-on of up to $5 per server per month, billed hourly, and paid plans came with a 30 day money back guarantee.

That price floor is why moving hurts: a 10 server fleet on Moss Unlimited cost $49, while the same fleet is $16 on Ploi Pro, $19 on Forge Growth or RunCloud Professional, $49 on RunCloud Business with atomic deploys, and $129 on DeployManage Growth. If you are comparing panels mainly on price, the server management panel comparison lays out every tier side by side.

Moss alternative with zero downtime deploys on several servers

Moss listed zero downtime deployments on every plan. Of the mainstream replacements, Forge does it on one server per site, RunCloud gates atomic deploys to its $49 Business plan, and DeployManage Growth ships one atomic release to every server behind a load balancer. If your app runs on a single server, any of them will do. If it runs on two or three app servers, the release has to be built on all of them before any switches, migrations must run once, and workers on each server restart afterwards.

With Forge that setup needs Envoyer as a second subscription at $10 to $50 a month; our Laravel Envoyer alternative page compares the combined bill. DeployManage Growth at $129 covers 10 servers, 50 sites per server and 10 seats, with the servers created through your cloud's API. Starter at $59 does not include atomic releases, so a Moss user who relied on zero downtime deploys should compare against Growth, not Starter.