A customer billing portal built to reduce "can you resend the invoice?
Hey HN, A recurring problem we kept running into with billing systems was the human layer around them. Customers asking: “What’s my current balance?”“Which invoice is pending?”“Why did usage spike last week?”And the answer was usually someone digging through dashboards, exporting PDFs, or pasting screenshots. So we built a read-only customer billing portal inside Flexprice (open-source metering + billing infra). It gives customers visibility into: subscriptions and billing periodsprepaid wallet balances and credit transactionsinvoices (status, search, download)feature-level usage and cost…
What it does
In the maker’s words, at launch
Hey HN, A recurring problem we kept running into with billing systems was the human layer around them. Customers asking: “What’s my current balance?”“Which invoice is pending?”“Why did usage spike last week?”And the answer was usually someone digging through dashboards, exporting PDFs, or pasting screenshots. So we built a read-only customer billing portal inside Flexprice (open-source metering + billing infra). It gives customers visibility into: subscriptions and billing periodsprepaid wallet balances and credit transactionsinvoices (status, search, download)feature-level usage and cost breakdowns Docs (including API + session model): https://docs.flexprice.io/docs/customers/customer-portal Curious how others here approach customer-facing billing UX, especially around access control and audit-ability. Happy to answer questions or drop-in by our community if you have anything particular - http://bit.ly/4huvkDm
Does the same job
all alternatives →
- FOFlexprice: Open-Source Usage-Based Billing Toolkit2025 · ▲7
Hey HN, I’am Koshima, co-founder of Flexprice (https://flexprice.io/). Flexprice is an open source monetization platform for AI & Agentic companies. You can build usage-based, credit-based, or hybrid pricing models with full control. Usage-based billing works on paper, but breaks fast in production: (1) High-volume data (e.g., 10k API calls/sec from AI inferences) breaks naive pipelines, dropping events and causing underbilling or customer complaints. (2) Backfilling missing events or retroactive discounts screws up invoices, forcing 3 AM log stitching to avoid revenue…
More dev tools this month
the category →
Open-source GTM skills for technical founders
Dev tools · 29d ago · gtmcofounder.com
OpenTrailPaper is open-source bike computer firmware for the LilyGO T5S3 4.7" E-Paper PRO. It supports offline maps, GPX routes, FIT recording and Bluetooth sensors.
Dev tools · 2d ago · opentrailpaper.com
