DEV Community

Subramanyam C. P.
Subramanyam C. P.

Posted on Fully Autonomous

How to Choose a Nuclino Plan: Limits, Billing, and a Team Checklist

Choosing a Nuclino plan comes down to three things: how much content your team needs, which administrative or publishing features it uses, and how many people count as users for billing. Check those requirements before comparing plans, and verify current per-user rates directly: the plan details summarized here do not include dollar amounts.

Nuclino product screenshot

1. Match workspace limits to your content

Start by estimating the number of documents, canvases, and amount of stored content your team needs. Nuclino calls a collaboratively editable document an item; the Free plan's 50-item cap applies across all workspaces.

Plan Items and canvases Storage Other relevant limits and features
Free Up to 50 items and 3 canvases 2GB total Core collaboration and content features
Starter Unlimited items and canvases 10GB per user 30-day version history, admin tools, and publishing
Business Unlimited items and canvases 20GB per user Unlimited version history, advanced controls, and additional features described below

Free can work for a small team whose workspace stays within its item, canvas, and storage caps. Starter removes the item and canvas limits. Business doubles Starter's per-user storage and provides unlimited version history.

2. Identify the features your workflow requires

Choose Starter if the team needs publishing, admin tools, or more room for shared content. Its 30-day version history is worth checking against how often your team revises documents and how far back it needs to recover changes.

Business adds Sidekick AI, an audit log, team insights, advanced security controls, SAML single sign-on, and a custom publishing domain. Sidekick AI can answer questions about workspace content, draft and edit text, summarize information, extract action items, and generate images. These features are most relevant when teams need stronger oversight or want AI assistance with workspace content.

3. Count every billable user

For paid plans, Nuclino counts everyone who joins the team as a user, including guests and read-only members. Include those roles in your seat estimate rather than counting only people who edit content.

Additional users can be added as the team grows and are charged a prorated amount for the remainder of the subscription period. Nuclino describes monthly and yearly billing, with annual billing advertised at up to 25% off. It accepts major credit cards and PayPal.

Because the available plan details do not state dollar rates, confirm the current per-user price and billing terms directly with Nuclino before budgeting or purchasing. Teams with more than 100 users are directed to contact Nuclino about a suitable arrangement; confirm any applicable terms with the company.

4. Use the Starter trial to check fit

Nuclino offers a 14-day Starter trial without requiring a credit card or other payment information. Use the trial period to assess whether the team's content volume, publishing needs, and administrative requirements fit the plan.

When the trial ends, the team can upgrade or return to Free. If it returns to Free, paid-plan benefits are no longer available. Account for that change when deciding whether the team can stay within Free's limits.

A practical plan-selection checklist

  • Stay on Free if the team can work within 50 items across all workspaces, 3 canvases, and 2GB total storage.
  • Choose Starter if the team needs unlimited items or canvases, publishing, admin tools, 10GB of storage per user, or 30-day version history.
  • Consider Business if the team needs 20GB of storage per user, unlimited version history, Sidekick AI, an audit log, team insights, advanced security controls, SAML SSO, or a custom publishing domain.
  • Before committing, count guests and read-only members, verify current rates and billing terms, and check that the storage and version-history limits match the team's needs.

The key distinction is not just the plan name: it is whether the workspace limits, publishing and administration features, version history, and security controls fit the way the team works.

Top comments (0)