Skip to content
Facteur
FRGet started

The subscription sells features, packs sell volume

Why increasing capacity never changes your subscription — and what is not wired up yet.

The principle

Two kinds of purchase, deliberately separated:

  • The subscription sells features, seats and a retention period.
  • Capacity is bought separately, as prepaid packs valid for twelve months, cumulative, and never lost when the plan changes.

Direct consequence, and this is the point:

Increasing your capacity never changes your subscription.

Prices are on the Pricing page, with a calculator. They are not copied here: a grid written in two places eventually diverges.

Why this model

The dominant model ties capacity to the subscription: to receive more, you move up a tier. On a real account that means a daily limit hit that blocks testing for half a day, an increase that commits you for the whole month, and no way down before the next cycle. Since the price is driven by the daily limit, you have to size for the peak: you pay for provisioned capacity, not consumed capacity.

A test suite does not have a steady rate. That model therefore bills irregularity, which is precisely the irritant this product refuses to reproduce.

Pay-as-you-go

It exists, as a safety net, deliberately priced above the cheapest pack, and bounded by a spending cap you set. It is there so a runaway suite on a Friday evening does not block your tests, not to be the normal mode.

The credit ledger

Your capacity is held by an internal append-only ledger, typed by origin — plan grant, pack, pay-as-you-go, adjustment — with its expiry date.

That ledger is the source of truth, not the payment provider. It is this decoupling that makes packs, downgrading without loss, and the spending cap possible at all.

What is not wired up yet

Better said plainly than discovered:

  • Online payment is not live. Subscriptions, invoices, packs and reconciliation arrive together; the Settings › Billing screen says so.
  • Changing plan goes through us today. It is one of the last operations that is not self-service, and it is treated as a defect to fix, not as a service.
  • No usage history beyond the current month — see quotas-et-retention.