Welcome to Antithesis
0. What is Antithesis?
Antithesis is a tool for verifying that your software works as intended. It supplements or replaces your existing testing tools and lives alongside your normal CI workflow.
Antithesis works like an additional staging environment. 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 — which is vital if you’re going to keep up with AI writing code.
Unlike a conventional shared staging environment, 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.
1. How does Antithesis work?
We have a whole page about this. It’s a concise explainer of the key concepts behind the product: state space exploration, property-based testing, simulation testing, and more.
If you’re new to Antithesis, having a clear mental model of what Antithesis is doing really helps, so we recommend reading that next.
2. Who uses Antithesis? What can I test with Antithesis?
Antithesis is primarily used by developers building stateful distributed systems, with coding agents or by hand. Antithesis offers a CLI, API, and a plugin which make it usable by any agent.
If you’re interested in testing program logic at the application level, we also offer Hegel, a universal property-based testing engine and family of libraries. Hegel is open source and available in many different languages.
If you’re interested in testing a web or terminal UI, we offer Bombadil, an open-source property-based testing tool.
We also offer agent skills for both Hegel and Bombadil.
3. How do I get my software into Antithesis?
Your software needs to be packaged as Linux container images orchestrated using Docker Compose or Kubernetes.
Antithesis runs your software in a hermetic simulation environment — meaning no internet access at all. Anything your system needs must either be packaged into the environment or mocked appropriately.
Our plugin will take care of setup — including containerization and uploading dependencies — for you.
Setup guide | The Antithesis environment | Handling external dependencies | Docker best practices | Kubernetes best practices
4. How do I test my software?
Antithesis tests your software by running it (and your dependencies, your workload, and your checkers) in a fault-filled environment, and then analyzing what happens.
Along with your system, you’ll need to upload a driver (a.k.a. workload) which exercises your system and check its behavior.
The easiest way to create a driver is to have the plugin write one for you.
Writing tests | Using the plugin | Creating test templates | Asserting correctness
5. How do I get my results?
Antithesis streams your test results via API or webapp, so you (or your agent) can start debugging as soon as your test encounters a failure.
Antithesis provides two types of output: the raw logs of every execution path, and an evaluation of whether each property asserted passes or fails.
We also provide an interactive, searchable visualization of what happened during each test run.
6. I found a bug, now what?
In addition to detailed reproductions of every issue, Antithesis provides two powerful debugging tools: Causality Analysis, which allows you to see which events in your system are associated with a particular bug becoming much more likely, and the Multiverse Debugger, which allows you to time-travel to pull information, and do destructive analysis on the execution path.
We also have a handy guide to how all these tools come together, and when to reach for each one.
7. How do I sign up?
Once you’re ready, you can sign up for an account, request a demo, or join our Discord to ask the community questions.
Or, if you’re just exploring and want to see how this is going to fit your workflow, here’s a 5 minute video.
Getting Started with Antithesis
We strongly recommend using our agent plugin to drive Antithesis.
The plugin needs Docker or Podman with Docker Compose, jq, and Snouty CLI.
# Check Docker (or Podman) with Compose, and jqdocker compose versionjq --version
# Install the Snouty CLIcurl --proto '=https' --tlsv1.2 -LsSf https://github.com/antithesishq/snouty/releases/latest/download/snouty-installer.sh | shThen install the plugin:
Claude Code
claude plugin marketplace add antithesishq/antithesis-pluginclaude plugin install antithesis@antithesisCodex
codex plugin marketplace add antithesishq/antithesis-plugincodex plugin add antithesis@antithesisUsing Devin or Replit? See the Devin or Replit setup.
Recommended models
We test and use the plugin mainly with Claude Opus 5.5 at medium effort, and recommend it. Other models, such as OpenAI Sol, work, but have been seen to issue many safety refusals because the plugin comprehensively tests and fuzzes software. Access to OpenAI Daybreak or Anthropic’s Cyber Verification Program makes such refusals less likely.