Product

Product

Stackap is one server that does the work of several subscriptions: deploys, HTTPS, databases, storage, domains, scheduled jobs, backups and monitoring.

Stackap is one server that does the work of several subscriptions: deploys, HTTPS, databases, storage, domains, scheduled jobs, backups and monitoring.

Each page below describes one part of the product: what it does, how it works, and what it does not do yet. Pages for the rest of the platform are added as they are written, and nothing is listed here until it is true.

Pages in this section

• Deployments: How Stackap deployments work: a git push is built into a Docker image, health-checked beside the old version, and only then switched live.
• Databases: How Stackap gives each project its own Postgres database and role, a Supabase-compatible data API, a table browser, and what it does not yet offer.
• Storage: How Stackap stores uploaded files in a Cloudflare R2 bucket you own, served by the open-source Supabase storage service, and what is verified so far.
• Domains: How Stackap attaches custom domains: one DNS record you create, a DNS check before issuing a certificate, automatic HTTPS, and expiry monitoring.
• Cron jobs: How Stackap runs scheduled jobs by calling a path on your app, imports vercel.json crons, records every run, and what the schedule semantics are.
• Environment variables: How Stackap stores secrets: AES-256-GCM encryption bound to project and name, values masked when listed, stdin-only input, and how build-time values work.
• Logs: How to read Stackap build logs and live runtime logs from the CLI or API, the size limits and rotation, and what is not collected.
• Monitoring: The checks Stackap runs on itself, how alerts reach Telegram, the per-project load-time metrics, and the blind spot of a monitor on the same machine.
• Backups: How Stackap backs up databases and repositories to a bucket you own, encrypts them, and proves they restore, plus the gaps that remain.
• Rollbacks: A Stackap rollback re-activates the previous deployment with one command, health-checking it first. What it restores, and what it cannot.
• Scaling: How Stackap scales an app by running 1 to 8 copies behind a load balancer on one server, the measured throughput, and what multi-server scaling still lacks.
• Agent-first infrastructure: What agent-operable infrastructure means in practice at Stackap: commands, an HTTP API and plain-text docs an agent can use without a human in the loop.

Last updated 2026-10-03.