Hexabot Plans: How to Choose Between Starter, Pro, and Unlimited

Updated

Hexabot offers three paid plans — Starter, Pro, and Unlimited — and you can start free before upgrading. The right tier depends on your operational usage: how many users you bring on, how many workflows you run, and how many license activations you need in production. Hexabot's own pricing page frames the decision this way rather than around fixed feature lists, so the practical approach is to begin on the free tier, watch those three signals grow, and upgrade when one of them becomes a constraint.

The Plans at a Glance

Plan Best suited for What drives the upgrade
Free (start here) Evaluating the platform, building and testing workflows locally Hitting limits on users, workflows, or activations
Starter Early production use with a small team First real users and live workflows
Pro Growing operations with more workflows and team members More users, more workflows, more activations
Unlimited Full-scale deployment without plan ceilings Usage that would otherwise keep pushing you up tiers

The site lists Starter, Pro, and Unlimited as the paid tiers and provides a "Buy" checkout link for each. It does not publish per-plan prices, user caps, or workflow limits in the page content available, so confirm exact numbers on the pricing page before committing.

How to Decide

1. Start free and measure real usage

Hexabot's guidance is explicit: start free, then upgrade as users, workflows, and license activations become production signals. Don't guess your tier from a feature checklist — build your first workflow, connect a channel, and see what your actual footprint looks like.

2. Identify your binding constraint

Ask which of the three signals will hit a limit first:

  • Users — if your team or client base is growing, you'll likely move up on seats.
  • Workflows — if you're automating many separate processes (support triage, lead routing, internal ops), workflow count becomes the driver.
  • License activations — if you're deploying across multiple environments or instances, activations matter most.

Whichever runs out first tells you which tier to buy.

3. Match the tier to the stage, not the feature list

  • Starter fits a first production deployment: a small set of workflows serving real users.
  • Pro fits an expanding operation where both workflow count and team size are climbing.
  • Unlimited fits deployments where you'd otherwise keep bumping ceilings — multi-channel, multi-team, or multi-instance setups.

Where to View Pricing and Buy

  • Pricing overview: https://hexabot.ai/pricing
  • Purchase links are provided per tier on the site: "Buy Starter," "Buy Pro," and "Buy Unlimited," each leading to a license checkout.

Because Hexabot is self-hostable, your plan governs licensing and usage rather than hosting — you run the runtime yourself, which is why activations are a meaningful signal.

A Practical Path

  1. Install the CLI and scaffold a project: npm install -g @hexabot-ai/cli, then hexabot create my-project, cd my-project, hexabot dev.
  2. Build one customer-facing workflow and connect a channel.
  3. Track users, workflows, and activations as you add real traffic.
  4. When one signal nears its limit, check the pricing page and buy the next tier up.

This keeps you on the cheapest plan that actually fits, and avoids paying for capacity you haven't reached yet.

Common Pitfalls

  • Buying before measuring. The free start exists precisely so you can size your usage first.
  • Assuming features differ by tier. The site steers plan choice by operational usage, not feature gating — verify any specific capability you depend on before upgrading.
  • Ignoring activations. For self-hosted deployments across environments, activation count can be the real ceiling, not users or workflows.

For the underlying platform capabilities — graph/YAML workflows, memory and RAG, MCP tools, human handoff, and multichannel delivery — see the features page; those apply across the runtime regardless of which plan you land on.