Integrations

mirrord works with the stack you already run.

Your coding agents, your IDE, your CI, and the queues and databases your services depend on. mirrord connects all of them, and the tools you test with, to your real Kubernetes cluster with no code changes.

The MetalBear bear holds out a laptop covered in stickers and presses a mirrord sticker into the last free spot.

AI coding agents

Any agent that can run a shell command can use the mirrord CLI to run your code against the real cluster, the same way a developer does. The plugins and rules files below add mirrord knowledge on top.

AI evals

Run agent evals against the real dependencies in staging instead of mocks, so an eval score shows how the agent behaves with the services it will actually call.

IDEs

Run or debug against the cluster from the editor, with no separate CLI session to keep alive.

CI/CD

Run integration tests against shared staging, and open a preview environment for every pull request.

Message queues

Queue splitting gives each session only the messages that match its filter, so developers and agents share one queue without taking each other's messages. No code changes.

Databases and storage

DB branching gives each session an isolated branch of the shared database, so schema changes and test writes stay out of everyone else's way.

PostgreSQL

mirrord branches PostgreSQL with schema-only, full, or filtered copies, custom pg_dump arguments, and several databases in one branch.

Read the docs β†’

MySQL

mirrord branches MySQL and can authenticate to the source with IAM on AWS RDS and GCP Cloud SQL.

Read the docs β†’

MariaDB

mirrord branches MariaDB with full or filtered copies and custom dump arguments, such as a single transaction with no table locks.

Read the docs β†’

Microsoft SQL Server

mirrord branches SQL Server as an empty database, the schema only, or a full copy, and can clone only the rows you filter.

Read the docs β†’

MongoDB

mirrord branches MongoDB, and collection filters copy only the documents a session needs.

Read the docs β†’

Redis

mirrord branches Redis in the cluster, including from TLS sources, or runs a local Redis on your machine and redirects your app to it.

Read the docs β†’

DynamoDB

mirrord branches DynamoDB tables, with table filters and IAM authentication.

Read the docs β†’

Google Cloud Spanner

mirrord runs the Cloud Spanner emulator as the branch and points your app at it through SPANNER_EMULATOR_HOST.

Read the docs β†’

CockroachDB

mirrord branches CockroachDB, including from sources that use TLS or mutual TLS.

Read the docs β†’

ClickHouse

mirrord branches ClickHouse as table structures only, a full copy, or a filtered clone.

Read the docs β†’

Amazon S3

mirrord clones the source S3 bucket into a separate branch bucket for each session.

Read the docs β†’

turbopuffer

mirrord clones a turbopuffer namespace into a separate branch namespace for each session.

Read the docs β†’

Developer tools

Point the tools you already test with at the cluster.

Kubernetes platforms

Install the operator with Helm, and target the workloads you already run, with or without a service mesh or an API gateway.

Don't see your tool? Ask in the mirrord Slack community or open a GitHub issue.

Got a question?

Which message queues does mirrord queue splitting support?
Kafka, Amazon SQS, RabbitMQ, Google Cloud Pub/Sub, Azure Service Bus, NATS, Redis Pub/Sub, Temporal, and BullMQ. Each session gets only the messages that match its filter, so developers and agents share one queue without taking each other’s messages. See queue splitting.
Which databases does mirrord DB branching support?
PostgreSQL, MySQL, MariaDB, Microsoft SQL Server, MongoDB, Redis, DynamoDB, Google Cloud Spanner, CockroachDB, and ClickHouse, plus Amazon S3 buckets and turbopuffer namespaces. Each session gets an isolated branch, and the shared database stays as it is. See DB branching.
Can Claude Code, Cursor, or Codex use mirrord?
Yes. Any coding agent that can run a shell command can use the mirrord CLI to run code against your real cluster. The mirrord skills plugin installs in Claude Code, Codex, Cursor, and other Agent Skills agents. See Agent Skills for mirrord.
Does mirrord work with a service mesh like Istio or Linkerd?
Yes. mirrord works the same way with and without a service mesh. It skips mesh proxy containers when it picks a target container, and preview environments handle Istio and Linkerd sidecars automatically. See preview environments and service meshes.
Does mirrord work with an API gateway like Kong?
Yes. mirrord intercepts traffic at the service pod, after the gateway, so your local code receives requests that the real gateway already authenticated and routed. Target the service behind the gateway and filter on the baggage header, which most gateways forward. See Working with API Gateways.
Which Kubernetes workloads and platforms does mirrord support?
mirrord targets Deployments, StatefulSets, Jobs, CronJobs, and Argo Rollouts. It runs on OpenShift too: either change the scc settings, or use the mirrord operator, which works with the default policies. See mirrord limitations.
Does mirrord work with my CI system?
Yes. mirrord ci is a CLI command, so it runs in GitHub Actions, GitLab CI, Jenkins, CircleCI, or any pipeline that can run one. For pull request previews, the mirrord-preview GitHub Action opens a preview environment for each pull request. See mirrord for CI.

Connect your stack to the real cluster.

Start with the free CLI, or talk to us about queue splitting, DB branching, and preview environments for your organization.