Billing

FlareX runs on Stripe. Plans are monthly subscriptions with included AI credits, compute limits, and storage allowances. Usage beyond your plan cap can be billed as metered overage if you opt in.

See the pricing page for up-to-date plan limits.

What's in a plan

Each plan includes:

• AI credits — tokens consumed by AI-backed chat generation. See below.
• Bot count — max active bots per workspace.
• Team seats — workspace members (including you).
• Compute — per-bot vCPU and RAM caps.
• Storage — shared allowance across bots in the workspace.
• Log retention — how far back per-bot logs stay queryable.

AI credits

An AI credit is a unit of chat generation. FlareX meters each chat-side AI call — proposals, explanations, diffs, everything the chat panel generates. Message edits and diff-view loads are not metered (they don't re-trigger generation).

The per-workspace cost breakdown under Usage shows exactly which bots and which chat threads consumed credits this cycle.

Metered overage

Overage is off by default. Enable it in Settings → Billing. When on, usage past your included credits continues at the plan's per-credit rate, invoiced at cycle close.

Toggle uses proration_behavior: 'create_prorations' under the hood — turning overage on mid-cycle doesn't back-bill for credits already consumed.

Upgrading mid-cycle

Click Change plan in Billing. Before confirming, FlareX calls Stripe's invoices.createPreview and shows you the exact proration amount: typically a small immediate charge (or credit if downgrading) that lines your subscription up with the new tier for the remainder of the cycle.

No surprises. Confirm to apply.

Downgrading

Downgrades take effect at the next cycle close — no refund, no disruption. Once the new cycle starts, the new plan's limits kick in.

If your usage would exceed the new plan's limits (e.g., you have 10 bots and you're downgrading to a plan with a cap of 3), the extra bots are paused automatically until you remove them or upgrade back.

Dunning: what happens if an invoice fails

Stripe sends a invoice.payment_failed webhook. FlareX puts your workspace in past_due state:

1. Immediately: a yellow banner appears in the panel linking to the Stripe customer portal to update your card.
2. Deploys still work for the duration of your plan's dunning grace window (3 days Starter, 7 Pro, 14 Enterprise).
3. After grace expires: new deploys are blocked. Your running bots keep running. The banner turns red.
4. Invoice paid: Stripe sends invoice.paid → we flip you back to active → deploys resume. Automatic.

No one is ever locked out of a running bot. We only block new deploys during past-due.

Invoices + customer portal

All invoices are viewable in Settings → Billing → Invoices. Each line-item-itemises your usage. For refunds, chargebacks, or custom terms, open a support ticket.

The Manage billing button opens the Stripe-hosted customer portal: update your card, update your billing email, download invoices, cancel.

Enterprise

Enterprise plans are quoted individually. Common customisations:

• Higher compute / storage / credit caps.
• Dedicated runner pool.
• Contract-level SLAs.
• 14-day dunning grace window.
• SSO for workspace members (planned).

Contact us to start a conversation.

Related

• Pricing — plan comparison and current rates.
• Managing bots — bot count limits per plan.
• Databases — storage overage behaviour.