Install and operate the managed server stack.
ServerChirp installs a lean production stack during provisioning and can add supported runtimes or databases later. Managed versions are tested together instead of resolving to whatever package version happens to be current.
| Category | Software |
|---|---|
| Web | Nginx |
| PHP | PHP 8.2, 8.3, 8.4, and 8.5 with PHP-FPM |
| JavaScript | Node.js 22 and 24, Bun 1.3.14, npm, pnpm, Yarn, and Corepack |
| Databases | MySQL 8.4 and PostgreSQL 16 |
| Cache | Redis 8.10 |
| Containers | Docker, Buildx, and Docker Compose |
| Processes | Supervisor |
| Security | UFW and Fail2Ban |
| Tooling | Composer, WP-CLI, and the AWS CLI |
The Services page shows installed versions, running state, CPU use, memory use, and when each status was sampled. Supported services can be started, stopped, or restarted from the dashboard.
Only inventoried, controllable services can receive start, stop, or restart commands. These controls act on the selected system service, so review dependent applications before stopping a shared runtime, database, cache, or proxy.
Open the server's services page and choose Install software. Available choices depend on the operating system and what is already present. The installation runs as a tracked operation and reports progress through the agent.
The inventory distinguishes the installed version from the release managed by the current ServerChirp catalog. Platform-managed packages update through an intentional ServerChirp release; MySQL and PostgreSQL are install-once channels and are not automatically advanced by that catalog.
The ServerChirp agent updates separately. Signed agent updates report progress and can roll back when the replacement binary fails to start.
