Krafa
Dashboard
Dashboard
Getting Started
QuickstartHow it works
The Canvas
Canvas overviewPasting and node typesOrganizing a boardCommand menuKeyboard shortcuts
Design Taste
Taste memoriesExtractionConflictsCurating your profile
Using with Agents
Connecting an agentMCP server referenceClaude CodeCursorCodexKiroAntigravity
Imports
Imports overviewXPinterestDribbble
Reference
Plans and billingHTTP APISelf-hostingFAQ
KrafaAll systems operational
Reference

Plans and billing

What Krafa costs, what a generation is, and what happens when your agent runs past the included allowance.

Krafa is a paid product with a 14-day free trial and no free tier. A subscription covers the app and a monthly allowance of generations, which is the unit your agent spends every time it reads your taste over MCP.

Plans

Pro is a workspace of one. Teams adds people, extra workspaces, and a pooled allowance everyone draws from.

Krafa ProKrafa Teams
Monthly$25 / month$30 per seat / month
Annual$20 / month$25 per seat / month
People1One per seat, up to 99
Workspaces1Unlimited
Included generations2,000 per period3,000 per seat per period, pooled

Annual is billed as a single invoice: $240 a year on Pro, $300 per seat on Teams. Both plans start with a 14-day free trial, offered on your first subscription only. Upgrading later doesn't restart it.

Teams pools its allowance across the workspace, so five seats share 15,000 generations rather than getting 3,000 each. One heavy user and four light ones is exactly the case pooling is meant to absorb.

Note

Pro is deliberately a party of one: a single workspace holding a single person. Adding a second workspace, or inviting anyone at all, is what moves you to Teams.

What counts as a generation

One MCP tool call is one generation, whichever tool it is. Asking for the profile, listing memories, and pulling exemplars each cost the same one.

Connecting doesn't cost anything, and neither does listing the available tools, so an editor sitting idle with Krafa configured never spends. Only a real tool call is billed.

Nothing else in Krafa is metered. Pasting references, running extraction, resolving conflicts, and editing memories are all part of the subscription, however much of it you do. There's no quota on how many boards, nodes, or memories you accumulate, or on how much you upload. The one upload limit is a 50 MB ceiling on any single file, which is practical rather than commercial.

The allowance resets at the start of each billing period, which follows your subscription date rather than the calendar month.

When the allowance runs out

Krafa works down a fixed order and only stops at the last step.

OrderSourceWhat it costs
1Included allowanceNothing, it's in the plan
2Prepaid creditsBought up front, never expire
3Overage$0.02 per generation, added to your next invoice
4RefusedNothing, because nothing is served

Running past the included allowance doesn't interrupt your agent. It moves to prepaid credits if you have any, and to overage if you don't. The only hard stop is the spend cap.

Credits

Credits are prepaid generations at the same $0.02 each. They never expire and they're spent before overage, so buying them is how you keep a heavy month off the invoice.

PackGenerations
$5250
$10500
$251,250
$502,500
$1005,000

$5 is the smallest top-up. Buy them under Settings → Credits.

Auto-recharge

Off by default. Turned on, it buys another pack whenever your credit balance falls to the threshold, which defaults to a $25 pack at 100 credits remaining.

It tops up at the threshold rather than at zero on purpose: a long agent run would otherwise stall mid-task waiting on a card round-trip.

Spend cap

The cap is the most Krafa will charge beyond your subscription in one billing period, and it defaults to $100. It counts credit purchases made this period plus overage accrued. Past it, generations stop rather than cost more.

This is the one limit that refuses work outright, so it's the one worth setting deliberately. Raise it, lower it, or remove it entirely under Settings → Credits.

Warning

The cap is what stands between a misconfigured agent loop and a surprise invoice. Removing it removes that.

What your agent sees

Refusals come back as ordinary MCP tool errors rather than HTTP failures, written as a plain sentence because the agent reading it is what tells you what happened.

At the spend cap:

This workspace has reached its monthly spend cap, so no more generations can be billed. Raise or remove the cap at app.krafa.ai/settings/credits.

Without an active subscription, the error says the board has none and points at the page to start one. A token that's missing or wrong is a different failure and returns 401 before any of this is reached; see the MCP reference.

Who pays on Teams

A token belongs to a board, and a board belongs to a person, but the person spending isn't always the person paying.

Krafa bills the board owner's own subscription when they have one. Otherwise it looks at the workspaces they belong to and draws from the first one running on Teams. Pro never lends its allowance out.

Members drawing on someone else's pool see the workspace's usage but can't change its credit settings. The owner holds the card, the cap, and the auto-recharge switch.

Tracking usage

Settings → Usage shows every tool call your agents made over the last 7, 30, or 90 days, broken down by day and by tool, counted in UTC.

It's a rolling window rather than a billing period, so it answers "what have we been doing lately" rather than "what do we owe". The remaining allowance, credit balance, and any overage sit under Settings → Credits.

Changing or cancelling

Plan changes, payment methods, and invoices all go through the Stripe billing portal, reachable from Settings → Billing.

  • Upgrades and added seats take effect immediately and are invoiced with proration.
  • Seat reductions can't drop below the seats you're using. Remove people first, then reduce.
  • Cancellation takes effect at the end of the current period, so you keep what you've paid for.

Accounts that aren't metered

Some accounts show "This account isn't metered" and spend nothing:

  • Accounts that predate the paywall, which were grandfathered in.
  • Self-hosted instances running without Stripe credentials, since locking users out of a feature nobody can pay for would be the wrong default.

Their calls are still recorded, so the usage panel works normally. They're just never charged.

On this page

PlansWhat counts as a generationWhen the allowance runs outCreditsAuto-rechargeSpend capWhat your agent seesWho pays on TeamsTracking usageChanging or cancellingAccounts that aren't metered