Workers IO

Chaitanya Verified account @chaaai · Nov 2

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!

View quoted post on X

Chaitanya Verified account @chaaai · 19h

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.

View quoted post on X

Chaitanya Verified account @chaaai · Nov 2

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!

View quoted post on X

Chaitanya Verified account @chaaai · 5d

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.

View quoted post on X

Max von Hippel Verified account @maxvonhippel · Oct 30

I’m very, very excited to announce that @dartmouth professor and former @DARPA pm @sergeybratus will be giving the opening remarks tomorrow morning to kick off Vibecheck, the formal methods hackathon!

About a decade ago, I went to Sergey’s office and told him I wanted to be a hacker and I loved math. He told me to drop my EE major and switch to pure mathematics — the best foundation for a real hacker. He also gave me an enormous book by Dennis Yurichev on reverse engineering, which meant that hilariously, I was reading about linker/loader internals before I’d ever even tried building a compiler. In fact I learned about C reverse engineering before I learned C. (Not claiming I was any good at it, just that my sequence of exposures to the topics was comedic ..)

Sergey is known for many things but maybe the most fundamental is the co-invention of LangSec, the field of cybersecurity which posits that many — well, most — exploits are in fact parser vulnerabilities, and therefore security should be approached from the perspective of formal language theory. This insight has proved incredibly prescient, predicting vulnerabilities like Pegasus, or more recently the incredible node exploit. But it’s also prescient in another way. More philosophically, we have these language models generating code, and no good way to parse their outputs to determine if the code is safe or not. If you’ll allow me the slight stretch of the formalism I think this is basically a LangSec issue .. and the solution, AI enabled formal methods, is basically a parser innovation. Modulo how do you find specs, which of course is a more nuanced conversation involving HCI and more.

We will have many experts on the floor at vibecheck from folks like @mathematics_inc @theoremlabs @workersio @lanyon_ai and more. But I couldn’t think of anyone I’d rather have open the event than Sergey. See you all at 10am @thegp !

View quoted post on X