R_F retweeted
On ECS, the usual way to find out whether a change works is to deploy it. You build the image, push it, register a new task definition revision, wait for the rollout and look at what happened, then do it all again if it's wrong.
This week we launched mirrord for ECS which changes that.
- Your code can now run on your laptop, in your CI runner or in your coding agent's sandbox as if it were a live task in your staging environment, with the task's network, environment variables and IAM task role.
- It reaches the same databases, queues, and internal and external APIs as the deployed service.
- Only the requests that carry your session header come to it, so you, your teammates and your agents can each run your own version of the service at the same time, on the staging environment you already share.
It works on Fargate and EC2, and it's free to get started (no Kubernetes needed).
Learn more here: metalbear.com/mirrord/ecs
R_F retweeted
We've been talking about mirrord for ECS nonstop this week, but if you're one of those people who can only grasp ideas when they're presented in the form of a game, we have good news for you.
metalbear.com/mirrord/ecs/gaβ¦
The top 3 on the leaderboard by 24th November 2026 win mirrord swag!
R_F retweeted
mirrord supports ECS now. Brave new world.
If your services run on @awscloud ECS, you know the loop. You build the image, push it, register a new task definition and wait for the rollout. Only then do you find out whether your change works, and if it doesn't, you do it all again.
This week we launched mirrord for ECS which collapses the loop. Write code, then immediately test in staging.
@EBukchin wrote about how it works and what testing on ECS looks like now: metalbear.com/blog/stop-deplβ¦
#aws #ecs #containers
R_F retweeted
If your services run on @awscloud ECS, you know the loop. You build the image, push it, register a new task definition and wait for the rollout. Only then do you find out whether your change works, and if it doesn't, you do it all again.
This week we launched mirrord for ECS which collapses the loop. Write code, then immediately test in staging.
@EBukchin wrote about how it works and what testing on ECS looks like now: metalbear.com/blog/stop-deplβ¦
#aws #ecs #containers
R_F retweeted
For years, weβve had to turn away eager ECS teams because mirrord was Kubernetes-only. But no more.
mirrord for ECS is now live on every plan, including Free.
@aviramyh explains why it matters even more with coding agents: an agent writes a change in seconds, then waits a full rollout to find out it needs another try π
Coding agents write a change in minutes. Testing it on AWS ECS still takes hours.
Every team on ECS we've talked to describes the same loop: build the image, push it, register a new task definition revision, wait for the rollout, check what happened, and do it all again if it's wrong.
That was already too slow for humans, but it's so much worse for agents who write a change in seconds, then have to wait a full rollout to learn whether it worked.
Most of the speed you got from the agent ends up spent on waiting for rollouts.
On Kubernetes, mirrord fixed this a while ago. 20,000+ developers use it along with their AI agents to test generated code against their real staging environment without deploying it.
Today we're going beyond Kubernetes with the launch of mirrord for ECS.
β’ Your code runs on your laptop or in an agent's sandbox, but it gets real traffic, environment variables, network access, and files from your ECS task in staging. You see if a change works in seconds, not after a rollout.
β’ To set it up, it's just one task definition change.
β’ Only requests that carry your session header come to your code, so you, your teammates and your agents can each test your own version of the service at the same time, on the staging environment you already share.
mirrord for ECS is live today, and itβs free to get started with! Let your agents test against real staging without deploying, and without getting in anyone else's way.
R_F retweeted
The Cognition team hit the classic Staging Bottleneckβ’, so they migrated all their services so they could run locally, + mocked all their 3rd party APIs.
For teams who, well, don't want to do that, there's mirrord. Fast, isolated agent sessions against staging = no bottleneck.
R_F retweeted
Coding agents write a change in minutes. Testing it on AWS ECS still takes hours.
Every team on ECS we've talked to describes the same loop: build the image, push it, register a new task definition revision, wait for the rollout, check what happened, and do it all again if it's wrong.
That was already too slow for humans, but it's so much worse for agents who write a change in seconds, then have to wait a full rollout to learn whether it worked.
Most of the speed you got from the agent ends up spent on waiting for rollouts.
On Kubernetes, mirrord fixed this a while ago. 20,000+ developers use it along with their AI agents to test generated code against their real staging environment without deploying it.
Today we're going beyond Kubernetes with the launch of mirrord for ECS.
β’ Your code runs on your laptop or in an agent's sandbox, but it gets real traffic, environment variables, network access, and files from your ECS task in staging. You see if a change works in seconds, not after a rollout.
β’ To set it up, it's just one task definition change.
β’ Only requests that carry your session header come to your code, so you, your teammates and your agents can each test your own version of the service at the same time, on the staging environment you already share.
mirrord for ECS is live today, and itβs free to get started with! Let your agents test against real staging without deploying, and without getting in anyone else's way.
R_F retweeted
Day one at @TheLeadDev #Berlin was full of live demos, meeting customers, and a lot of coffee!
It's the last day today, so come find us at booth 103 for a demo of agents testing against a real cluster, or grab some mirrord sleep masks while they last! π»
R_F retweeted
With AI generating more code than ever, focus has shifted to testing. But the solution to the testing problem isn't one size fits all. Read our latest blog to learn the best tools you can use for different phases of testing + what testing environment to consider based on your needs.
Read here: metalbear.com/blog/best-micrβ¦
R_F retweeted
World class engineering teams like @PodiumHQ βs use mirrord (by @metalbear ) to power their autonomous coding agents.
If youβre serious about building an incomparably fast agentic workflow that delivers high quality software with minimum human intervention, you should too.
We built a $150M ARR business twice.
The first time took 8 years. The second took 2.5.
Today, Podium crossed $150M in AI annual recurring revenue.
Three years ago, we already had a great software business. Well over $100M in revenue, tens of thousands of customers, and a product we'd spent nearly a decade building.
And we decided to start over.
The business was performing well. But we believed AI was going to fundamentally change the software industry and make much of traditional software obsolete.
As a founder, you pour your life into what you're building. An insane amount of time, sacrifice, and effort. The hard part is not getting too attached to it.
When we started building our first AI agents, we had to confront the possibility that much of what we'd built might not be that valuable in the future. That's a tough pill to swallow.
But we also realized those same 10 years had put us in a unique position to take advantage of what AI could do for our customers.
Instead of protecting what we'd spent a decade building, we decided to bet the future of the company on AI employees that actually do the work for our customers.
We massively underestimated what we'd signed up for.
We ended up building entirely new operating systems for the industries we serve, from the AI agents all the way down to the systems of record. Now customers run their entire businesses on Podium.
Reinventing our product wasn't even the hardest part. We had to reinvent how the entire company operated.
When you've been running a company for over a decade, the operational inertia is incredibly powerful. We had to rethink how we build products, how we sell, how we serve customers, and how we run the business.
We effectively started a second startup inside an already successful company. And we're still at the very beginning.
Today, we have 20,000 AI agents working for our customers. They've helped generate more than $13 billion in revenue for those businesses. And we're barely scratching the surface of what AI will be able to do for them.
And we've done all of this while becoming profitable and generating free cash flow. We're building Podium to be around for decades.
Huge credit to our team for having the guts to make this bet and the ability to actually pull it off. We still have a long way to go and tons of problems to solve, but it's so damn fun to be winning when the opportunity ahead is this big.
In the age of AI, you can either disrupt your own company or wait for somebody else to do it.
I'd rather do it ourselves.
R_F retweeted
Good news for anyone who wants to make their agent evals faster, cheaper, and more accurate by running them against real dependencies!
The recording from our webinar with @dorco8 on how they do evals at @mondaydotcom is now available here: metalbear.com/events/agent-eβ¦
R_F retweeted
Replying to @deedydas
@deedydas suggest solving it with old ways - more compute, more efficiency, more cache. Beyond amount of CI needed, there's almost no value in UT when using AI while tremendous value lies in E2E.
None of the listed companies help you run E2E better/faster.
The biggest cost of E2E is spinning up a real-environment.
our (@metalbear) approach with mirrord offers something different - give each test/ai/engineer a slice of a real environment, isolating flows allowing infinite scale while almost zero cost (beyond compute needed for the tests). Use it in CI, in CD and in the cloud agents it selves to have everyone iterating against same baseline.
for example - metalbear.com/mirrord/case-sβ¦
or @fagamericano who writes a lot about it (also mirrord user :D)
As cost of coding has plummeted, long builds (CI) has become a bottleneck for many software cos. Three of the biggest startups solving this:
1. Blacksmith (@useblacksmith)
2. Namespace (@namespacelabs)
3. Depot (@depotdev)
R_F retweeted
Take a read π
This week @dorco8 and @EBukchin's webinar left such an impression on me that I ended up writing a blog about :P
If you missed the webinar (or prefer text over video) and want to learn how @mondaydotcom runs its agent evals read the blog here: metalbear.com/blog/monday-agβ¦
R_F retweeted
If you're considering building or vibe-coding an in-house solution for Kubernetes dev environments, check out our latest blog by @RinkiyaKeDad
We're a little biased as a vendor, but we tried to be as honest as possible about:
- the 90% of the work that comes after the prototype
- what it really costs
- how to decide whether buying or building is the right call
Read here: metalbear.com/blog/build-vs-β¦
R_F retweeted
Attending KubeCon Japan?
Come stop by our booth (SU9) to learn how mirrord letβs you have autonomous AI agents that can test their own code in @kubernetesio π€
We have some cool swag and a Minesweeper leaderboard competition going on as well!
R_F retweeted
"I feel more comfortable in what I ship now because we can test our code in staging using mirrord and get a sense of how the feature will behave, which gives us a lot of confidence."
β Reut Levy, Software Developer at @mondaydotcom
These are the results monday.com saw after adopting mirrord:
β±οΈ Environment setup dropped from 30 minutes to 10 seconds
π° Recurring cloud costs for dev environments eliminated entirely
π§βπ» A single shared cluster now serves 350+ engineers
π
New developer onboarding went from 3β5 days to about an hour
Read the full case study: metalbear.com/mirrord/case-sβ¦
R_F retweeted
"After @claudeai finishes its task, a mirrord Preview Environment is spun up and then anybody on the team can come and review it."
β Itay Hilel, AI Automation Engineer at Daylight Security
Watch Itay Hilel and Shira Lev from @DaylightSec share how their team tests every change made by Claude Code and @OpenAI's Codex. With mirrord Preview Environments, it all happens in a production-like environment, safely and with zero extra infra π
Read the full case study here: metalbear.com/mirrord/case-sβ¦
R_F retweeted
"The biggest improvement we saw was in 'wake-up time,' which we define as the moment a developer wants to start developing until they can actually start. We saw a 10x speed increase, and it really made a difference!"
β Marek Pelka, Engineering Manager at @mondaydotcom
Read the full case study to learn how mirrord changed the way development happens at @mondaydotcom:
β±οΈ 30 minutes β 10 seconds to set up an environment
π
3β5 days β ~1 hour to onboard a new developer
π° Recurring cloud costs for dev environments β $0
π§βπ» 245+ engineers, all on a single shared cluster
Read here: metalbear.com/mirrord/case-sβ¦
R_F retweeted
Earlier this week, to celebrate the launch of mirrord for Windows, we put up a Minesweeper game we vibe coded with a leaderboard and prizes for top scorers. It was hacked almost immediately.
But when life gives you lemons, you write blog posts about them. Read more about Minesweepergate here: metalbear.com/blog/minesweepβ¦




















