Credits and Plans
What the plans include, what consumes credits and what does not, rough costs per action, what happens at zero, and how to keep a Cloud workspace inside its monthly allowance.
Cogny charges for what it pays a model or data provider for, at a small margin, in credits. One credit is roughly one Swedish krona, about ten US cents. Plans differ in the monthly allowance and in which actions are metered.
The plans
| Plan | Price | Monthly credits | Integration calls | In-app chat and reports |
|---|---|---|---|---|
| Free | 0 | 15 | Metered from the 15 | One-time 50-credit signup gift for chat |
| Solo | $9 | none | Unmetered under fair use | Top-up credits only |
| Cogny AI | $18 | 150 | Unmetered | From allowance, then top-ups |
| Cogny Pro | $90 | 1,500 | Unmetered | From allowance, then top-ups |
| Cloud | $499 | 5,000 | Metered | From allowance, then top-ups |
Cloud is the full product: the warehouse, context tree, reports, ticket board, coding agent, automations and the analysis loop, with Cogny paying for inference. Solo is bring-your-own-agent: Cogny's integrations behind one MCP connection, your own Claude or ChatGPT subscription doing the thinking. Cogny AI and Pro sit between: an allowance for chat and loops, without the Cloud warehouse and provisioning.
Plans are month to month with no lock-in. There is no free trial of Cloud because Cogny pays for the inference; you can sign up, use it for a month, and cancel. Upgrading from Solo to Cloud keeps the workspace.
Credits, allowance and top-ups
Every workspace has two buckets. The monthly allowance refills on the billing date and does not roll over. Top-up credits ($20, $50, $100 or $200, one-time) roll over forever. Cogny drains the allowance first, then top-ups.
What costs credits
| Action | Metered on Cloud | Rough cost |
|---|---|---|
| A report run | Yes | Tens of credits, more for wide cross-channel audits |
| Ticket generation and approval scoring | Yes | A few credits per batch |
| A campaign ticket (build a campaign with keywords and ads) | Yes | 30 to 40 |
| A content piece | Yes | A few to tens, depending on length and research |
| A fully coded page via the coding agent | Yes | A couple of hundred |
| A meta title rewrite | Yes | A few |
| Chat message | Yes | Token-based; a data question is cheap, a long analysis is not |
| Integration call | Yes | One credit minimum per call |
| Image generation, media analysis, web search | Yes, on every plan | Per call |
| Cogny Shield masking and injection scan | Yes | Small, per pass |
| Scripts | No | Free |
| Impact analysis of completed tasks | No | Free |
| Researching an MCP wish | No | Free |
Coding burns the most, then content, then reports, then campaign changes. A mixed setup of three or four weekly reports plus ten content pieces a month fits inside the Cloud allowance with room to spare; content-only usage gets you roughly twenty articles or product pages a month. A reference Cloud workspace with six weekly reports and regular tickets has averaged between 400 and 2,000 credits a month over the last six months, with the high months being the ones with large content and coding pushes.
Where to see it
Settings → Account → Billing shows the plan, the current balance in both buckets, the refill date, and the top-up button. A credit chip on the plan card shows the balance everywhere.
What happens at zero
When both buckets are empty, chat, scheduled reports and ticket automation pause. A banner on Home, Reports, Tickets and Tasks says so and offers a top-up; the plan refills on the next billing date. Nothing is lost: scheduled reports resume on their next run, and tickets stay where they were. Connected integrations and data collection keep running.
Keeping consumption sensible
- Run the reports you read. Disable the rest. This is the single largest lever.
- Prefer content and campaign tickets over coding tickets where a CMS can do the job.
- Run large coding tickets on your own agent if you have a Claude or ChatGPT subscription with headroom: the ticket stays tracked in Cogny while the inference is billed to your subscription.
- Watch the first month. Onboarding, backfills and the first big content push spend more than a steady month. The reference workspace above used roughly 7,000 credits in its first full month and settled to under 1,500 afterwards.
- Pause reports during a site migration. They spend credits analysing a moving target.
Agencies and multiple sites
One workspace per client. Credits are per workspace. For portfolios of low-activity sites, the Cogny team can price a bundled arrangement after observing real consumption; ask during onboarding rather than provisioning a full Cloud plan per satellite site.
Ad budget
Media spend is separate from the subscription and paid to the platforms directly. Cogny changes budgets only through approved tickets or explicitly granted tools. The exception is geo-targeted TV campaigns booked from the Campaigns page, which are prepaid to Cogny per campaign.
Reading this with an AI agent? Fetch the raw markdown at /docs/credits-and-plans/index.md or see llms.txt.