Antithesis docs

What is Antithesis

Antithesis is a testing platform that works like an additional staging environment. You ensure your software is reliable by deploying it to Antithesis and running it there before you deploy it to production. It supplements or replaces your existing testing tools and lives alongside your normal CI workflow.

When you deploy to Antithesis, we run multiple copies of your software in a simulation environment that’s much more hostile than prod. This quickly exposes the bugs in your software – even the most complicated, unlikely, and lethal ones. Essentially, it tests your software without you writing tests.

Unlike the shared staging environment you already use, you never have to babysit your system, compete for deployment locks, or worry about what’s changed under you since you last deployed.

And because Antithesis’ simulation is perfectly deterministic, you get perfect, effortless repro of any problems you find.

How to use Antithesis

1. Deploy a containerized production binary (or binaries) to Antithesis just as you would to any other deployment target.
2. Deploy a containerized client – what we call a test template – to Antithesis.
3. Antithesis uses the client to run your software under extremely hostile production conditions, exposing any bugs or unexpected behaviors.
4. Explore what happened during the run by searching across thousands of execution histories, or specify problematic behaviors for which you want alerts.
5. If you need to debug, Antithesis provides detailed artifacts and powerful, one-of-a-kind debugging tools, like a deterministic time-traveling debugger.

What next?

We recommend you read this quick introduction to how Antithesis works under the hood, because the mental model really helps.

Once you’re ready, contact us at support@antithesis.com or ask on our Discord to request a container registry and credentials.

Or, if you’re just exploring and want to see how this is going to fit your workflow, here’s a 5 minute video.