MetalBear

“Even the simplest local development setup for us previously was a multi-day effort, and now it’s a couple of hours from a brand-new MacBook to getting things running.”

“With mirrord we’ve increased what we call our ‘say-do ratio’ - what engineers say they’ll do and what they actually get done.”

“There’s a lower defect rate. We are producing better code faster right now. And I really do think having mirrord and having the ability to bridge into the cluster network like that has facilitated it.”

“We’ve increased our feature velocity overall. Teams can now focus on the features and capabilities of the product rather than the process.”

“It took us less than a day to get it deployed, and it very much fit our operational model of how we treat Kubernetes, how we support it, and how we upgrade it. Everything worked just perfectly right from the start.”

“We’re engineers, so we thought we could solve it. But it’s a very complex problem, and not our core business.”

“We've reduced the time from when an engineer builds something to when it's deployed - because when they test locally, it is a true approximation of our production environment.”

“We are not pushing them to use mirrord. Everyone is asking for it.”

“When I’m working with mirrord, I don’t have to compromise between speed and confidence. I get both.”

“Before mirrord, a lot of developers were afraid of setting up their local development setup. I think mirrord removed that fear.”

“With mirrord, we shifted development onto a real environment with real data, without paying the cost of provisioning a separate environment for every developer.”

“People are happier developing on mirrord. It's quicker, it's leaner, it's closer to them.”

“Our team uses Cursor to write the code, and mirrord to test it in pre-prod - in seconds. Together, it’s a complete dev loop.”

“If the tool isn’t dead simple and totally reliable, developers will avoid it. With mirrord, they don’t even think about it. It just works.”

“Without mirrord, testing a single change would take 5 to 8 minutes. Multiply that by 10+ times a day - that’s at least an hour lost, per developer. With mirrord, it takes 5 seconds.”

“We’re testing against the real environment before merging. That level of fidelity gives us high confidence in every release.”

“We’re going to use a lot more AI agents per developer. That means we need to be supervising that work. And mirrord is going to help us do that.”

“The biggest change is giving us confidence, sending out agentic loops like Claude Code or Codex to do their work, and actually verifying that logically and visually the work is done.”

“Checking a real change in Daylight in our dev environment would be around 5 seconds.”

“Code is done, PR is green, preview environment is live. We get a link and we put that into the mirrord extension. We can just see all of the changes. It can see all of its changes, and then we have more confidence going from PR to production.”

“If you need to wait 5 minutes till you can actually test something, you’ll wait until you have multiple changes that you want to test. You’ll double-think everything because you want to act fast. We’re running fast here.”

“There’s so much code being written, and what do you do after that? If you don’t have the right setup, if you don’t have the right mechanisms in place after that code is written, you’re just in a pile of code that you can’t manage.”

“The difference between an AI agent that just outputs code and an AI agent that I can trust is one that can see its changes, an AI agent that can test its changes.”

“The difference between an AI agent that just outputs code and an AI agent I can trust is one that can see its changes, an AI agent that can test its changes.”

“There’s nothing more frustrating than working on a system without the support to get it running. But when everything works, and you can focus on coding, you’re actually making progress on the business,”