Runnable examples for Signadot, which gives every pull request, developer and coding agent an isolated sandbox inside a shared Kubernetes cluster. A sandbox runs only the services you changed. Requests that carry its routing key reach those services, and everything else comes from the shared baseline, so you test against real dependencies without copying the whole environment.
Most examples have a step-by-step tutorial in the Signadot docs that explains how it works and walks through every command.
- Create a free Signadot account. No credit card needed.
- Install the Signadot Operator in a Kubernetes cluster. Minikube or kind works for most examples.
- Install the Signadot CLI
and run
signadot auth login.
New to sandboxes? Create Preview Environments is the shortest path to a first sandbox.
| Example | What it shows | Tutorial |
|---|---|---|
| argocd-tutorial | An Argo CD ApplicationSet giving every agent pull request a sandbox and an e2e check, which the agent reads through the Argo CD MCP server | Test Coding Agent Pull Requests with Argo CD |
| coderabbit-tutorial | Playwright tests in a sandbox on every pull request, with CodeRabbit explaining failures | Diagnose Failing Tests with CodeRabbit |
| devin-tutorial | Devin validating its change to one microservice against the rest of the system | Test Devin's Changes End to End |
| jira-coding-agent-tutorial | From a Jira ticket to a pull request tested in a sandbox, with Bitbucket Pipelines | From Jira Ticket to Tested Pull Request |
| modal-sandboxes-tutorial | A background coding agent in a Modal sandbox testing against Kubernetes services | Modal Sandboxes: E2E Testing for Coding Agents |
| dolt-tutorial | A closed-loop agent workflow with the Signadot MCP server and a Dolt database | In the README |
| closed-loop-comparison | A harness that compares Claude Code with and without Signadot agent skills | In the README |
| Example | What it shows | Tutorial |
|---|---|---|
| apollographql-tutorial | A GraphQL schema change per pull request with Apollo graph variants | Testing Apollo Federation Schema Changes |
| wundergraph-tutorial | A GraphQL schema change per sandbox with WunderGraph Cosmo feature flags | Testing WunderGraph Federated GraphQL Schemas |
Playwright, Cypress and k6 tutorials run against HotROD directly; see Pull Request Testing.
| Example | What it shows | Tutorial |
|---|---|---|
| vercel-preview-signadot-sandoxes-cicd-connection | A Vercel frontend preview wired to a backend sandbox from the same pull request | Full-Stack Vercel Preview Environments |
| collaborative-pre-merge-testing-for-multi-PR-features | One preview for a feature that spans several pull requests and services | Testing Multi-PR Features Before Merge |
| hotrod-ios-app | An iOS app sending a sandbox's routing key to preview backend changes | Preview Backend Changes in a Mobile App |
| argocd-tutorial | An Argo CD ApplicationSet whose hooks create a sandbox for every pull request, run its Playwright suite and report a commit status | Test Coding Agent Pull Requests with Argo CD |
Each consumer version processes only the messages whose routing key is meant for it, so sandboxes share one broker.
| Example | What it shows | Tutorial |
|---|---|---|
| selective-consumption-with-kafka | Kafka, with a consumer group per sandbox | Testing Kafka Microservices |
| rabbitmq-signadot-demo | RabbitMQ, with a queue per consumer version on one exchange | Testing RabbitMQ Microservices |
| SQS-Based-Microservices-with-Signadot-main | Amazon SQS, with a shared queue and SNS fan-out | Testing Amazon SQS Microservices |
| selective-consumption-with-google-pub-sub | Google Pub/Sub, with a subscription per sandbox | Test Google Pub/Sub Flows End to End |
| selective-consumption-with-redis-streams | Redis Streams, with a consumer group per sandbox | Test Redis Streams Consumers |
| debezium-cdc-tutorial | Change data capture with Debezium, with the routing key stored on each row and moved into Kafka headers | Test Debezium CDC Pipelines |
| sidekiq-tutorial | Sidekiq, with a queue per sandboxed worker and the baseline handing each one its jobs | Test Sidekiq Jobs |
| temporal-tutorial | Temporal workers in Go, Java and TypeScript sharing one task queue | Test Temporal Workers |
| dapr-tutorial | Dapr service invocation and pub/sub, keeping Dapr's mTLS | Testing Dapr Services |
| Example | What it shows | Tutorial |
|---|---|---|
| clickhouse-branching-tutorial | A ClickHouse database branch for every sandbox, made by a resource plugin that hard-links the source's partitions | In the README |
| neon-branching-tutorial | A Neon database branch for every sandbox, created by a resource plugin | Neon Database Branching |
| xata-branching-tutorial | A Xata database branch for every sandbox, created by a resource plugin | Xata Database Branching |
Testing a schema change with a temporary MariaDB per sandbox uses signadot/plugins; see Testing Database Schema Changes.
| Example | What it shows | Tutorial |
|---|---|---|
| zap-security-tutorial | A ZAP DAST scan against one change before merge | Run ZAP DAST Scans on Every Change |
| falco-security-tutorial | Falco runtime alerts scoped to a sandbox | Catch Risky Runtime Behavior with Falco |
| Example | What it shows | Docs |
|---|---|---|
| cli | Sandbox, route group, job runner group and job specs to copy | CLI reference |
| instrumentation | OpenTelemetry context propagation inside an app | Context propagation |
| prometheus | Prometheus Operator config to monitor the Signadot Operator | Monitoring |
| sdk | Tests for the Signadot SDKs in Java, Node.js and Python | In the README |
| experimental/custom-routing-with-envoy | Custom routing with an Envoy proxy | In the README |
All tutorials, including ones that need no code from this repository, are at signadot.com/docs/tutorials.
- Questions: ask in the Signadot community Slack.
- Problems with an example: file an issue in the community issue tracker.