serveroshq/panel

What it does

ServerOS panel is the web application in the ServerOS stack. It keeps your existing VPS instances with their providers while giving you one interface to deploy apps, sites and databases, watch CPU/memory/disk, install updates, schedule backups, run uptime checks and optional status pages, and keep service logs together. Workflows can run deploy, check and promote steps on a schedule, on a push or manually, and teams get members, roles, two-factor sign-in and an activity log.

Each managed machine runs serverosd, a small AGPL-3.0 daemon that connects out to the panel on port 8443. The panel itself is a Laravel/PHP application; an API and an MCP server let other tools and assistants interact with your servers.

It suits operators who already have Linux servers and want a shared control plane without moving away from their provider or account.

Quick start

Self-hosting needs a Linux server with Docker, ports 80, 443 and 8443 open, plus a domain with two A records: one for the panel hostname and one wildcard for subdomains (workspaces live on subdomains).

On that server, run:

curl -fsSL https://raw.githubusercontent.com/serveroshq/panel/main/docker/self-hosted/install.sh | sudo bash -s -- --domain=panel.example.com --email=you@example.com

The installer adds Docker if needed, runs the official image ghcr.io/serveroshq/panel, and prints a setup code. Open https://panel.example.com, enter the code, and follow the setup for email and the first account. If the code is lost, serveros-panel setup-code prints it again.

Then go to Machines › Connect machine and run the connection command on each server; serverosd will connect back to the panel. The self-hosting guide covers building the community edition, non-Docker installs, upgrades, backups, machine connections and the anonymous daily ping, including how to disable it.

Development setup

For local development you need PHP 8.4, Composer, Node 22 and npm; SQLite works by default. Run composer setup to install dependencies, create .env, generate the key, migrate and build, then composer dev to start the panel, queue worker, logs and Vite together. Because workspaces are served on subdomains, set APP_URL, APP_DOMAIN and SESSION_DOMAIN in .env and open http://serveros.localhost:8000. CONTRIBUTING.md documents tests and CI checks, and docker/dev runs everything in Docker on Linux.

Editions and licensing

The community edition built from this repo is AGPL-3.0 and free. The official image also bundles serveroshq/panel-ee, which stays off until a license key is added; without one it behaves like the community edition. A license enables single sign-on, SCIM, custom roles, custom domains and other paid features without reinstalling. The hosted service at serveros.com runs this same panel for you as a paid offering. The ServerOS name and logo are trademarks and are not covered by the AGPL.

Constraints

• Production self-hosting requires Docker, the listed open ports and DNS for both the panel hostname and a wildcard subdomain; subdomain-based workspaces will not work without the wildcard record.
• The official image contains proprietary panel-ee components under separate terms; only the code in this repository is AGPL-3.0.
• Managed machines must run the serverosd daemon and reach the panel on port 8443.
• First-time contributors must sign a CLA via a pull request comment.

HotRepo's take

ServerOS panel entered HotRepo's new-project list on 2026-11-12, adding 29 stars and 3 forks in a roughly one-hour measurement window while at 142 stars overall. That is a fast start for a young infrastructure project, but the record covers a single short window and no GitHub daily rank, so it does not yet show sustained traction. The more relevant signal for adoption is the split stack: a panel that needs a daemon on every machine, wildcard DNS and an open control port has real operational prerequisites. The source-available community edition plus a paid hosted option is a workable model for teams that want the panel without running it themselves.