Start here

Get started

You ask for an invitation, we create your organization, and your coding agent or your own terminal takes an app from a repository to a live address in a few commands.

What you need

• An application in a git repository. Next.js, a single-page app, a static site, or any Node app with a start script works, and so does anything with a Dockerfile.
• A coding agent that can run shell commands, or a terminal you are comfortable in.
• A domain name, if you want your own address. It is optional: every project gets an address of its own the moment it is created.

How early access starts

You begin as an organization on the Stackap server. That is a walled-off space with its own projects, its own access token, its own git key and its own dashboard sign-in, so nothing you do can be seen by anyone else on the server. If your team later needs a server dedicated to it, that is set up together with you during onboarding. Nobody in early access has to rent or configure a machine to get started.

What a deploy looks like

The timings below are from a real push of this very website to Stackap: 1.2 seconds queued, 1.4 seconds building, 0.3 seconds switching traffic, 2.9 seconds in total. Across the last nine pushes the average was 2.2 seconds. A site this size is the best case, and a large application takes as long as its build does: a 31,592-page Next.js site builds in about 96 seconds.

$ stackap deploy my-app
remote: stackap: build queued
remote: building image ........ ok
remote: health check ......... ok
remote: routing swapped ....... live   previous version kept for rollback

Hand this to your coding agent

Paste the prompt below into Claude Code, Codex or any agent that can run commands. It tells the agent where to read, how to handle secrets, when to stop and ask you, and the exact steps. It uses only commands that exist today.

You are going to deploy an application to Stackap, a platform you operate through its command-line tool and HTTP API.

First read these, in order:
1. https://www.stackap.com/llms.txt
2. https://api.stackap.com/v1/capabilities  (every route, scope and error code; no token needed)

Rules:
- Never put a secret on a command line. Pass secrets on standard input (--stdin).
- If a deploy does not go live, read the build log and then the runtime log before changing any code.
- Ask me before deleting anything and before pointing a production domain at the server.
- If a call answers approval_required, tell me, wait for my decision, then repeat the identical request.

Task:
1. Log in:  stackap login --url https://api.stackap.com --token-stdin   (I will give you the token.)
2. Create a project:  stackap create my-app --name "My App"
3. Set each environment variable:  stackap env set my-app KEY --stdin
4. Deploy:  stackap deploy my-app
5. Read the result:  stackap logs my-app --source build
6. Tell me the live address and what you checked.

The agent will stop and ask you in three places, on purpose: before it deletes anything, before it points a production domain, and whenever the platform asks for a human approval. Everything else it can do on its own.

If something goes wrong

The build fails

The previous version keeps serving. Read the build log with stackap logs my-app --source build; it says what Stackap detected and why it stopped.

The build passes but the app does not go live

The health check failed. Read the runtime log, and check that your app listens on the port in PORT and answers on its health path.

The new version is wrong

stackap rollback my-app brings the previous one back after checking it is healthy.

The push is rejected

Your SSH public key is not registered with your organization yet. We register it during onboarding, or an owner token can do it through the API.

Steps

1. Ask for an invitation. Tell us what you run on the contact page. Early access is limited, and a person replies by email.
2. Receive your organization. You get an access token, shown once, a git key registration and a dashboard sign-in. The command-line tool is provided with your invitation.
3. Give your agent the prompt. Paste the prompt on this page into your coding agent, and hand it the token when it asks.
4. Watch the first deploy. The agent creates the project, sets variables, pushes, and reads the build log. A small site is live in seconds.
5. Add your domain. Attach your hostname and create the one DNS record Stackap shows you. HTTPS switches on by itself once DNS is correct.

Questions

Last updated 2026-10-03.