Resources

Glossary

These are the terms Stackap uses, in plain English.

Where a term has its own page, the page gives the full detail. These entries are the short version, for readers and for language models that need one unambiguous definition of each word.

Control plane

The part of Stackap that manages everything else: its API, its database of projects and settings, and its background workers.

Project

One application, with its repository, domains, variables, database, schedules and backups.

Organization

A group that owns projects, tokens and git keys, walled apart from every other organization.

Tenant

One organization, seen from the point of view of a platform that serves several of them.

Health check

A request Stackap makes to a new version before it receives visitors. It must answer successfully or the deploy is abandoned.

Approval

A human decision for one risky action. The agent is stopped, the account owner gets a link by a separate channel, and approving covers only that exact request, once, within an hour.

Rollback

Re-activating the previous version of a project, health-checked first.

TTL

Time to live: how long other computers may remember a DNS answer. A long one slows down any change of server.

PostgREST

Software that turns a Postgres database into a web API, used by Supabase and by Stackap.

R2

Cloudflare's object storage, which Stackap uses for backups and uploaded files. It follows the S3 interface and does not charge for data leaving it.

Row-level security

A Postgres feature that restricts which rows a database user may read or change, enforced by the database itself.

Point-in-time recovery

Restoring a database to any chosen moment, not only to the last nightly backup. Planned, not built.

Master key

The one secret from which Stackap's encryption keys derive. Lose it and every encrypted variable and backup is unrecoverable.

Last updated 2026-10-03.