2026.4.22
Billing, credits, and new Settings
Plans, checkout, and credit metering across every billable operation, plus a Settings area reorganized into a deep-linkable, permission-aware sidebar.
- billing
- credits
- settings
Twenty-one changes shipped in this release. Loquent became a paid platform: plans, checkout, and a credit model that meters every billable operation. Settings was also rebuilt from a flat row of tabs into something an owner can navigate.
Billing and credits
- Plans and checkout — organizations pick a plan, check out, and manage billing from Settings, with a direct link into the payment portal.
- Everything is metered — every billable action, from a voice call to a text, an email, a transcription, or an AI turn, draws through one path with a free-allowance, included-credits, purchased-credits waterfall.
- Usage you can read — a card on the billing settings shows credits consumed this cycle, the breakdown per operation, and the remaining balance.
- Credits everywhere — every customer-facing surface speaks in credits. Minutes and tokens stay internal conversion knobs.
- Bounded overdraft — the general credit pool can go slightly negative up to a configured limit instead of hard-stopping at zero, with the debt reconciled at the next cycle.
- Admin configuration without SQL — a billing panel for keys, conversion rates, plans, and credit packs, backed by an audit trail.
Settings
- A real information architecture — a multi-level sidebar with addressable URLs, so a channel, team, or organization setting can be linked to directly. Sections you cannot administer simply do not appear.
- Consistent pages — every subsection uses the same header and card structure with plain-language descriptions.
- Team members — members, invitations, and pending invites grouped into cards, with a confirmation before revoking an invitation.
- Narrow screens — the sidebar collapses into a grouped picker on a phone.
Reliability
- Per-pull-request previews — every change now gets its own preview environment with live status, so behavior is reviewed rather than imagined.
- Faster builds — build caching and a split between preview and production images cut build time and reduce the chance of a preview tweak reaching production.