Antifailure
GitHub
Sign inRequest a demo
Pricing

Antifailure pricing.

Run the open-source engine for free, or add hosted reporting and coordination for your team.

  • Community

    $0
    local engine, forever

    The open-source engine on your own infrastructure.

    Start the quickstart
    • MIT licensed, installed with one command
    • Docker Compose and basic Postgres support
    • The MCP server, af mcp, for a coding agent
    • Bring-your-own infrastructure and model keys
    • Inspectable agent, sanitization, egress, and cleanup
    • No account and no key. Your cloud, your credentials

  • Team

    $500
    per month · one organization

    Shared reporting and coordination for your team.

    Request a demo
    • Flat platform fee per organization, not per person
    • Up to 50 members, counting invitations not yet accepted
    • Included run credits for deployment twins
    • Usage for environment minutes, data volume, and workload execution
    • Run test environments in your own cloud
    • Pull-request checks and aggregated reports across repositories

  • Enterprise

    Illustrative
    $2,000 to $8,000
    per month · Enterprise band
    Annual contract
    $30,000 to $250,000+
    annually · scale, governance, and where environments run

    More repositories, organization policy, and the controls enterprises buy.

    Talk to us
    • More repositories, volume, and peak workload
    • Up to 1,000 members, counting invitations not yet accepted
    • Organization-wide release policy
    • Residency, so environments run only in the regions you name
    • Single sign-on and SCIM, in the enterprise edition you run
    • Discuss support and service-level requirements

Community runs on your own compute. Team is billed per organization plus usage. Enterprise pricing is indicative; contact us for a quote.

Free plan

Included in the free hosted plan.

The local engine has no environment or hour quota. The limits below apply to free organizations using the control plane, including its default self-hosted configuration.

At the limit, you cannot create a new environment until capacity is available. Existing environments keep running.

  • Live environments
    3
    at once

    Environments that exist and have not been torn down. The fourth is refused until one of the three is gone, and nothing that is already running is ever taken away.

  • One run may commit to
    24
    environment-hours

    The lifetime a single dispatch may ask for. A day is the default runtime.ttl, so one environment for one branch is never refused, and a thirty day lifetime asked for in one call is.

  • Any rolling day may accrue
    72
    environment-hours

    The total across a moving twenty four hours, not a calendar day. It is what stops a workflow that creates an environment per push from running up a month of environment time in an afternoon.

Value metrics

Usage follows your test environments.

Applications protected

The services and databases included in each test environment.

Deployment runs

Safety validations attached to a pull request or release.

Environment execution

Minutes the twin is provisioned, exercised, and destroyed.

Data volume

Sanitized, referential state restored inside your boundary.

Peak workload

Traffic volume and concurrency during a test.

Governance and support

Policy scope, the regions environments may run in, and response level.

Questions

Pricing questions.

Is the MCP server free?
Yes. The MCP server is included in the MIT-licensed engine. Your coding agent starts it locally with af mcp; no Antifailure account or subscription is required.
Do I need an account to use Antifailure?
No. The quickstart goes from an empty machine to a running environment with no account and no sign-up. An account exists only for the hosted control plane, which coordinates environments across a team. Anybody can create one with a GitHub sign-in, and it needs no card and no invitation.
Is the engine really open source?
Yes, under the MIT license. Everything outside the ee directory is MIT, which is the engine, the command line interface, the masking, the egress gateway, the reports and the MCP server. The ee directory is public source under a separate enterprise license and running it needs a license key.
How many people can be in my organization?
5 on the free plan, 50 on Team, and 1,000 on Enterprise. The count is members plus invitations that have been sent and not yet accepted, because an invitation nobody has accepted is still holding the place. There is nothing to buy here and no per person price: the plan decides the number, so an organization is never charged per head for a limit it already has. Reaching it refuses the next invitation, names what you are holding, and removes nobody.
What happens when a free limit is reached?
You cannot create another environment until capacity is available or the limit is increased. Existing environments keep running.
Can I run the control plane myself?
Yes. The control plane is in the same repository and the self-hosting documentation covers it. The three numbers above are the defaults it ships with, so an installation you run yourself enforces the same free plan unless its operator moves an organization to another plan or edits the numbers.
What is an environment-hour?
One environment running for one hour. Two environments running for thirty minutes each also use one environment-hour.
Next

Bring your next pull request.

See how Antifailure would test your stack, what it would check, and the evidence your team would review before merging.

Request a demoConnect your agent