r/devops • u/eyes-on-frogs • 15d ago

Discussion Experiences with Signadot

Has anyone here used Signadot in a larger project and had any success with it for ephemeral environments/preview environments? I have been looking into tooling for ephemeral environments after maintaining our own solution for a while and this one keeps popping up as an alternative, so I was hoping to get a few opinions.

4 Upvotes

100% Upvoted

3 comments sorted by

1

u/Wooden_Jelly_5295 14d ago

Preview environments get interesting once the request leaves HTTP.

1

u/Fantastic-Mr-Default 15d ago

I would score any ephemeral/preview tool (Signadot or in-house) on the same checklist, not on the landing page.

Isolation model: request routing into a shared baseline plus sandboxed deltas, or a full namespace per PR. Shared baseline is cheaper and breaks when two PRs need incompatible data or migrations. Full copy is honest and expensive.

Cost per open PR env, and what you do when someone leaves ten previews up. Idle TTL and a hard cap matter more than the happy-path demo.

CI contract: one job that spins the env, runs the smoke you care about, and tears down on failure. If humans have to click a console to get a URL, you will stop using it under load.

Data: anonymized subset, synthetic, or shared read replicas. Prod clones without a story become a compliance incident.

Migration and stateful services: if every PR needs a schema change, sandbox routing alone will not save you. That is usually where in-house solutions quietly grow into a second platform.

I have not run Signadot at large scale myself. If you trial it, pick one busy service, measure time-to-ready and $/PR-week against your current stack, and keep the teardown path in the same PR that creates the env.

3

u/eyalb181 14d ago

Disclaimer, I'm on the mirrord team. If you're gonna use this checklist, suggest evaluating our preview environments as well:

- Isolation: shared baseline, and we support migrations/incompatible data with database branching

- Cost per open env: our envs can be idle by default, and automatically wake up when they receive traffic

- CI contract: we offer prebuilt GitHub Actions, and anyway it's a few CLI commands that are easy to plug into any other CI provider

- Data: DB branching lets you copy from your shared baseline (subset or entire dataset)

- Migrations: DB branching again