Compare plans
Every limit and feature on Free, Team, Business and Enterprise, and what happens to each when a workspace moves down a plan.
A workspace is on one plan: Free, Team, Business or Enterprise. This page lists what each plan allows. For prices, the trial, and how to choose or change a plan, see Plans and billing.
A new workspace’s 30-day trial runs on Business, so during the trial the Business column applies.
Limits#
| Limit | Free | Team | Business | Enterprise |
|---|---|---|---|---|
| People | 5 | No limit | No limit | No limit |
| AI workers | None | No limit | No limit | No limit |
| Live projects | 3 | No limit | No limit | No limit |
| Support portals | None | 1 | No limit | No limit |
| AI tokens a month | 250,000 | 2 million | 10 million | 10 million, or as agreed |
| File storage | 1 GB | 50 GB | 250 GB | As agreed |
How each one is counted:
- People are the active owners, admins and members. AI workers and support customers aren’t counted. When you send an invitation, invitations still waiting to be accepted count as well, so you can’t invite more people than the plan has room for.
- AI workers are the active AI workers in the workspace, however they run.
- Live projects are projects that aren’t archived. Archiving a project frees a place.
- Support portals are projects whose portal is on, whether it’s Invite only or Open.
- File storage is the size of every attachment on tasks and tickets and every version of every project document, including documents in the Trash.
- AI tokens are what the workspace uses on Projik’s own AI each month: AI workers that Projik runs on the built-in model, the knowledge base, and “Help me draft this”. An AI worker running on your own model key is billed by your provider and doesn’t use them. Token packs add to the monthly amount. See AI allowance.
On Team and Business you pay per person, so there’s no limit on people: the number you’re billed for follows the number you have. On Enterprise the limits and the AI allowance are set for your workspace.
Features#
| Feature | Free | Team | Business | Enterprise |
|---|---|---|---|---|
| Integrations (GitHub and calendars) | – | Yes | Yes | Yes |
| Limiting people to selected projects | – | Yes | Yes | Yes |
| Repeating tasks | – | Yes | Yes | Yes |
| The knowledge base | – | Yes | Yes | Yes |
| AI workers on your own model key | – | Yes | Yes | Yes |
| A support portal on your own domain | – | Yes | Yes | Yes |
| Support SLAs | – | – | Yes | Yes |
| Published help articles | – | – | Yes | Yes |
| A shared support address | – | – | Yes | Yes |
| AI workers that work on GitHub | – | – | Yes | Yes |
| Data sources | – | – | Yes | Yes |
Where each one is explained:
- Google Calendar and Outlook and GitHub
- Project access
- Repeating tasks
- Knowledge base sources and Ask
- Models and keys
- SLAs
- Help articles
- Portal setup, for the shared support address and your own domain
- GitHub workers
- Data sources
In every plan#
These aren’t limited by plan:
- invitations, booking and the cascade preview
- the list, board, Gantt, calendar and roadmap
- project documents, within the plan’s file storage
- “Help me draft this” for new tasks, within the plan’s AI tokens
- notifications: the bell, email and browser notifications
- passkeys and recovery codes
- connecting Claude to Projik
With no AI workers and no knowledge base, Free’s AI tokens are only used by “Help me draft this”.
Moving down a plan#
A workspace moves down when its trial ends without a plan being chosen, when a paid plan is cancelled or changed to a smaller one, or when payments keep failing.
A limit stops you adding. It never takes anything away. Nothing is deleted, hidden or locked, and people outside your workspace never see a plan message: a support portal that’s on stays on, and published help articles stay readable.
The one exception is spending: AI workers stop as soon as the plan no longer covers them.
What happens to each limit#
| Over the limit for | What happens |
|---|---|
| People | Everyone keeps their access and everything keeps working. Invitations, and reactivating someone who was suspended, are refused until the workspace is back under the limit. |
| Live projects | Every project keeps working. Creating a project, unarchiving one or restoring a deleted one is refused until the workspace is back under the limit. |
| AI workers | Free has no AI workers, so on Free every AI worker stops taking work. It no longer accepts invitations by itself, and a run that was waiting is skipped. Its invitations stay open for a person to pick up. Workers aren’t deleted and keep their settings, so upgrading turns them back on. |
| Support portals | Every portal that’s on stays on. Turning on another is refused. |
| File storage | Every file stays, and can be opened and deleted. Uploading attachments, documents and new versions is refused until there’s room. |
| AI tokens | Nothing changes part-way through a month except the amount. Once the month’s tokens and any token packs are used, AI workers’ runs, knowledge base questions and task drafts are refused until the next month. Token packs you bought stay yours on any plan. |
What happens to each feature#
| Feature lost | What happens |
|---|---|
| Integrations | Calendars and GitHub that are already connected keep syncing. Nothing new can be connected. Disconnecting always works. |
| Limiting people to selected projects | People who are already limited stay limited. Nobody else can be limited. Giving someone all projects again always works. |
| Repeating tasks | Repeats that are already running keep making copies. No new ones can be set up. |
| The knowledge base | Sources are kept, and customers can still read help articles in the portal. Asking a question, adding a source and refreshing one are refused. |
| AI workers on your own model key | Only Free lacks this, and on Free every AI worker is already off. Your keys are kept for when you upgrade. A worker set to your own key is never moved onto Projik’s AI. |
| Support SLAs | Your policies are kept. The resolution clock on open tickets is frozen at the moment SLAs go, and SLA warnings stop. Upgrading again starts each frozen clock from then, so the time without SLAs isn’t counted. Policies can’t be changed in the meantime, but one can be removed. |
| Published help articles | Published articles stay up as they are. Nothing new can be published, and a published article can’t be edited, because an edit goes live as it saves. It can still be archived. Drafts can still be written and edited. |
| A shared support address | An address that’s already set is kept. A new one can’t be set. |
| A support portal on your own domain | A domain that’s live stays live. A new one can’t be connected. |
| AI workers that work on GitHub | The workers stay, but their waiting runs are skipped. A task that was already handed to the coding agent is still followed until it settles. |
| Data sources | Connections are kept. AI workers aren’t offered their tools. |
Owners and admins see a banner for each limit the workspace is over, with the quickest way back under it. See Plans and billing.