Browse documentation pages

Cumulus Ecosystem Documentation

Blocks Plans and Limits

Active

Understand plan tiers and practical usage limits before scaling.

On this page

What this is

This page helps admins understand plan boundaries to avoid blocked actions during growth.

Why I built this

I built Blocks to help teams manage projects, workers, and assets in one operational system instead of fragmented tools. When project assignment and worker access are disconnected, teams lose time and quality drops fast. Blocks connects admin planning with worker execution so work can be assigned, tracked, and completed in a consistent way.

Who should use this

  • Admins who assign projects and monitor worker activity.
  • Workers who need secure access to assigned project resources.
  • Teams that need a controlled workflow from assignment to completion.

What you can do today

  • Compare available plan levels for your operation size.
  • Predict when usage upgrades are required.
  • Avoid interruptions by planning limits ahead of demand.

Quick start

By the end of this page, you will have a clear and repeatable first outcome in Blocks Plans and Limits.

  1. Review current usage and active projects.
  2. Compare your needs against available plan limits.
  3. Upgrade before reaching hard operational constraints.

Known limits and maturity

  • Plan limits are enforced to keep system reliability stable.
  • Late upgrades can delay assignment operations.
  • Review plan fit monthly if your team is growing quickly.
  • Current maturity: active.