Skip navigation
Introducing Workers IO
0:00 / 0:45

Introducing Workers IO

Workers IO

@workersio1.3K followers

Visit on X
634 likesDownloadOriginal post

65,835 views

Introducing Workers IO Agents are making it possible to turn ideas into software faster than ever. To keep up with that, we need better ways to understand how our software will behave in real-world. Workers IO runs your entire system through millions of simulated futures, exploring what happens when machines fail, networks slow down, and events arrive in the wrong order. It searches for the combinations that break your system before your customers encounter them. Every failure it encounters is perfectly reproducible, helping teams understand what happened, work on a fix, and verify against the same scenario. This ability changes what teams are willing to take on. Difficult engineering decisions become things that you can explore and verify. That’s the future we’re working toward: small teams building increasingly ambitious systems, with the evidence to stand behind. I can’t wait to see what you build with that confidence.

49 Comments

Comments from the original post on X (Twitter)

  • Dhravya Shah's profile picture

    @DhravyaShah

    Insane video and to think you made it yourself!

    10 likes

  • Workers IO's profile picture

    @workersio

    We do everything in house just like Supermemory 🕺🕺🚀

    5 likes

  • prateek - orchestrator.inc's profile picture

    @agent_wrapper

    this is fire! Need of the moment.

    5 likes

  • xevrion's profile picture

    @xevrion_the1

    This is so good and will completely change how software is verified!!🔥

    4 likes

  • Connex's profile picture

    @Connex01

    Congrats on the launch, I'm kinda curious about how the simulations actually work though.

    4 likes

  • Workers IO's profile picture

    @workersio

    We have a hypervisor, workload + input generators and fault models that are used to design scenarios that are then run in parallel.

    1 like

  • Connex's profile picture

    @Connex01

    Ok I see. Thanks for clarifying.👍

    1 like

  • Aapakari's profile picture

    @aapakari

    Reproducible failures as the default is the bit I'd lean on hardest, congrats.

    3 likes

  • Workers IO's profile picture

    @workersio

    Yes, shrinking & reproducibility is something that we spent a lot of time on.

  • Prasanna's profile picture

    @_prasanna_ap

    this is amazing🔥

    3 likes

  • Vardhman's profile picture

    @flcrom

    Holy shit that video was insane! video production team deserves a shoutout

    3 likes

  • Soham Daga's profile picture

    @sohamdaga22

    super straightforward and clear, love to see it

    3 likes

  • Workers IO's profile picture

    @workersio

    good abstractions :)

    1 like

  • Tejas's profile picture

    @tejasktwt

    This is 🔥🔥

    3 likes

  • Workers IO's profile picture

    @workersio

    Let’s make every software unbreakable!

    1 like

  • Vlad Korobov's profile picture

    @terpimost

    great video

    3 likes

  • Workers IO's profile picture

    @workersio

    I'll go thank Claude for it :')

  • Divvyansh Gandhi's profile picture

    @DivyanshGandhi

    @aaron_epstein I have been waiting for something like this since I first heard about load testing

    2 likes

  • r/69's profile picture

    @r69shabh

    can it narrow a failure down to the smallest sequence that still breaks it?

    2 likes

  • Workers IO's profile picture

    @workersio

    Yes we have spent a lot of time on shrinking

    2 likes