Frustrated with Telepresence?
Say hi to mirrord 👋
mirrord brings your cloud cluster to your local machine—without any headaches. No more compatibility issues, sluggish performance, or complex setup. It just works—faster, smoother, and with a user experience built by and for developers.
Why developers prefer mirrord
mirrord and Telepresence both let you run your code locally in the context of your Kubernetes cluster... so what makes mirrord better?
Broader compatibility
Works seamlessly by overriding low-level syscalls on the process level, instead of using a VPN to the cluster. This means mirrord doesn’t care what else is running in your cluster - it simply works.
Granular control
mirrord lets you choose exactly what your process does locally and what it does remotely. This makes mirrord adaptable to a wide range of development environments and use cases.
Quick and easy setup
Setup takes seconds, and works right out of the box without configuring anything. Want proof?
Telepresence
Compatibility challenges
Relies on creating a VPN to the cluster, which can lead to compatibility issues with service meshes, corporate VPNs, or clusters with a high number of pods.
Restricted control
With Telepresence, you’re either connected to the cluster, or you’re not. If your environment is nonstandard in anyway, you will likely hit a roadblock.
Complex setup process
Unlike mirrord, which automatically configures your local process using your remote pod, Telepresence requires additional manual setup for each new microservice, adding extra steps to your workflow.
The mirrord
Speedrun Challenge
You can get mirrord running in minutes in any environment -- no matter how complex.
Curious about mirrord but don't want to set anything up? We'll do it for you -- fast.
“Then I tried mirrord and it was flawless. It does everything I liked about Telepresence but better. I especially love how customizable it is; it works with almost no configuration, but it allows for a great deal of customization should you want it.”
Brooke Weaver
Staff Software Engineer | Vivint
How does mirrord compare to Telepresence?
Connect your local process to Kubernetes
Works without root permission
Supports both traffic mirroring and interception
Configurable: Choose what runs locally vs. on the cluster
Compatible with clusters of any size
Works without restarting the remote service
Doesn't require a sidecar
Supports connecting to clusters over a corporate VPN
Why devs are switching to mirrord
“mirrord abstracts away the complexities for developers who may not have deep knowledge of Kubernetes or the networking stack”
“[mirrord] has significantly improved our development experience, making the team happier and more efficient.”
“We are using mirrord... to debug issues and test local changes, in our shared staging environment, without impacting other developers. ”
“Instead of asking every developer to create and fill a local environment, we have a single large remote one that is used by everyone.”
“[With mirrord] the service is running locally (fast iterations) but still receives all the cluster access including databases, credentials, configuration.”
“With the use of mirrord and its extensions, we were able to [debug a complete workflow], significantly improving the development feedback cycle.”
I’m ready.
How do I make the switch?
Switching to mirrord is very easy—start your free account and try it out yourself, or book a call with us if you're moving a large team and have custom needs.
or if you have any questions, send us a message
