> For the complete documentation index, see [llms.txt](https://metalbear.com/mirrord/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://metalbear.com/mirrord/docs/release-stages/feature-matrix.md). # Feature Support Matrix See which platforms and infrastructure support mirrord's advanced features — DB Branching, Queue Splitting, Preview Environments, and Multi-cluster. Some of mirrord's advanced features - DB Branching, Queue Splitting, Preview Environments, and Multi-cluster - work across a range of platforms and infrastructure setups. Support levels vary by platform. The table below shows the current status for each combination. #### The columns reflect the different contexts in which a feature can be used: * Preview Env: using the feature inside a [preview environment](https://github.com/metalbear-co/docs/tree/main/docs/reference/use-cases/preview-environments.md). Each developer or agent gets an isolated slice of the dependency - for example, their own queue partition or database branch — within a shared staging cluster, without affecting others. * Multi-cluster: using the feature across [multiple clusters](https://github.com/metalbear-co/docs/tree/main/docs/reference/using-mirrord/multi-cluster.md). Traffic, queue messages, or database connections are routed across cluster boundaries, useful when your infrastructure spans more than one cluster. * mirrord up: using the feature when running multiple services together via [mirrord up](https://github.com/metalbear-co/docs/tree/main/docs/reference/using-mirrord/multiple-concurrent-sessions.md). Similar to how `docker compose` orchestrates containers, mirrord up lets you define and launch several interdependent microservices in a single `mirrord-up` file, managing their lifecycle as a group. | Feature | Platform | Preview Env | Multi-cluster | mirrord up | | ----------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- | ----------- | ------------- | ---------- | | [**DB Branching**](/mirrord/docs/sharing-the-cluster/db-branching.md) | [**PostgreSQL**](/mirrord/docs/sharing-the-cluster/db-branching/postgresql.md) | `Alpha` | `Alpha` | Planned | | | [**MongoDB**](/mirrord/docs/sharing-the-cluster/db-branching/mongodb.md) | `Alpha` | `Alpha` | Planned | | | [**MySQL**](/mirrord/docs/sharing-the-cluster/db-branching/mysql.md) | `Alpha` | `Alpha` | Planned | | | [**MariaDB**](/mirrord/docs/sharing-the-cluster/db-branching/mariadb.md) | `Alpha` | `Alpha` | Planned | | | [**MSSQL**](/mirrord/docs/sharing-the-cluster/db-branching/mssql.md) | `Alpha` | `Alpha` | Planned | | | [**Redis**](/mirrord/docs/sharing-the-cluster/db-branching/redis.md) (both local and remote) | `Alpha` | `Alpha` | Planned | | | [**DynamoDB**](/mirrord/docs/sharing-the-cluster/db-branching/dynamodb.md) | `Alpha` | `Alpha` | Planned | | | [**ClickHouse**](/mirrord/docs/sharing-the-cluster/db-branching/clickhouse.md) | `Alpha` | `Alpha` | Planned | | | [**CockroachDB**](/mirrord/docs/sharing-the-cluster/db-branching/cockroachdb.md) | `Alpha` | `Alpha` | Planned | | | [**Google Spanner**](/mirrord/docs/sharing-the-cluster/db-branching/spanner.md) | `Alpha` | `Alpha` | Planned | | | [**turbopuffer**](/mirrord/docs/sharing-the-cluster/db-branching/turbopuffer.md) | `Alpha` | `Alpha` | Planned | | | [**Generic**](/mirrord/docs/sharing-the-cluster/db-branching/generic.md) (user-supplied image) | `Alpha` | `Alpha` | Planned | | [**Queue Splitting**](/mirrord/docs/sharing-the-cluster/queue-splitting.md) | [**SQS**](/mirrord/docs/sharing-the-cluster/queue-splitting/sqs.md) | `Alpha` | `Alpha` | Planned | | | [**Kafka**](/mirrord/docs/sharing-the-cluster/queue-splitting/kafka.md) | `Alpha` | `Alpha` | Planned | | | [**RabbitMQ**](/mirrord/docs/sharing-the-cluster/queue-splitting/rabbitmq.md) | `Alpha` | `Alpha` | Planned | | | [**Temporal**](/mirrord/docs/sharing-the-cluster/queue-splitting/temporal.md) | `Alpha` | `Alpha` | Planned | | | [**Google Pub/Sub**](/mirrord/docs/sharing-the-cluster/queue-splitting/gcp-pubsub.md) | `Alpha` | `Alpha` | Planned | | | [**Azure Service Bus**](/mirrord/docs/sharing-the-cluster/queue-splitting/azure-service-bus.md) | `Alpha` | `Alpha` | Planned | | | [**NATS**](/mirrord/docs/sharing-the-cluster/queue-splitting/nats.md) | `Alpha` | `Alpha` | Planned | | | [**NATS Pub/Sub**](/mirrord/docs/sharing-the-cluster/queue-splitting/nats.md#core-nats-pubsub-no-jetstream) | `Alpha` | `Alpha` | Planned | | | [**Redis Pub/Sub**](/mirrord/docs/sharing-the-cluster/queue-splitting/redis-pubsub.md) | `Alpha` | `Alpha` | Planned | | | [**BullMQ**](/mirrord/docs/sharing-the-cluster/queue-splitting/bullmq.md) | `Alpha` | `Alpha` | Planned | | [**Preview Env**](/mirrord/docs/use-cases/preview-environments.md) | — | — | `Alpha` | Planned | | [**Multi-cluster**](/mirrord/docs/using-mirrord/multi-cluster.md) | — | `Alpha` | — | Planned | | [**mirrord up**](/mirrord/docs/using-mirrord/multiple-concurrent-sessions.md) | — | `Alpha` | `Alpha` | — | *Not sure what Alpha, Beta, or GA means? See* [*Release Status*](/mirrord/docs/release-stages.md) #### Didn't find what you are looking for? [Open a GitHub issue](https://github.com/metalbear-co/mirrord/issues) or reach out in the [mirrord Slack community](https://metalbearcommunity.slack.com/ssb/redirect) and tell us what you're working with, we prioritize based on demand. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://metalbear.com/mirrord/docs/release-stages/feature-matrix.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.