Open Source Alternatives LogoOpen Source Alternatives
AlternativesBlogAdvertise
Open Source Alternatives LogoOpen Source Alternatives

Stay Updated

Subscribe to our newsletter for the latest news and updates about Alternatives

Open Source Alternatives LogoOpen Source Alternatives

Handpicked Open Source Alternatives to Paid Softwares

Product
  • Search
  • Categories
  • Tag
  • Sign In
Resources
  • Blog
  • Collection
  • Submit
  • Advertise your tool
Company
  • Privacy Policy
  • Terms of Service
  • Refund Policy
  • Sitemap
Copyright © 2026 All Rights Reserved.
Home/Categories/Finance & Fintech/Lago
icon of Lago

Lago

Open source alternative to Stripe Billing, Chargebee and Zuora

Lago is an open source usage-based billing API for SaaS companies that need metered, hybrid, or consumption-based pricing without Stripe Billing's subscription model constraints. AGPL-3.0 licensed.

9.7K starsGoAGPL-3.0
image of Lago
Contents
  1. 01Who Lago is for

Repository

Stars
9.7K
Forks
614
License
AGPL-3.0
Latest
v1.47.0
Last commit
5 days ago
Last verified
May 29, 2026
Repo
getlago/lago ↗

Additional details

Active this week
Visit websiteGitHub repo
  • 02The problem it solves
  • 03How it solves it
  • 04Strengths and trade-offs
  • 05Lago vs alternatives
  • 06Tech stack
  • 07FAQ
  • 08Similar open-source tools
    • TL;DR

    Lago is an open source billing platform for usage-based, subscription, and hybrid pricing. It replaces custom billing code and proprietary billing infrastructure when product-led companies need metering, invoicing, entitlements, and payment orchestration under their control. Best for SaaS teams with pricing models that Stripe Billing alone does not model cleanly.AGPL-3.0 · Go · 9.7K stars · Active this week

    who it's for

    Who Lago is for#

    SaaS teams with usage pricing

    Lago fits products that bill by seats, events, credits, usage tiers, or hybrid models where simple recurring plans are not enough.

    Skip if:

    Skip if your pricing is a single flat monthly subscription handled cleanly by your payment processor.

    Platforms needing billing ownership

    Use it when billing data, entitlement decisions, and payment routing need to stay inspectable and portable.

    Skip if:

    Skip if finance operations require a fully managed enterprise billing suite first.

    the problem

    The problem it solves#

    how Lago solves it

    How it solves it#

    Usage and subscription billing

    Supports usage-based, subscription-based, and hybrid pricing models with real-time event ingestion and aggregation.

    Payment-agnostic architecture

    Works with Stripe, Adyen, GoCardless, or another gateway instead of forcing one payment processor.

    Entitlements and revenue workflows

    Connects feature access, invoicing, cash collection, revenue analytics, embedded billing, and integrations around one billing platform.

    strengths · trade-offs

    Strengths and trade-offs#

    Strengths

    • Billing logic you can inspectLago gives teams source access for billing workflows that are often trapped inside a proprietary billing vendor.
    • API-first billing operationsThe README states every feature is available through the REST API, which fits product-led billing automation.

    Trade-offs

    • -Billing infrastructure demands careRunning billing yourself means you own uptime, data accuracy, invoice testing, and payment-provider integration behavior. A managed billing vendor may reduce operational load.
    versus alternatives

    Lago vs alternatives#

    tech stack · detected from GitHub

    What it's built on#

    Languages
    GoRuby
    Frameworks
    React
    frequently asked

    FAQ#

    What is Lago used for?

    Lago is used for metering, billing, invoicing, entitlements, cash collection, and revenue workflows for SaaS pricing models.

    Is Lago open source?

    Yes. Lago is positioned as an open source billing platform, and the repository is AGPL-3.0 licensed.

    Can Lago replace Stripe Billing?
    also worth a look

    Similar open-source tools#

    Billing SDK

    Billing SDK

    Open source React components for SaaS billing flows

    453TypeScriptGPL-3.0
    Zoneless

    Zoneless

    Open source payout platform for global marketplace payments

    294TypeScriptApache-2.0
    Supabase

    Supabase

    Open source Firebase: Postgres database, auth, and file storage

    102.3KTypeScriptApache-2.0
    Soketi

    Soketi

    Self-hosted Pusher-compatible WebSocket server, open source

    5.6KTypeScriptAGPL-3.0
    Sylius

    Sylius

    Headless Symfony commerce for complex B2B and B2C stores

    8.5KPHPMIT
    Saleor

    Saleor

    Open source headless e-commerce platform with GraphQL API

    22.9KPythonBSD-3-Clause
    Language
    Go
    Open issues
    18
    Contributors
    49
    First release
    2022

    Categories

    Finance & FintechAPIs & IntegrationBackend Development

    Tags

    API InfrastructureInvoicing & PaymentsPayment InfrastructureSelf HostedOpen CoreDeveloper ToolsCloud Native

    Billing becomes risky when product usage, plan entitlements, invoices, payment providers, and revenue reporting all live in separate systems. Teams either build billing logic into application code or accept proprietary workflows that are hard to inspect when money, taxes, and customer access are on the line.

    Lago vs Stripe Billing

    Lago is the stronger choice when usage metering, entitlements, and billing rules need to live in an inspectable open source platform. Stripe Billing is still a better fit when a team wants the shortest path to managed subscription billing inside the Stripe ecosystem.

    Lago can replace or sit beside Stripe Billing when you need more control over usage metering, entitlements, and multi-gateway billing. Stripe Billing may be simpler for basic subscription plans.