Status labels
The labels on this page are a summary. Feature status holds the evidence tiers behind them.
Deploy sources
Builds
Ruby and PHP projects get a plan from Railpack, but the docs say no live build has run for either. Other providers Railpack detects are rejected with an error.
Databases and backups
Compose database dumps run on a cron schedule. Restoring one is a manual step today. The compose apps page lists the commands.
Networking and ingress
The Proven on a real host row covers one recorded issuance, on 2026-10-05, against a public CA on a public VPS, using the staging CA first and then production. Renewal, DNS-01 wildcard issuance and the port 80 preflight from outside the server are not verified. See the ACME runbook for the record.
The SSH deploy key, request body cap and runtime options rows marked Proven on a real host cite a 2026-11-08 run on an arm64 Ubuntu VM (build 243a8ee00). The body cap run covered the proxy path only, not the dashboard control, and the deploy key run covered trust-on-first-use pinning only. See Feature status.
Previews
Security
Multi-server
App controls
Observability
Other gated features
These are the rest of the experimental catalog. Each one is switched on separately. The other seven catalog entries appear in the sections above.Keeping this page current
When a capability changes, update its row in the same change. The Experimental labels should matchinternal/experimental/catalog.go, and Beta labels follow Feature status. A new Proven on a real host row needs a recorded run in the docs first.