Workers IO

Simulation environments for verifying mission critical software. Backed by @ycombinator and @solofounders

[Workers IO @workersio]

Software is going to become 100x safer, faster, and cheaper

Let's fix all of the internet!

[Chaitanya @chaaai]

Today I'm announcing Workers IO to solve the slowest part of engineering, verification!

AI agents can now write years’ worth of code in days, but it still takes significant engineering effort to verify what’s being built.

It’s impossible to predict all scenarios that could lead to a failure and that’s why most expensive failures are found in production.

Workers IO runs millions of simulated production scenarios on your entire system, including dependencies. These simulations run inside a deterministic hypervisor which injects faults like network delays, disk errors, clock skew, and process failures to verify how your system handles these conditions.

Deterministic execution allows us to systematically explore the state space of the system and perfectly reproduce failures.

We are already helping customers do years worth of production hardening in days and build confidence in what they’re shipping.

If you are working on systems that you can never afford to break, DM me and we can help you battle test them!

[Chaitanya @chaaai]

It's insane how fast small AI pilled teams move, we onboarded this team 2 days ago and they are now the fastest team when it comes to shipping fixes.

It's also a good signal for us because it shows we are surfacing things that directly impacts their business not just an intellectual exercise.

[Mehul Arora @infiniter3grets]

https://t.co/O6m7AJ4nbi

[Chaitanya @chaaai]

Every time I convince myself I understand our market, some crazy inbound appears with a use case like verifying software for power inverters!

We are so early in this, @workersio going to be the most important vendor for so many businesses.

[Chaitanya @chaaai]

We're making software verification super fun and accessible for everyone with @workersio

Almost every customer we've worked with for over 30 days has expanded across multiple teams or projects.

[Mehul Arora @infiniter3grets]

if you haven't tried @workersio 🔥, you're missing out!

[shikhar @shikhrr]

Very high signal reports! It helps that this is on a new system so we can iterate much quicker than if it was in prod already.

[Workers IO @workersio]

These guys know what they are doing!

[Chaitanya @chaaai]

You know a team is going to win BIG when they speed run every issue we report in one weekend.

Yall should check out @s2_streamstore a top-tier team building a top-tier streaming product.

[Workers IO @workersio]

@chaaai Speedrun “fixing the internet”

[Chaitanya @chaaai]

Exactly why we are building @workersio to help teams speed run turbulent times, reach an ideal reliability faster and maintain it!

[Workers IO @workersio]

When working with our customers, two of the most important things are -

1. Minimize the amount of compute spent to find failure scenarios that are important to our customers

2. ZERO false positives

Just helped close 10+ critical/high severity issues for a infra company that served 10s of millions of user requests a day.

Just getting started, we are going to push the bar for software quality really really high!

[Chaitanya @chaaai]

Today I'm announcing Workers IO to solve the slowest part of engineering, verification!

AI agents can now write years’ worth of code in days, but it still takes significant engineering effort to verify what’s being built.

It’s impossible to predict all scenarios that could lead to a failure and that’s why most expensive failures are found in production.

Workers IO runs millions of simulated production scenarios on your entire system, including dependencies. These simulations run inside a deterministic hypervisor which injects faults like network delays, disk errors, clock skew, and process failures to verify how your system handles these conditions.

Deterministic execution allows us to systematically explore the state space of the system and perfectly reproduce failures.

We are already helping customers do years worth of production hardening in days and build confidence in what they’re shipping.

If you are working on systems that you can never afford to break, DM me and we can help you battle test them!

[Workers IO @workersio]

@shikhrr We are working with at-least one of them ;)

[Chaitanya @chaaai]

Not saying I have PFM but it’s not uncommon for us to sign annual contracts and angel checks in the same email.

[Solo Founders @solofounders]

@chaaai Be sure to check out @workersio and our conversation with Chai from last week! https://t.co/jirj8e2uwW

[Workers IO @workersio]

@vishctx @TaliaRinger Thanks 🫡

[Workers IO @workersio]

+1

[Chaitanya @chaaai]

I feel that is the wrong hill to climb on, the point is not to just "formally verify" the code.

BUT to make sure we help teams develop understanding of their systems and then verify things that they care about.

DST or FV, the hardest part is often coming up with the right properties to work with. It's very easy to verify the wrong things, or even worse things that has no business outcomes tied to them.

[Chaitanya @chaaai]

Hot take: code review and running agent generated tests will become obsolete.

It's just matter of time, we will make DST and FV so accessible and cheap to use that this will become the default way people will build any kind of software.

[Workers IO @workersio]

@chaaai

[Ananya Grover @AnanyaGrover1]

the bottleneck in software engineering isn't writing code anymore. it's knowing whether the code actually works under real-world conditions.

huge kudos to you @chaaai for tackling such an important problem. excited to see Workers IO out in the world! 🚀

[Workers IO @workersio]

1. We are an entirely different product. We don’t use agents to test your product; if anything, we find far more interesting things than LLMs do.

2. Web / API / MCP

3. We look at the state of the entire system and use the signals you can expose from your product to explore the state space. This is handled by our own orchestrator (not an agent).

We do use LLMs for narrowly scoped tasks.

[Dhravya Shah @DhravyaShah]

every serious software company will need a correctness system - workers io is an insane product and has enabled us to move faster