Subscriptions and Pricing

Braidrun offers four plans: Free / Pro / Team / Enterprise. This page lays out how the tiers differ, who each is for, how upgrades and downgrades work, and how billing and quotas behave.

Check Out the Four Packages at a Glance

Which Plan Is Right for You?

Free

For trying, personal projects, and learning: single, code, and classifier steps, 1 concurrent run, and up to 5 workflows. The AI assistant is unlimited with your model credentials, but schedules and webhooks are not included.

Pro ($49/mo)

For independent developers and freelancers: unlock all 8 step types, 5 schedules, 3 webhooks, 5 concurrent runs, and the debugger. The AI assistant remains unlimited; LLM token charges go to your provider account.

Team ($99/mo)

A small team of a few people: shared workflows and credentials, division of labour via sharing permissions, 15 concurrent runs, 180 days of execution history, unlimited AI assistant.

Enterprise（Contact Sales）

Mid-size to large companies / strict compliance. Self-hosted deployment, SSO / OIDC, audit logs, 50 concurrent runs, with SLA and support terms set by contract.

Team Seats

The Team plan includes 1 base seat by default. Additional seats are billed at the seat price configured for the account; the current displayed price for monthly Team is $9.9 per seat/month. The checkout page is authoritative for the actual amount and current-period proration.

• Seat capacity belongs to the subscription owner and is shared across all teams owned by that person. The same member uses only 1 seat when joining multiple teams under the same owner.
• Every member except the owner uses a seat, regardless of the member’s role. When a regular user invites a platform administrator to a team, the administrator still uses 1 seat.
• Regular users must complete payment when adding seats. The seats take effect immediately, the payment provider prorates the current charge over the remaining period, and future renewals include the new seat quantity.
• New invitations cannot be sent when no seats are available. Seat reductions take effect in the next billing period, and the target capacity cannot be lower than current usage.

Upgrade

1. Open /pricing Or account settings → Package.
2. Pick the target plan and complete payment on the checkout page.
3. Takes effect immediately — new quotas and features are available right away; how the current period is prorated is whatever the checkout page shows.

Downgrade

1. Account Settings → Package → Select the target package → Click "Downgrade".
2. The system first checks whether the current usage exceeds the target package limit:
   • If you're over the limit, you'll be asked to deal with it first — for example, downgrading from Team to Pro means getting workflows down to 50 or fewer.
   • Anything you can't delete can be archived instead (archived items don't count against quota).
3. Downgraded In Next billing cycle Take effect. The remainder of the current billing cycle will still be used according to the original package quota.

Payment Methods And Invoices

• Subscriptions are paid for at checkout. The pricing page has a monthly / yearly switch at the top; whether yearly is offered and what discount applies is whatever that page shows. The available payment channels are likewise whatever checkout actually shows.
• Enterprise can pay by corporate bank transfer with invoicing — contact sales to sign a contract.

Account settings → Billing lists every payment so you can reconcile transactions. For a tax invoice, contact the support team.

Refunds & Cancellation

• Monthly subscriptions can be canceled anytime; after cancellation the current period runs to its end and doesn't renew.
• Refund terms follow the subscription agreement; Enterprise follows the signed contract.

How Quota Limits Are Enforced

Limits are checked server-side and are safe even in multi-instance clusters. When a limit is hit, new creation requests are rejected while existing resources are untouched. Three kinds of overage map to three machine-readable error codes:

• Creating workflows / schedules / Webhooks past the plan's count limit — HTTP 403, with code resource_limit_reached
• Runtime allowances such as concurrent runs are exceeded — HTTP 429, code quota_exceeded
• Using a feature your plan doesn't include (say, opening the debugger on Free) — HTTP 403, with code feature_not_available

For example, creating a 6th workflow on Free:

{
  "error": "workflows limit reached (5/5)",
  "code": "resource_limit_reached",
  "resource": "workflows",
  "currentCount": 5,
  "limit": 5
}

The UI shows a clear message guiding you to upgrade or archive unused resources.

AI Assistant and Gating of Advanced Functions

Beyond resource counts, these features are also plan-controlled:

• Breakpoint Debugger — Not on Free; available from Pro
• AI Assistant — All plans include unlimited use with the user's own model credentials.
• Advanced step types — Free has only single / code / classifier; group_chat, agent_based, state_machine, sub_workflow, and manual_approval require Pro or above
• Version Management & Batch Runs — Pro and up
• Rerun from a Chosen Step — Pro and up
• Team Collaboration — Team and up (Pro can view shared workflows but not edit them)
• Audit Log — Enterprise Only
• SSO / OIDC — Enterprise Only

Trial

The Free tier has no time limit, so you can get a workflow running before deciding. Whether Pro / Team have trial offers is per the pricing page and in-product notices; when a trial ends you drop back to Free automatically.

FAQ

I’m an Individual Developer, but My Workflow Is Used by Many Colleagues. How Is Usage Counted?

Count the people who log in — if you're the only one operating Braidrun, Pro is enough even when the workflow's output serves many people. You only need Team when colleagues also log in to edit and manage together.

Can I pay as I go?

Currently subscription only. Enterprise can negotiate billing based on the number of executions or per seat.

Next

• Pricing Details Page — Upgrade directly within the product