Stackr Documentation

Publish a starter

The pilot supports a landing page and a JSON Status API. Sign in with a pilot invite, create a project, choose a starter, and publish. Open the project URL to see the active release.

Leave the address blank for a generated name. Enter a repository URL to use its name when available. You can change the address in the project dashboard.

Deploy from a terminal or Git CI

Download Stackr CLI

Use Node.js 22 or later. In deployment history, create a project token. Store the endpoint and token in your CI system as STACKR_DEPLOY_URL and STACKR_DEPLOY_TOKEN. Run the command below on pushes to your deployment branch.

node stackr.mjs deploy launch.json --tag v1 --stage

Example launch.json:

{
  "template": "landing-page-v1",
  "title": "My app",
  "message": "We are live."
}

Supported templates are landing-page-v1 and status-api-v1. The CLI can run in GitHub Actions, GitLab CI, Bitbucket Pipelines, or another CI runner.

Preview, promote and roll back

A staged release leaves live traffic on the current version. Open Preview in deployment history, then choose Make live to promote the release. Choose Make live on an earlier release to roll back. Release tags are unique within a project.

node stackr.mjs status https://YOUR_APP_URL

Pilot limits

One project per account, 30 releases per project, and 10,000 requests per account each UTC calendar month. Project usage is visible in the dashboard. Repository discovery and general code builds require additional provider setup.

To manage Zo.gy routing and load balancing, open the Zo.gy dashboard.