Open-Source Usage Billing API: Track & Manage Subscriptions

Lago: A New Open-Source Billing Solution for Flexible Subscription and Usage-Based Pricing

If you're building a billing system for your SaaS product, you've probably encountered these challenges: supporting traditional subscriptions while handling usage-based billing (like API calls or storage), implementing flexible pricing models (tiered pricing, volume discounts), all without paying revenue shares to third-party platforms. During my recent research into such tools, I discovered Lago—an open-source project positioned as an "open-source metering and usage-based billing API" aiming to replace commercial solutions like Chargebee, Recurly, or Stripe Billing. Launched in 2022 and already boasting 8k+ stars, Lago's design philosophy and technical implementation warrant attention.

Core Capabilities: End-to-End Support from Metering to Billing

Lago's core value lies in connecting the complete chain of "usage data collection → metering calculations → pricing application → invoice generation", making it particularly suitable for scenarios requiring hybrid billing models. Among its core features, several stand out:

First is its event-driven usage metering system. Unlike traditional billing tools that rely on predefined periodic usage, Lago supports real-time reporting of usage events via API (e.g., "User A made 100 API calls"). The system automatically aggregates and calculates usage, correlating it with corresponding pricing rules. This design makes "if you can track it, you can bill for it" a reality—whether for server resources, feature usage counts, or custom business metrics (like AI model invocation duration), anything describable via an event can be integrated into the billing system.

Second is its support for hybrid pricing models. SaaS pricing strategies are growing increasingly complex: pure subscription (fixed monthly fee), pure usage-based (pay-as-you-go), subscription + usage (base fee + overage), tiered pricing (volume discounts), etc. Lago allows combining these models in a single price plan—for example, setting "base subscription 50/month including 1000 API calls, 0.1 per call beyond that" with daily/weekly/monthly billing cycles. This flexibility is crucial for teams with frequent product iterations—pricing adjustments don't require rebuilding billing logic, just modifying rules via API or admin interface.

Finally, its composable integration capabilities. As an open-source tool, Lago isn't tied to specific payment gateways or CRM systems, but supports integration with any third party via APIs and webhooks: payment processing can connect to Stripe, PayPal, or internal systems; customer data can sync to Salesforce or HubSpot; invoice information can push to QuickBooks and other accounting software. This "plugin-based" design avoids vendor lock-in and facilitates integration with existing enterprise systems.

Technical Implementation: High-Performance Billing Engine in Go

Lago is developed in Go, an interesting choice for billing systems. Go's concurrency model and performance advantages enable efficient handling of large volumes of real-time events—like API call metering in high-concurrency scenarios (imagine tens of thousands of usage events per second). Architecturally, Lago employs a modular design with core components including: event ingestion service (processing real-time metering data), pricing rule engine (calculating charges), and invoice generation module (handling billing logic), with modules communicating via internal APIs for independent scaling or replacement.

Another technical highlight is multi-language client support. Beyond the core service, the project offers SDKs in Go, JavaScript, Python, Ruby, and other languages to lower integration barriers. For example, reporting usage events in Python requires just a few lines of code:

from lago_python_client import Client
client = Client(api_key="your_api_key")
client.events.create({
    "event": {
        "transaction_id": "unique_id",
        "customer_id": "user_123",
        "code": "api_calls",
        "timestamp": "2024-05-20T10:30:00Z",
        "properties": {"quantity": 10}
    }
})

For deployment, Lago provides Docker Compose configuration, enabling local testing with just repository cloning, key generation, and container startup—making it accessible for technical teams to quickly validate functionality.

Comparison with Commercial Solutions: Why Choose Open-Source Billing?

When thinking about billing tools, most teams first consider commercial products like Stripe Billing or Chargebee. Their advantages include maturity, stability, and out-of-the-box functionality, but they have two significant drawbacks: cost structure and flexibility.

Commercial billing tools typically charge revenue shares (e.g., 0.5% for Stripe Billing's free tier) or expensive subscription fees that become substantial as company revenue grows. Lago's self-hosted version is completely free, and its cloud version uses fixed SaaS pricing (no revenue sharing), resulting in significant long-term cost savings.

In terms of flexibility, commercial tools offer "standardized" features that struggle with specialized scenarios. When you need usage calculations based on custom algorithms (like AI model token billing), integration with internal approval workflows, or modified invoice generation logic, commercial APIs often prove insufficiently flexible. As an open-source project, Lago allows direct source code modifications or plugin-based extensions—teams can even fork and deeply customize it, which is critical for specialized billing requirements.

Of course, open-source solutions involve tradeoffs: commercial tools provide ready-made compliance support (like global tax rules), 24/7 customer service, and mature anti-fraud systems—all currently requiring in-house solutions with Lago.

Objective Evaluation: Who Is Lago For? What Are Its Limitations?

Lago's advantages are clear: open-source and free + flexible customization + hybrid billing support. If you're a technically-driven SaaS team needing to rapidly iterate pricing models (e.g., testing different billing strategies in early product stages) or with strong data privacy requirements (needing billing data to remain on your servers), Lago helps avoid commercial tools' cost traps and functional limitations. Its pricing rule engine particularly reduces custom development when products involve both subscriptions and usage-based billing.

However, it has notable limitations:
First, self-hosting requires technical investment. While Docker deployment is simple, production environments need high availability, data backups, and security hardening (for sensitive pricing and invoice data)—creating additional burdens for small teams.
Second, AGPLv3 license restrictions ⚠️. If you develop commercial products based on Lago and provide public services, modified code must be open-sourced, potentially conflicting with some businesses' strategies (though internal self-hosted use is unrestricted).
Finally, ecosystem maturity. Compared to established tools like Stripe, Lago has fewer third-party integration plugins (e.g., regional payment gateways, accounting software), potentially requiring custom adapter development.

Conclusion: When Should You Consider Lago?

Lago is worth trying if:

• Your product needs hybrid billing models (subscription + usage, tiered pricing, etc.) where commercial tools' standardized features are insufficient;
• Your company is cost-sensitive, wants to avoid revenue sharing, or commercial tool subscription fees have become burdensome;
• You have technical capacity to maintain self-hosted services or prefer Lago's cloud version (priced by server scale, no revenue share);
• You have data sovereignty requirements and need complete control over billing data.

Conversely, if your product uses simple subscription billing and scale is small, Stripe Billing may be more convenient; if you need global compliance and mature customer support, commercial tools like Chargebee remain safer choices.

As an emerging player in open-source billing, Lago's design philosophy is noteworthy—it demonstrates that "billing systems" don't require commercial tools, as open-source alternatives can deliver enterprise-grade flexibility. For developers seeking to understand billing system architectures, Lago's source code (especially its event processing and pricing rule engine) offers excellent learning opportunities.

If you're evaluating billing tools, spend 30 minutes running Lago's demo with Docker—it might help you avoid future billing system重构 pitfalls.