Case Study Laurel's software factory: 6x the PRs at a 75% lower incident rate. Read the case study.

Signadot vs Release

The Release (ReleaseHub) alternative that copies only what changed

Release copies your whole stack for every pull request. Signadot gives local development, PRs and coding agents one model: ephemeral environments that copy only what changed and share the rest.

Trusted by engineering teams worldwide

  • Brex logo
  • Miro logo
  • Wealthsimple logo
  • Bitso logo
  • Qlik logo
  • SoFi logo
  • Earnest logo
  • Care.com logo
  • InfoTrack logo
  • Quizlet logo
  • OnBoard logo
  • Calendly logo
  • Lightspeed logo
  • Storyblocks logo
  • OutSystems logo
  • Luxury Presence logo
  • Posh AI logo
  • Juniper Square logo
  • Leadr logo
  • Nox Health logo
  • Favor Delivery logo
  • Laurel logo

Signadot vs Release: six key differences

Both give each pull request an environment to test in, but they are built differently. Release copies the whole environment, every service and database, and runs the clusters for you. Signadot copies only what a change touches and shares the rest, so environments stay fast and cheap as your app grows. The complete guide to preview environments compares Release with the other preview platforms.

Feature Signadot Release
Foundation

One model, the ephemeral environment, for local dev, PRs and agents. Copies only what changed.

Copy the whole environment for every PR.

Coding agents

Agents on laptops or in the cloud each get an ephemeral environment for Jobs and Plans.

An API for agents, and a full-stack copy for each one.

PR environments

Ready in seconds. Hundreds share one cluster.

A full stack per PR. Cost grows with every service.

Databases, queues and more

Any database or queue. Resource plugins add anything else.

A database copy per environment. Queues run inside each copy.

Service mesh and Gateway API

Native on Istio, with no extra sidecar. Gateway API and Linkerd too.

None in its docs. Routing is NGINX ingress by host and path.

Testing: Jobs and Plans

Jobs run your tests. Plans let agents build test workflows.

None. You run your own tests against it from CI.

When to choose Release

A fit when your app is small enough to copy in full.

  • Your app has a handful of services
  • You want every PR to get a standalone copy, with nothing shared
  • You want a vendor to run the clusters in your cloud account

When to choose Signadot

The choice when copying the whole stack for every PR is too slow or too costly.

  • Dozens or hundreds of services
  • Local dev and PR environments on one model
  • An ephemeral environment for every coding agent, local or in the cloud
  • Any database or queue, plus resource plugins
  • Built-in testing with Jobs and Plans
  • A free Starter plan to get going

The bottleneck has shifted from writing code to proving it works.

Agents write code faster than teams can check it. Signadot gives every change its own environment with real services and data, so your tests and agents can show it works.

The Signadot platform

Four pillars of the Signadot platform

Signadot spins up an ephemeral environment for every code change, from a developer's laptop to thousands of coding agents, so your tests and agents can check it against your real services, databases and message queues.

Built for Agents

Run thousands of agents in parallel.

Each agent gets its own lightweight ephemeral environment, cheap and fast to spin up, so agents run more validations on their own before human review.

Unified Architecture

Inner and outer loop, one platform.

The same ephemeral environment covers local development and PR validation. One platform. One mental model.

Comprehensive Coverage

Smart Tests, Jobs and Plans, built in.

Jobs run your existing tests. Plans let agents build test workflows. All of it runs in your cluster.

Deep Isolation

Data, queues and cloud resources.

Share a database or branch it per ephemeral environment. Queues stay shared, with messages routed by key. Resource plugins create cloud resources outside Kubernetes.

Testimonials

Hear from our customers

Brex logo

$2M saved annually

On the margin, with the Signadot approach, 99.8% of the isolated environment's infrastructure costs look wasteful. That percentage looks like an exaggeration, but it's really not.
Connor Braa, Software Engineering Manager at Brex Connor BraaSoftware Engineering Manager
Bitso logo

83% lower change failure rate

We basically stopped creating full preview environments and replaced our custom solution with Signadot. Instead of isolating the full environment, the strategy using routing keys is much lighter, and we are able to provide an isolated environment, even with isolated databases, per PR quite fast.
Marcus Tavares, Staff Software Engineer at Bitso Marcus TavaresStaff Software Engineer
Wealthsimple logo

