account · billing
Billing
Plan, payment state, usage against the plan contract, and every invoice and receipt. The member-facing half of the billing lifecycle. Operators get the same events in the console Finance group.
Plan
Team
Active
$75.00
USD / month · $15 per seat
Usage this month
Against your Team plan contract.
Relays created2,340 / 5,000
1,000 per seat, 5 seats.
Connections4 / 5
1 per seat, 5 seats.
Context per relay
16,384 tokens
Team ceiling.
Invoices and receipts
Hosted by our payment processor. Every charge, refund, and credit.
| Date | Description | Invoice | Amount | Status | Document |
|---|
Payment method
VISA
•••• 4242
Expires 09 / 2028
What this prototype models. The three states are the ones the platform actually resolves, not invented ones:
Reactivation is webhook-confirmed. Paying opens the processor's hosted invoice page. Paid access returns when the payment is confirmed, not when the member says they paid. Cards clear in seconds, bank debits take up to two business days.
Operator side. Admins see the same lifecycle from the other end in Console, Finance lifecycle: commitments, trials, seat true-up, churn. The Admin rail group here is role-gated and hidden for ordinary members.
active, past_due (retrying, full access retained), and unpaid (dunning exhausted, the
effective tier drops to the Free contract). Switch states above and watch the usage ceilings move: nothing is deleted, only the
limits change, and billing stays reachable in every state.Reactivation is webhook-confirmed. Paying opens the processor's hosted invoice page. Paid access returns when the payment is confirmed, not when the member says they paid. Cards clear in seconds, bank debits take up to two business days.
Operator side. Admins see the same lifecycle from the other end in Console, Finance lifecycle: commitments, trials, seat true-up, churn. The Admin rail group here is role-gated and hidden for ordinary members.