Managing usage

Teams plans include 2,400 pre-paid compute hours each month, and on-demand hours are billed at $2.50/compute-hour on a monthly cycle.

You can set limits on usage from the usage page in the web app. When you hit a usage limit, you won’t be able to start new sessions, though in-progress sessions will run to completion.

What’s a compute hour?

A compute hour is a CPU-hour of work in Antithesis. Antithesis runs all tasks in massive parallel, so you can expect a wall-clock hour of testing to consume many compute hours, generally 48 or more. The advantage of this is that you get over a full day (or 2, or 4) of testing time in a single wall-clock hour.

What counts towards my usage?

The following activities consume compute hours:

• Running a test
• Running a causality analysis
• Using multiverse debugging

Running a test

Running a test consumes a variable number of compute hours per wall-clock hour, based on the performance tier chosen.

Higher performance tiers increase parallelism to explore your system’s state space faster, and consume more compute hours per wall-clock hour.

The time required to initialize the system under test does not count towards compute consumption. Compute consumption is calculated from the moment fuzzing starts.

Running a causality analysis

Running a causality analysis consumes 48 compute hours per wall-clock hour by default.

Each causality analysis requires a small amount of setup time to rewind to the moment of interest, which does count toward usage.

Using multiverse debugging

Multiverse debugging sessions consume 48 compute hours per wall-clock hour.

Multiverse debugging sessions last 6 wall-clock hours (288 compute hours) by default, and users can cancel the session once they’re done.

Each multiverse debugging session requires a small amount of setup time to rewind to the moment of interest, which does count toward usage.

Managing usage

You can set limits on how many compute hours users (including agents) on your account can use. When you hit a usage limit, you won’t be able to start new sessions, though in-progress sessions will run to completion, and be billed at the applicable rate.

You can also manage these limits from the settings page.

Monthly limit

Caps how many on-demand compute hours you can use each month. Defaults to 4,000 compute hours, max allowable 20,000 compute hours (contact us if you want more!). You are only billed for on-demand hours that you actually use.

Daily limit

Caps how many compute hours you can use each day, expressed as a proportion of your total monthly limit (including both pre-paid and on-demand hours).

Concurrency limit

Limits the number of concurrent Antithesis sessions you can run, across all session types (tests, multiverse debugging, causality analysis). Defaults to 5. Contact Antithesis support if you’d like to change this: support@antithesis.com