Skip to main content
Plans bundle limits, support, and compliance features. Use this page to shortlist options before legal review—exact numbers change, but the pattern usually holds: pay for seats, automation volume, and the audit artifacts you need.

Highlights

  • Free — Core projects and limited automation runs. Best for evaluation and tiny teams with light automation.
  • Team — SSO options, higher limits, and priority email support. Common step after product-market fit when coordination overhead grows.
  • Enterprise — Regional options, advanced audit, and dedicated support channels. Typical when procurement, security questionnaires, or data residency enter the conversation.

Hidden costs

Count integrations, API volume, and retained history—not just seats. A team on paper may exceed automation quotas during a busy quarter.

How to choose

Start where your current limits hurt first—usually automation volume or member count—then add Enterprise when procurement or compliance requires it.

Proof points

Before upgrading, reproduce one painful workflow in a trial project and measure time saved. Finance teams respond to minutes per week reclaimed, not feature lists alone.

Pilot checklist

  • Confirm how many seats you truly need after removing inactive accounts.
  • List must-have integrations and confirm they are included or priced as add-ons.
  • Align legal and security on DPA, subprocessors, and data residency before you sign.

When to revisit

Re-evaluate plans at major milestones: funding rounds, geographic expansion, or a spike in automation usage after a new workflow goes live. Annual true-ups catch drift between contract and reality.