Stackyard builds your app, its services and a masked copy of your database for each branch, posts the URL on the PR, and tears everything down the moment you merge.
$ npx stackyard init
Illustration: an exploded stack of four layers — data, services, app and edge — that together form the preview environment for pull request 482.
features
One shared staging server means a queue, a Slack thread about who broke it, and reviewers approving screenshots. Stackyard gives every branch its own copy of production-shaped infrastructure.
Every push to an open PR rebuilds its own isolated stack at pr-<n>.<app>.stackyard.dev. No staging queue, no "who deployed over my branch".
Each environment mounts a copy-on-write branch of your nightly Postgres or MySQL snapshot. Masking rules rewrite emails, names and tokens before anyone can query them.
Idle environments sleep after 30 minutes and wake on the next request. Merge or close the PR and the whole stack is destroyed — containers, volumes and the database branch.
how it works
Stackyard reads the docker-compose.yml you already have plus a short stackyard.toml. Every push rebuilds only the layers that changed.
A copy-on-write branch of last night's snapshot, ready in under 4 s regardless of size. Masking runs before the branch mounts.
api, worker and redis start from your compose file — same images, same ports, a private network per PR.
Your web app builds with layer caching shared across branches. Median rebuild after a push: 38 s.
pr-482.acme.stackyard.dev with TLS, an optional SSO gate and per-branch environment variables.
A GitHub check goes green and the bot comments the URL on the PR. Merge or close it and the stack is destroyed.
# stackyard.toml [preview] compose = "docker-compose.yml" expose = "web:3000" [data] snapshot = "nightly" mask = ["users.email", "users.name"]
integrations
Install the app on your Git host, point Stackyard at a compose file or Helm chart, pick a snapshot, and send notifications where your team already talks.
pricing
Sleeping environments don't count. Every plan starts with a 14-day Team trial, no card required.
Hobby
$0/month
For side projects and trying Stackyard on one repo.
100 env-hours included
hard cap, no overage
↻ hover, focus or tap for details
Hobby includes
Team
$49/month
For product teams shipping several PRs a day.
600 env-hours included
then $0.04 per env-hour
↻ hover, focus or tap for details
Team includes
Scale
$299/month
For platform teams with compliance and network needs.
3,000 env-hours included
then $0.03 per env-hour
↻ hover, focus or tap for details
Scale includes
An env-hour is one running environment for one hour. Sleeping environments are billed at $0.
Connect a repository and your next pull request ships with its own URL, its own services and its own database — in about a minute and a half.