Orbit runs the full life of a subscription business: plans, subscriptions, recurring invoices, payments and revenue reporting, with an idempotent billing engine enforced by the database itself. Offline-first, on your own PostgreSQL.
0
duplicate invoices, ever
₹1,639.62
invoice just generated
100%
offline, no internet
INV-2026-00006
Acme Stores Pvt Ltd · due Nov 15
from SUB-2026-00001
period 2026-10-01 → 2026-11-01
| Brightloop CRM (Odoo), Oct 1 → Nov 1 | 1 | 1,559.00 | 1,559.00 |
| GST 18% | — | — | 280.62 |
| LAUNCH200, launch discount | — | — | −200.00 |
UNIQUE(subscription_id, period_start) — the database refuses a second invoice for this period
Live artifact from the demo dataset, every number computed by the engine
Renewals get missed, invoices go out wrong, and nobody can say how much recurring revenue the company actually has. Orbit replaces that whole month.
From a new customer signing up to the finance lead closing the month: the seven moments that break a spreadsheet workflow, each a working part of Orbit.
Customers self-signup with a real password policy and hashed, single-use reset links staged in a mail outbox. Admin, staff and customer see three different systems behind one login, RBAC enforced server-side, citext-unique emails.
Products with attributes and variants, the Odoo brand adds ₹560 with price_extra. Plans carry billing period, minimum quantity, availability windows and per-plan flags: auto-close, closable-early, pausable, renewable.
Sales starts from a quotation template with pre-filled lines and a validity window, then walks one state machine: Draft → Quotation → Confirmed → Active → Closed, with every transition recorded by actor and timestamp.
Hundreds of subscriptions due at once become invoices with snapshot lines, per-line tax, discounts and gapless numbers. Re-run the same day and the database reports “0 created · 4 skipped (already billed)”, nothing billed twice, nothing skipped, catch-up built in.
Admin-set rules, percent or fixed, minimums, date windows, usage limits, product or subscription scope. The next invoice carries the discount on its own line, stops on expiry or exhaustion, and keeps a usage ledger.
Record a payment by UPI, card, cash, transfer or cheque; the invoice flips to Paid inside the same transaction, overpayments rejected. Overdue invoices surface instantly, and one click stages a reminder in the outbox.
Active subscriptions, revenue received, amount owed, overdue aging buckets, MRR and ARR with movement (new · expansion · contraction · churn), renewal forecast, revenue by plan, one summary, filterable, exportable to CSV.
Most subscription tools promise careful billing. Orbit makes it a database-level property you can demonstrate, not a convention you hope for.
Never twice. A UNIQUE(subscription_id, period_start) constraint makes a duplicate period physically impossible.
Never concurrent. pg_try_advisory_xact_lock serializes billing runs — cron and the button cannot overlap.
Never skipped. The catch-up loop invoices every missed period after downtime, one invoice per period, capped at 12.
Never partial. Each subscription runs under a SAVEPOINT: one failure rolls back only that subscription, never the run.
-- a billing run, replayed the same day
orbit> billing.run(asOf: today)
{ created: 4, skipped: 0, errors: 0 }
orbit> billing.run(asOf: today)
{ created: 0, skipped: 4 (already billed), errors: 0 }
-- the constraint that makes it true
UNIQUE(subscription_id, period_start)
No abstractions: the lifecycle a subscription walks, the pipeline the engine runs every billing day, and exactly how one invoice gets its total.
Admin adds products, variants, plans, taxes
Template → quotation → confirmed → active
Engine invoices every due period, idempotently
Payments settle invoices; overdue gets chased
Owns the system: products, plans, taxes, discount rules, staff, billing runs, outbox, audit trail.
Runs the month: quotations, subscriptions, invoices, payments, billing day — no staff mgmt, no discount rules.
A portal of their own: subscriptions, invoices, print, pause/resume/renew — only their data, ever.
Every figure below is reproducible: volume-seed the database, run the EXPLAIN ANALYZE kit, or execute the flow verifier. Numbers ship with their scripts.
10,007
subscriptions seeded for the perf proof
10.55 ms
slowest dashboard query (budget: 2 s)
17
CHECK constraints holding business rules
142
automated tests on the billing core
12/12
end-to-end flows verified green
0
external dependencies, runs fully offline
Local-first by design: the whole demo runs with the WiFi off — local PostgreSQL, a node-cron billing worker, and mail staged in an outbox table instead of SMTP. No fonts from a CDN, no cloud APIs, no mocks.
Create an account and run your first billing day in minutes, or sign in to the demo workspace and watch the engine skip an already-billed one.
Three seeded accounts, three different views of the same system.
Admin
everything: catalog, discounts, billing runs, staff, outbox
Staff
day-to-day: subscriptions, invoices, payments, billing day
Customer
the portal: Acme's own subscriptions and invoices only
Seeded demo accounts — the entire workspace resets with one seed run. Not for any real deployment.