Early access is open. Stagd is free during the beta. Sign up

Changelog

New features and fixes in Stagd, newest first.

  1. Sign in with Googlenew

    Reviewers without GitHub sign in with their Google account, and land in the same account as before when the address is the same. Settings → Account → Ways to sign in adds or removes GitHub and Google.

  2. Seeds pick the newest file that matchesnew

    A seed’s path can be a pattern: dumps/*.dump uses the newest .dump file in that folder at each deploy. A folder path (dumps/) now passes over files without an extension, such as a latest file a backup job writes beside its dumps.

  3. Your previews in the terminalnew

    stagd ui (CLI v0.15.0) shows your workspace’s previews in the terminal, laid out like k9s: a table by status, refreshed every two seconds. Describe one, follow its logs, open it or its pull request, wake it, or destroy it after a confirm. stagd ui --demo shows made-up previews to try it. Update with stagd update.

  4. An activity log for the workspacenew

    Settings → Activity shows who changed what, a sentence per change, by day: secrets (by name, never values), seeds, compute, integrations, repositories, GitHub, members and invites. Filter it by area and person, there or with stagd activity --area --actor. Press G L, or search ⌘K for it.

  5. The way to a first preview, on Home and for agentsnew

    Home leads with the steps to a workspace’s first live preview, the next one open with why it matters. The same steps are on the API and the MCP server: run the setup prompt (/mcp__stagd__setup in Claude Code) in a checkout, and your coding agent takes it from there to a live preview. See Coding agents.

  6. A preview's status at a glancenew

    A preview’s Overview opens with where it stands: the step it’s at and for how long, each finished step with its time (Queued, Restoring data, Building, Starting, Live), and each service on its way. Builds read like Logs, in the same pane, and the pages in front of a preview, such as Starting or Sign in, look like Stagd.

  7. Hidden and write-only secretsnew

    A secret is visible, hidden or write-only, and new ones are write-only unless you choose otherwise. Admins can show or copy a hidden value, and each time they do it’s in the activity log. Generate makes a random value in the browser, with the encoding and length you pick.

  8. Storage and Namespace without stored keysnew

    Azure Blob Storage, Amazon S3, Google Cloud Storage and Namespace can trust Stagd itself instead of a key you paste: Stagd signs a short-lived token for your workspace, and your cloud swaps it for access. Nothing secret is stored at Stagd. See Sign in as Stagd.

  9. A status pagenew

    status.stagd.dev shows whether Stagd is up, and any incident as it happens. The website’s footer shows the current status, and the CLI and the page shown while Stagd restarts link to it.

  10. Choose when previews startnew

    Pull requests get a preview on demand (/stagd deploy), every time, or when they have a label. Set it for the workspace in Settings → Previews, for a repository on its Settings tab, or with stagd preview policy --start.

  11. Rename, hand on and delete a workspacenew

    Admins rename a workspace in Settings → General, or with stagd orgs rename; its URL stays. Each workspace has an owner, who alone may delete it. A deleted workspace is gone for its members at once and kept for 30 days in case you want it back. Anyone can now have as many workspaces as they like.

  12. Which secrets your app still needsnew

    Stagd reads the ${NAME} references in your compose file and stagd.yaml and tells you which have no value yet, on the repository’s Secrets tab. A preview that starts with an empty secret says which one, and a failed build’s pull request comment shows the end of its log, with the error’s line first.

  13. Testers and checked sign-insnew

    Name the users Stagd signs in as under testers in stagd.yaml, and how your app signs people in under sign_in. A sign-in is either a form Stagd fills in, with a fixed test code or the code or link from the email your app sends, or headers with an API’s token. stagd preview testers <id> --check signs in to the live preview as each tester and shows how each step went, with a screenshot of the page where a sign-in stopped. The preview’s Overview lists the testers and how to sign in as them, and members can check the sign-ins from there. See testers.

  14. A fork of your blob storage in every previewbeta

    services: { azure_blob: { from: [lab-files] } } gives a preview a copy-on-write fork of your Azure Blob Storage containers, and s3 does the same for S3 buckets: your app reads every file of the real ones, and what it writes or deletes stays in the preview. Nothing is copied up front. It runs blobfork, open source, in front of Azurite or Floci.

  15. Migrations on Kubernetesbeta

    Services that run once, like a migration your app waits for, now run on Kubernetes too: as a Job, with the rest starting once it’s done.

  16. Mail sent through Resend or SESnew

    With mail capture on, emails your app sends through Resend’s or Amazon SES’s API land in the preview’s inbox too. No code changes: Stagd points their SDKs at its mock.

  17. Leave one way of sending mail alonenew

    Mail capture catches every way your app sends, and ways Stagd learns later too. services.mail.skip names the ones that should reach the real vendor, such as mail: { skip: [ses] } for an app whose own SES calls the mock doesn’t answer. skip: [resend, ses] runs Mailpit alone.

  18. MySQL, MariaDB and MongoDBbeta

    List them under services next to Postgres. Each is seeded from its own dump, and your app gets the connection URLs it expects.

  19. Stagd checks the Namespace token's grantsnew

    Connecting Namespace checks that the workspace token has every grant Stagd uses, and says what it can’t do without the missing ones. Connect compute has the nsc command that makes the token with exactly those grants.

  20. Postgres extensionsnew

    List them under services.postgres.extensions: Postgres’s own, and any the PostgreSQL apt repository packages, such as pgvector, PostGIS, pg_cron and TimescaleDB. Stagd installs them as the database starts and makes them before your seed restores. The ones that load at start are preloaded for you.

  21. New commits keep data on Kubernetes and Docker hostsnew

    A new commit now deploys into the preview’s namespace or compose project, as it does onto its Namespace instance, so its databases keep their data and a Docker host keeps its build cache. On Kubernetes, what waits for a build keeps running the last commit until the new one is built.

  22. Seeds from the CLI, and on every databasenew

    stagd seeds lists, adds, changes and removes seeds, and finds the file a path picks. A preview with several databases shows each one’s seed. Home warns admins 30 days before an Azure SAS token ends.

  23. Sleeping previews keep their datanew

    On compute that can’t pause a preview, Stagd keeps its volumes while it sleeps and puts them back when it wakes, so its database comes back as it was.

  24. A stagd.yaml referencenew

    Every setting in stagd.yaml on one page, Postgres extensions included. Point your editor at https://stagd.dev/schema/stagd.schema.json to have it complete and check the file as you type.

  25. Text messagesnew

    Add sms under services, and text messages your app sends through Amazon SNS show on the preview’s Messages tab instead of reaching a phone.

  26. Seeds from your blob storenew

    Connect Azure Blob Storage or an S3 bucket and pick a seed on the Seeds page. A path ending in / always picks the newest dump.

  27. Sleep and expiry per repository

    Set lifecycle.sleep_after and expire_after in stagd.yaml to override your org’s defaults.

  28. Capture mail

    Add mail: {} and everything the preview sends stays in a Mailpit inbox for reviewers. Nothing is delivered.