Open Source Recurly Alternatives

Lago is the programmable system between product usage and revenue. Events arrive from the application, become billable metrics, pass through pricing and entitlements, and come out as invoices, payments, and revenue, which means pricing can change without billing being rebuilt.

The engine is headless and API-first. Applications, internal tools, and agents reach the same primitives through the REST API, SDKs, webhooks, and an MCP server, while product and finance teams use the interface when a human view is faster. Metering stays independent of payment processing, so Stripe, Adyen, or GoCardless can be connected without a provider's catalog becoming the source of truth.

Pricing can be assembled from whatever usage a product actually generates.

• Token metering: charges by model and by input, output, cache, reasoning, or tool call.
• Compute usage: GPU, CPU, storage, and other consumption billed from events.
• Prepaid credits: balances with automatic top-ups.
• Subscriptions: allowances, minimum commitments, and overages on top of recurring plans.
• Two operating models: Lago Direct bills your own customers, while Lago Embedded gives platforms metering and billing to offer to theirs.

The repository ships a maintained demo that prices three AI requests locally using Docker, curl, and jq. It seeds a disposable organization, reconciles the usage total independently, and retries one transaction to prove that usage does not increase. Nothing leaves the machine, and a cleanup flag removes the isolated Compose project and its data volume afterward.

Meteroid closes the gap between what a customer used and what their invoice says. That gap is where homegrown billing goes wrong, and it widens as soon as a company moves from flat subscriptions toward usage-based or product-led pricing.

It connects to your systems through an API that collects usage and interaction data, then feeds a billing engine that applies your pricing model and generates the invoice. Ingestion is written in Rust for high-throughput events, and the project describes itself as experimental.

One platform is meant to carry monetization end to end, whether the motion is product-led, sales-led or both.

• Usage metering: API requests, tokens, transactions, storage and other raw events become billable metrics in real time, with no pre-aggregation step.
• Pricing models: flat rate, usage-based, tiered or hybrid plans, versioned so a price change never touches existing customers unless you decide it should.
• Subscription lifecycle: upgrades, downgrades, mid-cycle changes and cancellations with full control.
• Quotes: send a quote to close a custom deal, and a signed one creates the subscription and starts billing with no manual handover.
• Invoicing and credit notes: detailed invoices from simple charges through to hybrid usage billing, with corrections issued as credit notes.
• Entitlements and growth tools: feature access and metered limits, plus trials, coupons, add-ons and a self-serve customer portal.

Self-hosting instructions live in the contributing guide, and a free cloud workspace is available for anyone who wants to try the platform before running it.

UniBee is billing software for SaaS companies that have outgrown invoice scripts but do not want to hand a share of revenue to a closed platform. It positions itself against Recurly, Chargebee and Paddle, and grew out of its authors' own years with WooCommerce, WHMCS and KillBill.

The system splits into an API backend, an admin portal and a user portal, each in its own repository, so the billing engine can sit behind an existing product or be used with the portal it ships. Standalone deployment is a Docker Compose stack that brings up the database, Redis and the API together.

Between those parts the recurring revenue cycle is covered end to end.

• Subscriptions: plans are created, updated and canceled from the admin portal.
• Invoicing: invoices are generated and sent to customers automatically.
• Billable metrics: usage is tracked and reported for consumption-based pricing.
• Transactions: payments, refunds and discounts are managed in one place.
• Webhooks: account events are pushed to your own systems in real time.
• Reports: product, plan and transaction data feed reporting on business performance.

Docker, Docker Compose and Git are all a standalone install needs, and the app answers on localhost once every container reports ready. Everything is AGPLv3, with a paid cloud edition for teams that would rather not operate it themselves. Contributions go to the frontend and backend repositories rather than this one.