Skip to content

Billing

Billing is wired for the alpha product, but all alpha plans are priced at $0. Stripe runs in test mode, and paid production monetization is outside the current alpha scope.

Billing page showing alpha pricing, current plan, client usage, AI usage, and available plan tiers.
Billing shows alpha plan limits and $0 plan pricing while Arboris is in alpha. Source: tests/e2e/specs/00-screenshots.spec.ts; authenticated header cropped out.
PlanClient capacityAlpha price
Starter3 clients$0
Core5 clients$0
Professional10 clients$0

Client capacity applies to active clients in the firm. The firm’s self-client is part of the firm/client model.

The Billing page shows the current plan and usage context. Arboris also uses billing data in the Add Client flow so you can see when a new client would exceed current capacity.

When there is one slot remaining, Arboris warns that the next client will require more capacity. When the plan is full, Arboris routes you to Billing before the backend limit blocks client creation.

Stripe checkout, portal, plans, and webhooks exist for the alpha billing flow, but alpha plans do not charge real money.

Use only Stripe test-mode flows and test cards in alpha.

Billing usage includes:

  • Active clients.
  • Current-period Review Runs started.
  • Current-period review reports exported.
  • Usage period dates.
  • AI usage tracking, including tokens, model, and estimated cost.

Usage-based AI billing is not part of alpha. The counters are present for visibility, operational review, and future packaging.

Payment failed and subscription change emails are not built for alpha because there are no real paid plans in the alpha billing flow.