SpipCP
Instances

What you can install

The full menu of software SpipCP installs for you — web servers, languages, databases, caches, and site types — with the versions on offer.

SpipCP installs and manages real software for you, inside your instances. This page is the complete menu: the services you install into an instance, and the site types you can launch on top of them. Versions are pinned, installs are clean, and everything is managed through the panel — no manual server setup.

Services (installed into an instance)

You install these from an instance's Services tab. One per category per instance.

Web servers

ServiceVersionsNotes
nginxstableThe default web server.
Caddy2Automatic HTTPS, simple config.
OpenLiteSpeedstableEvent-driven server with built-in LSCache — the alternative WordPress front.
Installing a web server
📷Choosing a web server for an instance.img/install-webserver.avif
Choosing a web server for an instance.

Languages & runtimes

ServiceVersionsNotes
PHP8.5 · 8.4 · 8.3Installed with FPM and Composer.
Node.js24 · 22 · 26For Node apps and build steps.
Python3.13 · 3.12 · 3.11CPython (deadsnakes) with venv, pip and build tools — for Django, FastAPI and Flask apps.
Go1.23 · 1.22Official go.dev toolchain (installed from the pinned, checksum-verified tarball). A build-time dependency only — a Go app compiles to a static binary that needs no runtime.
Rust1.96 · 1.95Installed via rustup (minimal profile), pinned and checksum-verified; build-essential rides along for the C linker cargo needs. A build-time dependency only — a Rust app compiles to a single binary that needs no runtime.

Databases

ServiceVersionsNotes
MariaDB11.8MySQL-compatible, the common default.
MySQL8.4
PostgreSQL18
Installing a database
📷Choosing a database engine; a site can own its own database.img/install-database.avif
Choosing a database engine; a site can own its own database.

Caches / key-value

ServiceVersionsNotes
Valkey9Open-source Redis fork (BSD).
Redis8Note its license at selection time.

Pinned, versioned, verified

Each version is pinned, so an install gives you the same software every time. Every install runs as steps ending in a check — a half-finished install is caught, not left silently broken. Bumping a version is a setting change, not a risky upgrade.

Site types (launched on top)

When you launch a site, you pick a type — a ready-made stack that installs and wires itself up for you:

TypeWhat you get
WordPressA full WordPress install — web server + PHP + database, unique salts, secure file permissions, hardened defaults. Choose nginx (FastCGI cache) or OpenLiteSpeed (LSCache) at create time, and tune PHP limits, OPcache and caching later in the site's WordPress settings.
PHPA generic PHP app on PHP-FPM behind the web server.
StaticStatic files served directly — the simplest, fastest option.
NodeA Node app under a systemd unit that restarts on failure and survives reboots.
PythonA Python app (WSGI via gunicorn or ASGI via uvicorn) under a systemd unit that restarts on failure and survives reboots — see Python sites.
GoA Go app built to a single static binary and supervised by a systemd unit that restarts on failure and survives reboots. A compile error fails the build before the site serves — see Go sites.
RustA Rust app built with cargo build --release to a single binary and supervised by a systemd unit that restarts on failure and survives reboots. A compile error fails the build before the site serves — see Rust sites.
DockerA containerized app run from a docker-compose.yml, per-app with its own port and route — see Docker site types.
Choosing a site type
📷The site types you can launch, each a ready-made stack.img/install-site-types.avif
The site types you can launch, each a ready-made stack.

Every site type can also have a database, domains and TLS, git deploys, backups, and scheduled jobs — see Sites.

→ How installs work: Catalog. · Security defaults: Security.

On this page