Open Source Metering & Usage-Based Billing

The best alternative to Chargebee, Recurly or Stripe Billing.
For usage-based, subscription-based, and all the nuances of pricing in between.

Slack · Website · Issues · Roadmap

Engineers be like…

Read more first-hand experiences from Qonto, Algolia, Pleo, Segment, or the 350+. Hackernews comments here.

The Solution: Lago, the open-source billing API for product-led SaaS

• Event-based: if you can track it, you can charge for it;
• Built for product-led growth companies;
• Hybrid pricing: subscription and usage;
• Hybrid go-to-market motion: self-serve and sales-led.

Open-source, open architecture:

• Composable: connect Lago to any of your internal systems or tools (i.e. any payment gateway, CRM, CPQ, accounting software);
• Pricing: we’re not rent seekers, we’re not asking for a % of your revenue. Our self-hosted version is free. Our cloud version is priced like a SaaS;
• Privacy: your data never has to leave your infrastructure.

• Usage metering: Lago's event-based architecture provides a solid foundation for building a fair pricing model that scales with your business.
• Price plans: Lago supports all pricing models. Create pay-as-you-go and hybrid plans in no time with our intuitive user interface or API.
• Coupons: Create engaging marketing campaigns and increase conversion with coupons that customers can redeem to get a discount.
• Add-ons: Why wait until the end of the billing cycle to get paid? Lago allows you to create one-time charges that are invoiced on the fly.
• Invoicing: Depending on the configuration of your plans, Lago automatically calculates what each customer owes you and generates invoices.
• Prepaid credits: Unlock recurring revenue opportunities for pay-as-you-go pricing models with Lago’s prepaid credit features.

Lago launched its v0.1 on June 2nd, 2022. Lots of new features are coming, and are generally released on a bi-weekly basis. Watch updates of this repository to be notified of future updates.

Check out our public roadmap

Distributed under the AGPLv3 License. Read more here.

1. Install Docker on your machine;
2. Make sure Docker Compose is installed and available (it should be the case if you have chosen to install Docker via Docker Desktop); and
3. Make sure Git is installed on your machine.

To start using Lago, run the following commands in a shell:

# Get the code
git clone https://github.com/getlago/lago.git

# Go to Lago folder
cd lago

# Set up environment configuration
echo "LAGO_RSA_PRIVATE_KEY=\"`openssl genrsa 2048 | base64`\"" >> .env
source .env

# Start the api
docker compose up -d api

# Create the database
docker compose exec api rails db:create
docker compose exec api rails db:migrate

# Start all other components
docker compose up

docker compose up

You can now open your browser and go to http://localhost to connect to the application. Lago's API is exposed at http://localhost:3000.

Note that if our docker server is not at http://localhost, the following env variables must be set: LAGO_API_URL. This may be on the command line or in your .env file. For example:

LAGO_API_URL="http://192.168.122.71:3000"
LAGO_FRONT_URL="http://192.168.122.71"

Your API Key can be found directly in the UI:

1. Access the Developer section from the sidebar;
2. The first tab of this section is related to your API keys; and
3. Click the Copy button to copy it to clipboard.

Please note that Lago, by default, tracks basic actions performed on your self-hosted instance. If you do not disable tracking, you may receive specific communications or product updates. However, rest assured that Lago will not collect any personal information about your customers or financial information about your invoices.

If you would like to know more about Lago's analytics or remove the entire tracking, please refer to this page for comprehensive information.

Docker images are always updated to the last stable version in the docker-compose.yml file. You can use a different tag if needed by checking the releases list.

Lago uses the following environment variables to configure the components of the application. You can override them to customise your setup. Take a closer look are our documentation.

Contact our team at hello@getlago.com to get started with Lago Cloud. More information on our website.

• See the documentation to learn more about all the features;
• Use our templates to get inspiration and learn how to reproduce Algolia’s, Segment’s and Klaviyo’s pricing models;
• Join our Slack community if you need help, or want to chat, we’re here to help;
• Contribute on GitHub: read our guidelines;
• Follow us on Twitter for the latest news;
• You can email us as well: hello@getlago.com.

You can follow this guide to set up a Lago development environment on your machine. This guide is intended for people willing to contribute to Lago. If you want to try Lago on your local system, we recommend that you take a look at Lago's public documentation.

You can contribute by following our guidelines.

B2B SaaS has evolved, but billing has not yet.

Pricings are now mostly hybrid: they include a usage-based component (i.e. “if you use more you pay more”) and a subscription component (i.e. a recurring fee for basic usage).

Not all software companies will go full “usage-based” like Snowflake for instance. This model is the new standard for cloud infrastructure products. However, in other areas of SaaS, users want to know beforehand how much they will pay to control their spending and software companies want to be able to predict recurring revenues.

SaaS used to be either self-service (SMBs) or sales-led (Enterprises). Go-to-market now mixes the self-service (all customers access the same price plans) and sales-led (customers get a custom quote from a sales representative) motions. A typical journey involves an individual contributor in a company who tests a new tool, puts their corporate credit card in, and starts spreading the use of the tool within the organization. At that point, the VP or head of department might want to upgrade to a custom plan tailored to the needs of the whole organization. As a result, billing needs to be flexible, automated, and transparent enough to embrace this hybrid go-to-market motion as well.

Why do payment companies take a cut on revenues? Because the higher the amount, the higher the risk for them (e.g. fraud, disputes, etc.).

Why did billing companies adopt the same pricing structure? We’re not able to provide an answer that makes sense. It’s been said on the internet that they did this because they could (read more here).

Lago is agnostic and we aim at being as transparent as possible, so we won’t nudge or lock you into using a specific tool in exchange for using our billing API (learn more).