Why We Built a Shared Bandwidth Pool
Splitting GB between residential and mobile balances felt fair, until customers started running out of one while the other sat unused. Here is how we redesigned billing.
Most proxy resellers force you to commit to a network up front: 50 GB residential or 10 GB mobile, no swapping. We did the same in our first version. The feedback was loud and immediate: customers wanted one balance.
## The shared pool Today, every dollar of credit lands in a single pool. Residential and mobile sub-users are provisioned automatically and draw from the same balance. No expiry, no migration UI.
## What it took on the back-end - An append-only ledger keyed on customer + proxy type. - A reconcile loop pulling upstream usage every 5 seconds under a Postgres advisory lock. - A small in-memory negative cache so a degraded upstream cannot stall the customer experience.
The result: a billing model that matches how customers actually buy and use bandwidth.