01 / 03Pricing

Free until you outgrow it. Then $30 a month.

Install it and start working. No account. Past the free allowance, $30 a month lifts the ceiling to unlimited cards. The agent runs in whatever harness you already use, and the model bills its own tokens. Cards marks up neither.

FreeStart here

$0no account · no credit card

50 cards to start, then 5 a week (the bank caps at 50)

Install for Visual Studio Code Install for Cursor, Windsurf & more

ProUnlimited cards

$30/ month

Unlimited cards.

Upgrade to Pro inside the extension

Your cards live on your own disk. Each one is a git repo you own: cancel, uninstall, or walk away, and the work stays where it already is.

Students, OSS maintainers, and nonprofits can apply for a free Pro grant — start at /apply/grant or write to support@cards.management.

02 / 03Where the line is

What runs free. What Pro adds.

What runs on the free tier

An extension for building with coding agents from plan to commit, in Visual Studio Code and compatible forks — with no account. Each coding-agent job becomes a card: description, plan, comments, attachments, sessions, streams, commits, and attribution — kept together on one work object that survives the session, the agent, and the harness.

Each card is its own git repository on disk. The session ends; the card stays. You start with fifty cards and earn five more a week — and reading, editing, and re-running the cards you already have is never metered.

The configured agent launches from card context — the card id, the workspace path, and the card-repo path passed through to whatever harness you already run. Cards is the context layer between the prompt and the harness; it does not execute the agent.

What Pro adds

Unlimited card creation. When you are creating cards faster than the free allowance refills — daily, heavy, production work — $30 a month removes the ceiling and the weekly count stops mattering.

Pro is a flat monthly price, not a meter. It does not count your cards, your tokens, or your runs. Students, OSS maintainers, and nonprofits can hold the same Pro access for free, by grant.

What neither tier includes

The harness

Claude Code and Codex CLI — separate products on separate billing. Cards launches them; it does not run them.

The model

The agent reaches the model provider directly; the provider bills for tokens in its own console. Cards does not see that traffic and does not mark it up.

A compliance surface

Cards' gates are advisory; its attribution is per contributor class (user, agent, system) and lives in git, not in an audit log.

03 / 03Questions, answered plainly

Is Cards really free without an account?: Yes. Install the extension and you get 50 cards to start and five a week after — no sign-up, no credit card. The whole work surface is there; the only limit on the free tier is how many new cards you create before you register.
What happens when the free allowance runs out?: After the bank of cards empties, creating a new card asks you to register. Nothing you have already made is touched; the cards you already have keep working, and each one stays a git repository on your disk. The count is tracked locally on your machine, not on a server.
What does the $30 Pro plan add?: It removes the weekly ceiling on new card creation, giving you unlimited card creation. It does not add the harness, the agent, or the model provider's tokens; those are billed directly, in your own console, and Cards does not mark them up.
Why no usage-based pricing?: Usage-based pricing on a work surface punishes the developer for using the product. Pro is a flat monthly price with unlimited cards: the developer who opens a card every morning pays the same as the one who opens one a week. Token costs from the underlying model are billed by the model provider, separately, in your own console; Cards does not mark them up.
Can students, OSS maintainers, and nonprofits use Pro for free?: Yes, by grant. A grant confers full Pro access regardless of subscription, reviewed per identity — write to support@cards.management. It is a human review, not a self-serve flow.
What happens if I cancel?: The cards stay on your disk. Each one is a git repository there, and the extension keeps reading them. The hosted service stops signing fresh entitlement tokens for your account, so new-card creation returns to the free allowance. Resubscribe and unlimited creation comes back against the same on-disk cards.
What does Cards not catch?: Cards is a work surface, not a verification system. Its gates are advisory; its attribution is per contributor class, not an audit trail. Read /docs/boundaries before relying on Cards as the only check between the agent and the merge.