> Canonical: https://antifailure.dev/pricing > Community, team, and enterprise pricing for pre-production deployment safety. # Operational value, not AI personalities. Community is the local engine. It is free, it is MIT licensed, and it works today with no account. Team is a flat platform fee per organization plus run usage. Enterprise adds volume, policy, and governance. Those bands are illustrative, not a quote. Community needs nothing from us. The engine is MIT licensed, it installs with one command, and the quickstart runs on your own compute without an account. The hosted control plane is open: signing up is a GitHub exchange with no card and no invitation, and it lands you in your own organization on the free plan, whose limits are the ones below and are enforced from the first environment. Team and Enterprise are open for design partners, and those two buttons book a call or reach a person rather than take an address. - Community $0 local engine, forever The whole engine, on your machine and your cloud, with no account. 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 Illustrative $500 to $2,000 per month · one application Hosted control plane, included run credits, usage beyond the floor. Start a design partnership 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 - Customer-cloud execution for margin and data exposure - 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, residency, fleet 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 - Governance, evidence retention, and residency - Fleet management and premium connectors - Support and service-level commitments, sold when references exist ## Three numbers decide what free gives you. These are the ones a control plane enforces, not a summary of them. The engine itself has no quota. It is MIT licensed, it runs on your machine and in your own continuous integration, and nothing in it counts environments or hours. The three below are what a control plane enforces for an organization with no live subscription, and they apply the same way whether that control plane is the hosted one or one you run yourself. Reaching any of them refuses the next environment and says so, naming the number and what you are holding. Nothing that is already running is ever torn down. - 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. ## We meter what the twin actually does. Not how many agents you named. The systems the twin actually covers, not a count of personalities. Safety validations attached to a pull request or release. Minutes the twin is provisioned, exercised, and destroyed. Sanitized, referential state restored inside your boundary. Traffic shape and concurrency, not model fan-out. Policy scope, evidence retention, residency, and response level. ## What free covers, in the words people ask it in. Including the one about MCP. **Is the MCP server free?** Yes, and it needs no account. The MCP server is part of the engine, which is MIT licensed, and your client starts it on your own machine with one command. It serves the rehearsal tools to a coding agent over standard input and output, so there is no hosted component behind it, no key, and no plan attached to it. The enterprise directory carries no MCP code at all. **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?** The next environment is refused, with a message naming the limit, what the organization is currently holding, and who can change it. Nothing that already exists is torn down. Taking somebody's running environment away because a number moved is not a behaviour this product has. **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, held for one hour. It is the unit the control plane can actually measure: every environment holds a database branch, a network and a container per service for as long as it exists, so the cost is close to linear in it. A cap in dollars would need a price list per runtime, per region and per service size, none of which a control plane has. ## Know what happens before you deploy. Create a disposable production twin for every risky change. Catch migration failures before they reach customers.