# Plans and availability

> Check personal and team plan access, included credits, seats and current offers, then diagnose the other requirements behind unavailable features.

Source: https://kaitoi.io/docs/reference/plans/
Section: Account and help / Plans and credits
Written for: Anyone choosing an account plan or diagnosing an unavailable feature.
Last reviewed: 2026-10-24

---

Your plan controls feature access. Some subscriptions also include credits;
**Add Funds** adds a separate pay-as-you-go balance. Buying credits does not
unlock a restricted feature, and feature access does not guarantee enough
credits, provider access or permission to edit a team's work.

## Check readiness in the selected workspace


Personal and Team contexts have separate subscriptions and funding. A team setup shell can exist before its active subscription and usable seats. First-party Code and Crew access belongs to the base capability set. For any action, check feature access, member authority, funds and required providers or services. Inspect the current offer in the selected workspace instead of assuming a personal purchase covers a team.

Personal and Team funding pools remain separate. Selecting an unresolved feature, authority, funds or dependency check highlights only that check; other gates do not turn into assumed successes.

*Figure: A capability, a role, available funds and dependencies are separate checks.*

## Check the right account and workspace

1. Open **Settings → Account → Profile** to confirm your identity and effective
   plan information.
2. Choose **Personal** or the intended team before inspecting **Plans** or
   **Billing**. A personal purchase does not subscribe or fund every team.
3. Open **Plans**, when offered, and inspect the current catalog, billing
   interval and subscription status.
4. Follow the action shown for that workspace. Existing subscriptions can offer
   **Manage Subscription** or **Manage in Portal**. An administrator-managed
   status can limit what you can change yourself.

Use [Pricing](https://kaitoi.io/pricing/) for the public catalog. Instance
settings and account-specific capability overrides can change what your
account is offered. Read the restriction beside the actual control before
deciding that an upgrade or more credits is the answer.

## Understand feature access

The source-defined tiers distinguish the following capabilities. The offer and
effective restrictions in your deployed account take precedence.

| Tier                 | Main distinction                                                                                                                                              |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Pay-as-you-go / base | Visual Studio workflows, Lab, raw-code viewing, supported connectors, Station publication, Kaitoi MCP server access, and first-party Kaitoi Code/Crew access. |
| Indie                | Adds personal provider keys and Variables, community/template publishing, outbound MCP client access, and public REST API capabilities.                       |
| Studio / Enterprise  | The full capability set, including raw-code editing, local integrations and template workflow API endpoints.                                                  |

First-party Code sign-in is separate from creating a developer REST key. General
REST access is also separate from template workflow endpoints: Indie does not
supply the latter capability. Applicable usage costs, provider requirements and
resource permissions still apply on every tier.

Connecting an external AI client to **Kaitoi's MCP server** is available on every
plan, including Pay-as-you-go. Having **Penny call another MCP server** is the
separate outbound client capability, available from Indie. An account-specific
restriction can still disable a capability; check the access message in Studio.

## Manage a team plan

You can create a team setup shell before buying its Studio subscription. Adding
new members requires **that team's** active Studio subscription and available
seats. A team role determines what each member can do with its resources.

Only the team owner manages its plan; other members can see **Owner Only**.
Choosing Studio from Personal can first offer **Select Team** or **Create Team
First**. Read the selected team and seat count before confirming a change.

Seat increases can apply immediately with proration; reductions apply next
billing period as shown in the offer. If cancellation is shown as scheduled,
check the displayed access-end date. Use the subscription portal's actual terms
for charges and cancellation rather than assuming a refund from a status label.

## Check the workflow's other requirements

Even with an eligible plan, a workflow may need:

- enough available credits or remaining team allowance;
- a supported managed provider or an eligible personal key;
- a team role that permits the operation;
- the correct connector account and service permissions;
- a running local service, model or installed recipe;
- compatible nodes and available input files.

For example, opening a Station does not grant its visitor the author's provider
accounts. Its execution uses the visitor's supported context and applicable
credits. See [Credits and costs](/docs/reference/credits/) to diagnose funding
separately from feature access.

## Hosted and self-hosted

Use the [Studio and Open Source comparison](/docs/concepts/studio-and-open-source/)
to understand the distributions. Follow installation and upgrade instructions
for an actually available package and its version. Hosted-only services,
account billing and managed capabilities should not be assumed to exist in a
local installation.

The CLI's local-service connection workflow connects your hardware to Studio.
It is a separate setup from running a self-hosted distribution.