Developers

Documentation

Stackap's documentation is a set of pages organized by task, with the CLI and the API reference as the exact sources for commands and routes.

Start here

• The CLI reference lists every command, how secrets are passed and how failure is signalled.
• The API reference lists every route with its request body and what it returns.
• The agent documentation explains the plain-text site files and the rules an agent should follow.
• The changelog says what has shipped and when.

By task

Ship an app

Read deployments, then the guide for your type of app: Next.js, React, Vite, Astro or Node.js.

Understand what is recognized

The frameworks section says what Stackap detects and builds, and is explicit about what has not been tested.

Operate it

See logs, monitoring, backups and rollbacks.

Move an existing app

See the migration guides.

How to read these pages

Every product page ends with the limits of that feature, stated as plainly as what it does. Framework pages separate what has been built and served from what has only been reasoned about from the code. Comparison pages carry the date their facts about other products were last checked. Nothing is listed as supported until a real project of that kind has been built.

What does not exist yet

There is no public status page, no SDK and no per-endpoint schema file. Request and response shapes are documented in prose in the API reference, which was written by reading the routes themselves. If something here disagrees with what the server does, the server is right and the page is a bug; tell us at hi@stackap.com.

Last updated 2026-10-03.