Plans and usage
A workspace is on a plan, which says how much of everything it may use. Plan and usage in the sidebar shows the plan, what the workspace uses against it, and the plans side by side.
Nothing is charged yet
There is no payment in CodeKasten yet. The prices say what a plan will cost; an administrator of the platform puts a workspace on a plan. A new workspace starts on Free.
The plans
Prices are per editor a month.
| Free | Team | Business | Enterprise | |
|---|---|---|---|---|
| Price, billed yearly (monthly) | $0 | $12 ($15) | $29 ($35) | on request |
| People | ||||
| People who can edit | 5 | unlimited | unlimited | unlimited |
| Viewers | 50 | unlimited | unlimited | unlimited |
| Guests | – | 5 | 25 | unlimited |
| Workspaces on this plan per person | 1 | – | – | – |
| Data | ||||
| Records per branch | 1,000 | 50,000 | 125,000 | 500,000 |
| File storage | 1 GB | 20 GB | 100 GB | 1,000 GB |
Branches besides main | 2 | unlimited | unlimited | unlimited |
| History you can open | 14 days | 1 year | 2 years | all |
| Installed apps | 3 | unlimited | unlimited | unlimited |
| Automation | ||||
| Enabled automations | 5 | 50 | 150 | 500 |
| Workflow runs a month | 100 | 25,000 | 100,000 | 500,000 |
| Connected accounts | 1 | 10 | unlimited | unlimited |
| Developers and agents | ||||
| API and agent calls a month | 1,000 | 100,000 | unlimited | unlimited |
| API keys | 2 | 20 | unlimited | unlimited |
| Coding sessions kept | 10 | unlimited | unlimited | unlimited |
| Workspace keys | – | ✓ | ✓ | ✓ |
| Publishing releases | – | ✓ | ✓ | ✓ |
| Access control | ||||
Roles, a protected main, sharing a branch with a person | ✓ | ✓ | ✓ | ✓ |
| Protect other branches, keep merges to a branch's admins | – | ✓ | ✓ | ✓ |
| Groups | – | 3 | unlimited | unlimited |
| Set what viewers and members get on a branch | – | – | ✓ | ✓ |
| Groups that carry a role | – | – | ✓ | ✓ |
On every plan, without a limit: chat, the Inbox, boards and drawings (with the Design app), saved views, translations, the assistant and the builders.
Who is an editor
An editor is anybody who can change something in the workspace: its members, admins and owners, and any guest or viewer whom a branch makes an editor - by name, as the one who made it, or through a group. Viewers and guests who only read are not editors.
What is counted
- Records are what people keep: projects, tickets, documents, tags. Relations between records, the blocks of a text and what workflows write for themselves are not counted. They are counted per branch, like installed apps and enabled automations: the page shows the branch you are on. The apps that come with the platform (CodeKasten, Design) are not counted as installed apps.
- Files are counted once, however many branches they are on.
- Workflow runs and API and agent calls are counted per calendar month. A call is one request to the GraphQL endpoint or the MCP server.
- Workspaces per person applies to Free only: you can own one workspace on it. Your own workspace and the ones apps and workflows are built in are not counted.
At a limit
Nothing that exists stops working, and nothing is deleted. Reading is never refused. Only the next new thing is, with a message that names the limit and the plan that has room:
The Free plan allows 2 branches besides main, and this workspace has reached that. The Team plan allows more.
An agent gets the same words as the result of its tool. History older than the plan allows is kept and not listed; it is there again on a higher plan.
A workspace that moves to a lower plan keeps what it made: four groups stay four groups on Free, and only a fifth is refused.
Changing the plans
The plans are records in the System workspace, so only an administrator of the platform (a superuser) changes them. On this page they get two more things:
- Put it on, to move the workspace to another plan;
- Edit plans, which turns the table into inputs: a limit left empty is unlimited, 0 is none. Each plan is saved by itself.
A change applies at once, to every workspace on that plan.