Engineering notes from the team building the platform.

Routine billing requests drain support time. Learn how a customer self-service portal on a self-hosted billing platform cuts ticket volume as you grow.

Ilinca Bostan

Selling hosting across borders means VAT, GST, and US sales tax. Learn how to automate tax compliance with a self-hosted billing platform.

Mario Marin

Flat plans leave revenue on the table. Learn how usage-based and metered billing work and how to run them on a self-hosted platform for hosting providers.

Ilinca Bostan

Involuntary churn from failed payments quietly drains recurring revenue. Learn how smart dunning management in a self-hosted billing platform recovers it.

Mario Marin

How to choose infrastructure for self-hosted billing: start from requirements, weigh cloud vs on-premise vs hybrid, plan the database, and account for hidden costs.

Mario Marin

What to consider when integrating payment gateways with self-hosted billing: choosing processors, keeping card data out of scope, webhooks, dunning, and redundancy.

Ilinca Bostan

Build trustworthy logging and audit trails for self-hosted billing: capture the right events, keep records immutable, respect privacy, and monitor for anomalies.

Mario Marin

Handle multiple currencies and global tax in a self-hosted billing platform: local pricing, VAT and GST rules, compliant invoices, and full configuration control.

Ilinca Bostan

How to connect billing to provisioning with a self-hosted platform: map lifecycle events, use webhooks and APIs, and build an idempotent, fault-tolerant pipeline.

Mario Marin

A decision framework for choosing between self-hosted and managed billing: weigh team capacity, compliance, control, and total cost before you commit.

Ilinca Bostan

A practical guide to deploying self-hosted FluxBilling on Kubernetes: mapping components, handling state, managing secrets, and rolling out updates safely.

Mario Marin

A safe, repeatable approach to updates and patching for self-hosted billing: prioritize security fixes, test in staging, back up first, use a maintenance window, keep a rollback plan, and read the release notes.

Mario Marin