mirrord vs. Bridge to Kubernetes

Looking for a B2K alternative?
Say hi to mirrord 👋

Microsoft discontinued Bridge to Kubernetes, but your cloud development workflow doesn't have to stop. mirrord offers everything B2K did — and more — with a simpler setup, broader compatibility, and active development.

"I tried Telepresence, Bridge to Kubernetes, and others and mirrord worked with our AKS setup best. mirrord has cut our "deploy-loop" issues and time tremendously. mirrord is a game changer for our development team!"

Concerned about making the transition from Bridge to Kubernetes?

1

Same approach, simpler setup

If you're used to the configuration processes in B2K, you'll appreciate how mirrord simplifies connecting your local process to any Kubernetes cluster — without the need for complex setup. Simply download one of the mirrord IDE extensions or the CLI tool and you're good to go!

2

More control, no extra effort

mirrord offers more control and flexibility over how your local and remote environments interact. You can choose exactly what your process does remotely and what happens locally — whether it's the files it reads, environment variables, or even which hosts/IPs it connects to locally or on the cluster.

3

Similar process, more use cases

You can keep your usual development workflow, even with complex or high-scale Kubernetes setups. While B2K limits traffic redirection to single-pod, single-container services, mirrord enables seamless operation across multi-pod deployments, allows multiple developers to work in the same cluster concurrently, and handles strict network policies by routing outgoing traffic from the local process through the remote pod.

Some of the companies already using mirrord

monday.com SurveyMonkey NAB Harness Personio Mercari League
Get started

Switch to mirrord today and keep your workflow uninterrupted

Making the move is easy — start with a free trial or talk with our team. We'll help you get set up in minutes.

Read the docs →