We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
The blog
Tips, tricks & guides on building with Phoenix and Elixir.
Build Stripe auto top-up in Phoenix: save the card, catch low balances, charge off-session exactly once, and handle declines, refunds and disputes safely.
By Liam Killingback
Stripe dunning in Phoenix: keep past_due customers entitled, sync failed-payment webhooks, show a card-update banner and still bill the final period's usage.
By Liam Killingback
API usage tracking in Phoenix per key: hashed keys, a plug that admits against the account quota, per-key caps, revocation and a live LiveView breakdown.
By Liam Killingback
Testing usage-based billing in Elixir with ExUnit: hard caps, races at the limit, frozen-clock period resets, restarts, clusters and prepaid credits.
By Liam Killingback
Grandfathered pricing in Phoenix: version your plans, keep existing customers on the price they bought, keep Stripe in sync and move people only on purpose.
By Liam Killingback
Build a usage-based free trial in Phoenix: capped trial plans, hybrid deadlines, expiring trial credit, clean upgrades and one trial per customer, with Aurora Meter.
By Liam Killingback
Overage billing in Phoenix, end to end: plan allowances, spend caps, live overage totals, and a graduated Stripe metered price that bills usage past the limit.
By Liam Killingback
Add the Stripe Customer Portal to Phoenix the right way: portal sessions, deep links and webhooks that keep plan entitlements in sync with every change.
By Liam Killingback
Aurora Meter 1.0 is out: the MIT core and Pro are now stable under SemVer, with durable events, versioned plans, credit lots and Stripe reconciliation.
By Liam Killingback
Build quota alerts in Phoenix: email customers at 80% and 100% of plan limits, once per period, never lost on failure, with Oban and Aurora Meter.
By Liam Killingback
LLM token billing in Elixir: read real token counts from the provider, hold credit before the call, settle the true cost after, and bill it through Stripe.
By Liam Killingback
Phoenix cluster usage metering done right: per-node ETS counters, delta flushes, PubSub gossip and idempotent batches, so every node agrees on one total.
By Liam Killingback
Metered vs seat-based pricing compared honestly: margins, churn and forecasting, plus the Phoenix code for seats, metered overage and a hybrid plan.
By Liam Killingback
Aurora Meter 0.4.0 brings a prepaid credit ledger to the free MIT core: hold, settle and refund real money in Postgres, with Stripe top-ups in Pro.
By Liam Killingback
Rate limits vs quotas in Phoenix: an ETS counter that protects your servers, a billing-period quota that protects your plan, and the right status code for each.
By Liam Killingback
How to build usage-based billing in Elixir and Phoenix: count usage in ETS, enforce plan limits atomically, and invoice overage through Stripe Billing Meters.
By Liam Killingback
Real-time Phoenix usage metering without touching the database on every request: atomic ETS counters, a flusher to Postgres, PubSub fan-out to LiveView, and cluster-wide totals.
By Liam Killingback
Phoenix feature gating and entitlements from one compile-time plan definition: hard caps that hold under concurrency, metered overage, feature flags, and status-aware downgrades.
By Liam Killingback
