Company

Reliability

Stackap protects a running site from bad deploys, watches itself, and proves its backups restore.

What protects a running site

• A new version never receives traffic until it passes a health check, so a bad build or a crashing container leaves the old version serving.
• Rollback is one command and health-checks the earlier version first.
• A project can run up to eight copies behind a load balancer with failover. A copy that was killed during a test caused no failed requests.
• Docker logs rotate, and a daily job prunes old build cache and images, so a disk does not fill silently.

What watches it

A monitor checks the platform and every project, including backups and the control plane, and sends alerts to Telegram. A failing check repeats its alert every six hours until it is resolved, so a missed message is not a missed problem.

What has been proven

• Backups of every project database and of the control plane are restore-verified, and restoring onto a separate machine using only the bucket and the master key has worked.
• One real Next.js site has been copied onto Stackap and compared with the live original, with 26 pages and 64 sampled sitemap URLs identical.
• A load test on one 4-CPU server reached roughly 700 requests per second on real pages with no errors.

What is next

Early access runs on one server in one region, with daily backups. The roadmap adds a full rebuild drill on a fresh machine, point-in-time recovery and a standby server. The steps for a full rebuild are written down in a runbook, and the drill is how that runbook gets proven.

Last updated 2026-10-03.