The mirrord CLI, VSCode and IntelliJ Plugins mean that they can embrace the Remocal Future and experience modern development with mirrord for Teams from the comfort of their current setup.

mirrord for Teams lets developers concurrently access staging resources throughout the entire development process, not just when the code is “ready for Staging.”

When a typical cloud developer wants to see how their work will perform in staging and production, they `git push`, trigger CI/CD, and wait. And wait – and this kills progress and innovation.

Fire up your service from your laptop, and it will act 100% like it is running in k8s in staging – mirrord makes getting started contributing to a complex services-based Kubernetes architecture as easy as cloning a repo and installing a CLI tool (or IDE extension!).

mirrord works on the principle of “setup once, and love forever.” Once a service is running with mirrord, everyone who can clone the repo will automatically enjoy the benefits of using the service Remocally.

mirrord is easy to explain, but there’s a lot going on behind the scenes to make it work like magic. Cloud developers can fire up the CLI tool and develop against full staging traffic, disks, queues, DNS, and more – as if they had the full Staging cluster running on their local machine.