Your whole stack, live, on every pull request.

Stackyard builds a full environment — database, services, app and edge — from each branch and posts its URL on the pull request in about 90 seconds.

Median build time
94 smedian push to live URL
Environments per branch
1:1one environment per branch
Idle cost
$0while an environment sleeps

Stop sharing one staging server between twelve branches.

Staging breaks the moment two pull requests need different migrations. Stackyard gives every branch its own copy of production's shape, then throws it away when the branch merges.

01

One environment per pull request

Open a pull request and Stackyard boots the full stack from that branch: schema, services and app. Reviewers click a link instead of checking out code and running seed scripts.

pr-482.stackyard.dev94 s medianteardown on merge
02

Real data, safely masked

Each environment restores last night's production snapshot with emails, names and card numbers rewritten. A 40 GB database mounts in 18 seconds on copy-on-write volumes.

pii maskingcow restore 18 spg · mysql
03

Asleep after 15 idle minutes

Environments sleep when nobody is looking and wake on the next request in about three seconds. You pay only for the hours someone actually used.

wake 3.1 sidle cost $0per-second billing

Four layers, five steps, about 90 seconds.

Every push runs the same pipeline, and each step only redoes work when its inputs changed.

  1. 01

    Clone the commit

    Stackyard checks out the exact commit and reads stackyard.yml from the repository root.

  2. 02

    Restore the data

    A masked production snapshot mounts as a copy-on-write volume, then your migrations run against it.

  3. 03

    Start the services

    Redis, queues and search boot from the same images your Docker Compose file already names.

  4. 04

    Build the app

    Builds reuse the previous commit's layers, so a typical change rebuilds in about 40 seconds.

  5. 05

    Route the edge

    The edge issues a certificate, wires the preview URL and comments the link on the pull request.

stackyard.yml9 lines
# one file, committed next to your code
data:
  snapshot: prod-nightly
  mask: [email, name, card_number]
services: [redis, nats]
app:
  build: ./Dockerfile
  port: 3000
sleep_after: 15m

Plugs into the tools you already run.

Stackyard reads your Git host, builds the containers you already have and reports back where your team already looks.

  • SourceGitHub, GitLab, Bitbucket
  • RuntimeDocker, Kubernetes manifests, Nixpacks
  • DataPostgres, MySQL, Redis
  • WorkflowSlack, Linear, Jira

Priced by the environment-hour.

Sleeping environments, build minutes and seats don't count. You pay for the hours an environment is awake and serving requests.

Hobby

For side projects and solo reviewers.

$0/ month

150 environment-hours a month, two running at once.

hover or tap for details

Hobby includes

  • 150 environment-hours per month
  • 2 concurrent environments
  • Snapshots up to 1 GB
  • Sleep after 15 idle minutes
  • GitHub and GitLab
  • Community support
Start free

Scale

For organisations with security reviews.

$1,800/ month

40,000 environment-hours included, then $0.04 each.

hover or tap for details

Scale includes

  • 40,000 environment-hours a month
  • $0.04 per hour beyond that
  • Runners inside your own VPC
  • SAML SSO and audit log export
  • SOC 2 Type II report
  • 99.9% uptime SLA
Talk to sales

Billed monthly in USD · metered per second · $0 while an environment sleeps

Preview your next pull request.

Install the app, push a branch, and a working URL lands as a comment on your next pull request.

Connect GitHub $npx stackyard init

GitHub · GitLab · Bitbucket — SOC 2 Type II