Skip to content

docs: update Plane AI credits page to seat-based model and workspace overage #441

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
vihar merged 1 commit into from
Apr 27, 2026
Merged

docs: update Plane AI credits page to seat-based model and workspace overage #441

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
152 changes: 35 additions & 117 deletions docs/ai/plane-ai-credits.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,154 +1,72 @@
---
title: How AI credits work for team usage and billing
description: Learn how Plane AI's credit system works, why different tasks consume different amounts, and how workspace pooling helps teams manage AI usage efficiently.
title: How Plane AI credits work
description: Understand seat-based AI credits, what happens when included credits run out, and how workspace overage keeps your team moving.
---

# Plane AI credits
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot Apr 25, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Verify the H1 in docs/ai/plane-ai-credits.md and inspect sidebar labels in VitePress config.
set -euo pipefail

echo "== H1 in docs/ai/plane-ai-credits.md =="
sed -n '1,40p' docs/ai/plane-ai-credits.md | rg -n '^# '

echo
echo "== Potential sidebar references in docs/.vitepress/config.ts =="
rg -n -C2 'plane-ai-credits|Plane AI credits|How Plane AI credits work|/ai/' docs/.vitepress/config.ts

Repository: makeplane/docs

Length of output: 406

H1 heading "Plane AI credits" does not match the sidebar label "AI credits".

The page heading on line 6 must be updated to match the sidebar label defined in docs/.vitepress/config.ts (line 627). Either rename the H1 to "AI credits" or update the sidebar label to "Plane AI credits"—both must be consistent per coding guidelines.

🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@docs/ai/plane-ai-credits.md` at line 6, The H1 in the markdown currently
reads "Plane AI credits" but the VitePress sidebar label is "AI credits"; update
the H1 in the markdown file to exactly "AI credits" to match the sidebar label
(or alternatively update the sidebar label to "Plane AI credits"), ensuring the
top-level heading string and the VitePress sidebar label are identical; locate
the H1 "Plane AI credits" in the markdown and change it to "AI credits" (or make
the corresponding change to the sidebar label entry named "AI credits" in the
VitePress config) so they are consistent.


Plane AI uses credits as a universal measure of AI processing. This system ensures fair usage while giving teams predictable costs and transparent billing.
Plane AI credits measure AI usage in Plane Cloud.

::: warning IMPORTANT
AI credits apply only to Plane Cloud.

On self-hosted instances, you use your own AI provider [API key](https://developers.plane.so/self-hosting/govern/instance-admin#artificial-intelligence), and all AI usage and costs are managed directly through your provider. Plane does not track, pool, or enforce usage through credits.
On self-hosted instances, you use your own AI provider [API key](https://developers.plane.so/self-hosting/govern/instance-admin#artificial-intelligence), and all AI usage and costs are managed directly through your provider.
:::

## Why credits instead of limits?
## How credits are assigned

Traditional AI tools often impose hard limits, like "10 queries per day" or "50 messages per month." These limits create frustration because not all AI tasks are equal. A quick status check shouldn't cost the same as generating a full project plan.
Credits are included **per paid seat**.

Credits solve this by measuring actual computational work. Simple tasks consume fewer credits. Complex tasks consume more. This means you pay for what you use, not arbitrary quotas.
- Each active seat gets a monthly included credit amount based on your plan.
- Included credits are account-level entitlements tied to seats.
- This model is designed to be simple and predictable, similar to how modern AI products commonly package usage.

## What determines credit consumption?
For current included amounts by plan, check the latest pricing details on [Plane pricing](https://plane.so/pricing#ai-&-credits).

Three factors influence how many credits a task consumes:
## No default pooling

**Task complexity** measures the reasoning required. A straightforward question like "What's the status of work item SOFTW-124?" requires minimal processing. A request like "Analyze our project structure and suggest optimizations" requires multi-step reasoning, context synthesis, and detailed analysis.
Plane AI credits are **not pooled by default**.

**Response length** affects consumption because longer outputs require more generation. A brief answer might be 50 words. A detailed report with code examples might be 2,000 words. The AI needs to generate, validate, and format every word.
That means one member's unused included credits are not automatically shared across the rest of the workspace.

**Action scope** determines whether the AI is reading information or modifying your workspace. Querying existing data is lightweight. Creating 20 work items, each with descriptions, assignees, and metadata, requires multiple write operations and validations.
## What happens when included credits run out

## Credit consumption patterns
If a member (or your workspace's included capacity) runs out of available credits for the billing period, AI usage can stop unless overage is enabled.
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot Apr 25, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Clarify the scope of “runs out” to avoid mixed seat vs workspace semantics.

Line 34 currently blends per-member and workspace capacity language, which can read as contradictory with “no default pooling.” Consider using one explicit model statement here (seat-level only, plus overage behavior).

✏️ Proposed wording 
-If a member (or your workspace's included capacity) runs out of available credits for the billing period, AI usage can stop unless overage is enabled.
+If a seat exhausts its included credits for the billing period, AI usage for that seat can stop unless workspace overage is enabled.
🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@docs/ai/plane-ai-credits.md` at line 34, The sentence starting "If a member
(or your workspace's included capacity) runs out of available credits..." mixes
seat-level and workspace semantics; rewrite it to be explicit about the scope
(preferably seat-level only) and remove the workspace-capacity clause so it
aligns with "no default pooling" language, then add a short clause about overage
behavior (e.g., AI usage stops for that seat unless overage is enabled) and
ensure the updated phrasing replaces the current line.


Here's how these factors translate into typical usage:
Workspace admins can enable a workspace-level overage setting so teams can continue using AI after included credits are exhausted.

| Action type | Credit range | What this looks like |
| ---------------- | ------------ | ---------------------------------------------------------------------- |
| **Short query** | ~10 credits | Quick questions, status checks, brief clarifications |
| **Long query** | ~50 credits | Detailed explanations, code generation, analytical responses |
| **Action** | ~100 credits | Creating or editing multiple work items, generating project structures |
| **Heavy action** | ~250 credits | Bulk operations, file analysis, complex workflow automation |
## Workspace overage

To illustrate with a real workflow:
When workspace overage is enabled:

| Task | Why this credit amount |
| -------------------------------------------------------- | ------------------------------------------------------------ |
| Summarize yesterday's stand-up notes (10 credits) | Simple extraction and formatting of existing text |
| Generate detailed project timeline (50 credits) | Requires analysis, structure creation, and detailed output |
| Create 20 tasks from PRD (100 credits) | Multiple write operations with metadata for each work item |
| Analyze project structure for optimization (250 credits) | Deep analysis across multiple projects, with recommendations |
- AI usage continues after included credits are consumed.
- Additional usage is billed at the workspace level.
- Admins stay in control of whether overage is allowed.

With 10,000 credits, you could handle approximately:
If overage is disabled, new AI actions are paused after included credits are exhausted until credits reset or additional capacity is purchased/enabled.

- 1000 short queries, or
- 200 long queries, or
- 100 actions, or
- 40 heavy actions, or
- any mix that fits your workflow.
## Tracking and controls

## Plan comparison
Plane provides usage visibility so admins can manage cost and adoption:

| Plan | Monthly credits per user | Rollover period |
| -------------- | ------------------------ | --------------- |
| **Free** | 500 | No rollover |
| **Pro** | 1,000 | 1 month |
| **Business** | 2,000 | 3 months |
| **Enterprise** | Flexible allocation | Up to 12 months |

New workspaces receive 1,000 bonus credits upon signup. These onboarding credits expire after 30 days and help teams evaluate Plane AI before committing to a plan.

## How workspace pooling works

Credits are allocated at the workspace level, not per individual. This creates a shared pool that all members draw from.

This approach exists because teams don't use AI uniformly. Some members might use AI heavily during cycle planning, others during code reviews, others barely at all. A per-user allocation would mean unused credits in some accounts while others run dry.

Here's how it works in practice:

A team of 20 users on the Pro Plan receives 20 × 1,000 = 20,000 credits per month for their workspace. All 20 members use this shared pool. When someone creates 5 work items with AI (consuming ~50 credits), that deduction comes from the workspace balance, not an individual quota.

Admins can monitor usage patterns, set per-user limits if needed, and see which activities consume the most credits. This visibility helps teams optimize their AI usage over time.

## Credit lifecycle and rollover

Different plans handle credit expiration differently, reflecting how teams use AI over time:

**Free plan** credits don't roll over. The 500 monthly credits reset each month.

**Pro plan** credits roll over for 1 month. This accommodates the reality that usage fluctuates—one month might be heavy on planning, the next on execution. The rollover prevents "use it or lose it" pressure.

**Business plan** credits roll over for 3 months, recognizing that larger teams have more variable usage patterns. Seasonal projects, team changes, and workflow shifts mean monthly consumption varies significantly.

**Enterprise plan** credits can roll over up to 12 months, providing maximum flexibility for organizations with complex, long-term projects.

When you have credits from multiple sources (monthly allocation + rollover + top-ups), the system always uses the oldest credits first. This prevents newer credits from expiring while older ones sit unused.

## Top-up credits

Top-ups exist for months when your team's usage exceeds the plan allocation. These are one-time purchases that don't auto-renew.

| Pack size | Credits | Price (USD) | Best for |
| ------------- | ------- | ----------- | ----------------------------------------- |
| Standard pack | 1,000 | $2.00 | Light monthly overages |
| Growth pack | 2,000 | $4.00 | Small active teams |
| Scale pack | 5,000 | $9.00 | Moderate automation use |
| Bulk pack | 10,000 | $17.00 | Larger workspaces (best value per credit) |

Top-up credits are added instantly to your workspace's shared balance and expire 12 months after purchase. All workspace members can use them, and admins can track consumption in the usage dashboard.

## What doesn't consume credits

Viewing AI-generated results never costs credits. Once the AI creates something, you can revisit it unlimited times at no cost.

Managing your AI history, reviewing past conversations, editing saved prompts, organizing results is free. Storage doesn't consume credits.

Deleting AI-generated content doesn't recover credits. The computational work already happened, so removing the output doesn't reverse the consumption.

## Fair usage and transparency

Every action shows its estimated credit cost before execution. This preview lets you decide whether the task is worth the consumption.

If a task fails due to technical issues on Plane's side, those credits are refunded automatically. You only pay for successful AI operations.

The usage dashboard shows your remaining balance, consumption history, and per-action breakdowns in real time. Admins can download detailed reports for capacity planning and budget forecasting.

Alerts notify workspace admins when the balance reaches 20% and 5% of total capacity, providing time to top up or adjust usage patterns.
- Current credit balance and consumption trends
- Workspace-level usage monitoring
- Billing visibility for additional usage when overage is enabled

## FAQs

::: details Why this pricing model?
Credits provide granular control while remaining predictable. Unlike token-based pricing (which fluctuates based on AI model costs), credits give you stable rates. Unlike subscription tiers with arbitrary limits, credits scale naturally with your actual usage.
:::

::: details How long do credits last?
It depends on your plan and how you acquired them. Free plan credits reset monthly with no rollover. Pro plan credits roll over for 1 month, Business for 3 months, and Enterprise plans roll over for up to 12 months. Top-up credits purchased separately are valid for 12 months on all paid plans, regardless of your base plan's rollover period.
:::

::: details Do all workspace members share the same credit pool?
Yes. Credits are allocated at the workspace level, creating a shared balance that all members draw from. This prevents the problem of some team members having unused credits while others run out. Admins can set per-user limits if needed to prevent any single member from consuming the entire pool.
::: details Are credits shared automatically across all users in my workspace?
No. Plane does not use automatic credit pooling by default.
:::

::: details What happens when my workspace runs out of credits?
You'll receive alerts when your balance reaches 20% and 5% of total capacity, giving you time to respond. Once you hit zero, AI features become unavailable until you top up or your monthly allocation renews. Your existing data, past AI results, and all non-AI functionality remain fully accessible. You just can't request new AI operations.
::: details Do I get credits for each seat?
Yes. Included credits are assigned per paid seat based on your plan.
:::

::: details Can I switch between plans without losing credits?
Yes, you can change plans anytime. When you switch, your unused credits carry forward and adopt the new plan's rollover rules. If you upgrade mid-month, your increased allocation takes effect immediately. If you downgrade, the change happens at your next billing cycle to avoid losing paid credits.
::: details Can we keep using AI after included credits are used up?
Yes, if a workspace admin enables overage at the workspace level.
:::

::: details How can I monitor my workspace's credit usage?
The real-time dashboard shows your remaining balance, consumption history, and trends over time. Before executing any AI action, you'll see a credit cost preview.
::: details Where can I see the latest included credit amounts?
Visit [Plane pricing](https://plane.so/pricing#ai-&-credits) for the most up-to-date plan details.
:::

Ready to explore how Plane AI can help your team? [View our pricing options](https://plane.so/pricing#ai-&-credits) or start with 1,000 free credits.
Loading