No more fighting over staging

Creating a sandbox is extremely fast, it works every time, lets me test what I'm building quickly, and move on. This is awesome.
Tyler Marien, Senior Software Developer at Wealthsimple Tyler MarienSenior Software Developer
Miro logo

10x integration capacity

Our engineers were spending more time waiting for an environment than shipping. Now they test against our real services in parallel, which made a whole tier of fixed test infrastructure unnecessary. Retiring environments we had carried for years is projected to save us several million dollars annually.
Jony Jeyaratnam, Head of Engineering at Miro Jony JeyaratnamHead of Engineering

Coding agents

Built for agentic development

Most code is now written by coding agents, on laptops and in the cloud. Each one gets its own ephemeral environment to test in, the same kind a developer uses.

  • An MCP server and agent skills that work across the coding agents your teams use
  • Background agents running in cloud sandboxes get their own ephemeral environment too (see the Modal example)
  • Jobs and Plans that run in each agent's environment
Set up Signadot for coding agents

Testing

Run the tests too, with Jobs and Plans

Signadot runs your tests too. Release does not.

  • Jobs run the test suites you already have
  • Plans let agents build automated test workflows
  • Your platform team picks the Plans every change must pass
See Plans in action

Cloud native stack

Works with your service mesh

Signadot routes through the mesh you already run. On Istio it adds no sidecar of its own: it updates your VirtualService rules and Istio does the routing.

  • Istio, natively, in sidecar or ambient mode
  • Gateway API: routes beside your HTTPRoutes and GRPCRoutes
  • Linkerd or no mesh: a lightweight DevMesh sidecar
  • OpenTelemetry baggage carries the routing key
How request routing works

Deployment and security

Runs in your cluster

Most of Signadot runs in your cluster.

Need fully self-hosted? Talk to us.

  • Only resource metadata leaves your cluster by default
  • Never your code, app data or production PII
  • SOC 2 Type II
Read the security docs

Built for Developers and Agents

Works with your coding agents

Claude Code logoCursor logoOpenAI logo

Integrate with CI tools you already use

jenkins logoGitLab logoGitHub logoBitbucket logo

Support all test frameworks

Cypress logoSelenium logoCucumber logok6 logoPostman logoPlaywright logo
Signadot is making it easier for our developers to build and test microservices using deployments that are incredibly similar to production. This has made both human and AI-written code easier to validate and test.
Naomi Klein, Lead Infrastructure Engineer at Laurel Naomi KleinLead Infrastructure Engineer at Laurel

Frequently asked questions

Release vs Signadot: what's the difference?

They take opposite approaches. Release copies the whole environment for each PR and runs the clusters for you. Signadot copies only what changed and plugs it into one shared environment, so hundreds of environments run on one cluster. Full copies suit small apps. Copying only what changed suits apps with many services.

Is Release the same as ReleaseHub?

Yes. ReleaseHub is the earlier name of Release. releasehub.com now redirects to release.com.

Does Signadot work with databases and message queues?

Yes, with any database or queue. Resource plugins create a database for each environment, using tools you already use. Queues stay shared, and each message reaches the right environment. The same works for Temporal. The complete guide to ephemeral environments compares the approaches. Release copies or branches a database for each environment, and runs queues inside each copy.

Is Signadot self-hosted?

Signadot is hybrid. Most of it runs in your cluster, with a small cloud control plane that only sees resource metadata by default. Need fully self-hosted? Talk to us.

Does Signadot see my code or data?

No, not by default. Only resource metadata, such as names and status, leaves your cluster: never source code, images or application data. Optional features send more, encrypted at rest. Signadot is SOC 2 Type II. See the security docs.

Does Signadot require a service mesh?

No. Without a mesh, or with Linkerd, a lightweight DevMesh sidecar routes each request to the right environment. If you run Istio, Signadot updates the routing rules in your VirtualServices and adds no sidecar of its own, in sidecar or ambient mode. It also works with the Gateway API. The routing key travels in the OpenTelemetry baggage header your tracing libraries already pass along.

Can coding agents use Signadot?

Yes. Coding agents such as Claude Code and Cursor connect through Signadot's MCP server and agent skills. Each agent gets its own ephemeral environment, whether it runs on a developer's laptop or as a background agent in the cloud, and runs Jobs and Plans against it before anyone reviews the change.