Account and billing

Plans

The four plans, what each one includes, and how plan credit differs from usage credits.

There are four plans, and they differ in one thing: how much work you can do in a month. Every capability is on every plan; nothing is locked behind a tier. Free is a real plan rather than a trial, and you can stay on it as long as it covers what you do.

The four plans

PlanWho it is for
FreeTrying things out and occasional work. A one-time credit grant, no card, and no expiry on what you were given.
ProOne engineer working on RTL most days. Monthly credit, a better usage rate than topping up, and priority support.
MaxHeavy, sustained use; over five times the monthly volume of Pro. The right plan once you are running several jobs a day.
TeamA hardware team sharing one workflow, with the largest monthly credit in the catalog.

Prices are quoted in US dollars on both of our sites, because credit is measured in dollars and quoting the same unit twice keeps the price and the balance beside it comparable.

Each plan card also says roughly how many typical runs its monthly credit covers. That is usually the more useful number, because it already accounts for the fact that a larger plan is metered at a better rate as well as funded more generously.

Note

Plans are subscriptions, not run bundles. What a plan gives you is a monthly credit balance at a better rate; it does not hand you a fixed number of tickets that expire unused if you have a quiet week.

Every plan has every feature

This is worth saying plainly, because it is unusual. Upgrading does not unlock a mode, a language or a target device. It buys you more room to work.

  • Agent mode and Plan mode, on every plan.
  • Project mode on an uploaded repository, Debug mode and Optimize mode, on every plan.
  • Verilog, SystemVerilog and VHDL, on every plan.
  • Every FPGA target family and the generic target, on every plan.
  • Sharing, history, support tickets and referrals, on every plan.

The comparison table on the pricing page says the same thing row by row. What changes as you move up is the monthly credit, the rate it is metered at, and the level of support.

Plan credit and usage credits

Your account has two balances, and knowing which one is paying explains almost every question people have about billing.

BalanceWhat it is
Plan creditComes with a plan. It is worth the plan's price, it refills every month, it is spent first, and whatever is left at the end of the cycle does not roll over.
Usage creditsBought separately as a top-up, or granted by support. They never expire and they take over once plan credit is gone.

Plan credit goes further than the same amount of usage credits, and it goes further still on the larger plans. That is what a subscription buys you beyond the balance itself: a better rate on every run it pays for. The composer tells you when a run has moved from plan credit to usage credits, so the change never happens silently.

The full mechanics are in Credit and top-ups.

What uses credit

Anything that asks a model to do something. That includes questions:

ActionUses credit?
Writing a module from scratchYes
Editing an uploaded projectYes
A Debug or an Optimize runYes
Asking a question about a module or a projectYes, and usually much less
Clarifying questions before a Plan-mode runYes, and usually much less
Applying or rejecting a proposed fix or rewriteNo; applying is free
Downloading files, sharing a chat, reading historyNo

Note

Tools do not add runs. A generation with Web Search, Knowledge Base, Auto-Verify and Reflection all switched on is still one turn; it does more work, so it may use more credit.

Monthly or yearly

Paid plans can be bought a month at a time or twelve months at once. Yearly is cheaper per month; the credit still arrives one month at a time, so a yearly plan is a discount on the price rather than a large balance handed over on day one.

Both terms are shown on the pricing page behind the same toggle. See Buying and managing a plan.

Where to go next