Lago and Verdix solve different parts of billing
Both Lago and Verdix help companies manage complex and usage-based commercial models, but they start from different places:
- Lago starts with product events, billable metrics and pricing plans.
- Verdix starts with the signed customer or partner agreement.
What Lago does
Lago is an open-source, event-based billing platform for subscription, usage-based and hybrid pricing.
Companies send product events to Lago. Lago aggregates those events into billable metrics, applies the relevant plan and pricing rules, and generates invoices. It can also connect invoices to payment providers or pass invoice data to other financial systems.
Lago supports:
- fixed and usage-based charges;
- pricing tiers and dimensions;
- minimum commitments;
- prepaid credits;
- subscriptions;
- customer-specific enterprise plans;
- invoicing;
- payment-provider integrations.
Its plans determine pricing, billing cadence, commitments and invoice rules, while billable metrics determine how incoming events are measured.
What Verdix does
Verdix begins with the signed agreement rather than a predefined product plan.
For customer billing, Verdix:
- interprets the contract;
- identifies rates, thresholds, discounts and billing dates;
- connects those terms to customer-defined operational endpoints;
- retrieves the required usage;
- creates the billing schedule;
- routes it for approval;
- sends approved instructions to the chosen billing or invoicing system.
Verdix also applies the same agreement-to-data model to incoming partner invoices, identifying differences between the agreed terms, operational activity and amount charged.
Key differences
The main architectural difference
Lago's event model requires the product to send raw usage events. Lago aggregates those events into billable metrics, applies the relevant plan and charge model, and produces an invoice. This architecture is well-suited when metering is a central part of the product experience.
Verdix reads the signed agreement, identifies which usage data is needed and retrieves it from an existing operational endpoint. This fits periodic billing cycles where reliable usage data already exists inside the company's systems.
The practical difference is in where the work sits. Lago requires the product team to instrument event pipelines. Verdix requires Finance to define the endpoint from which usage is fetched. Neither is simpler in absolute terms; the right choice depends on whether metering is a product responsibility or a finance workflow.
When Lago may be the better choice
Lago may be stronger when a company needs:
- continuous product-event ingestion;
- real-time or near-real-time usage measurement;
- a central usage ledger;
- flexible aggregation across multiple dimensions;
- prepaid-credit management;
- subscription and hybrid billing;
- native invoice generation;
- control through open-source or self-hosted deployment.
Lago can be deployed through Lago Cloud, on the customer's own infrastructure or through enterprise VPC-style arrangements. This makes it particularly attractive to engineering-led companies that want control over their billing infrastructure.
When Verdix may be the better choice
Verdix may be more suitable when:
- the signed agreement is the commercial source of truth;
- terms vary significantly between customers;
- Finance manually interprets contracts today;
- usage already exists behind reliable internal APIs;
- billing occurs monthly or periodically;
- the company wants to retain Stripe, Fortnox, Visma or its ERP;
- implementing a dedicated event ledger would be unnecessary;
- partner invoices must also be reconciled against agreed terms.
The strongest Verdix buyer is not saying: “We cannot measure product usage.” They are saying: “We already have the data, but Finance still has to translate every agreement and prepare the billing instructions manually.”
Is Lago a competitor or a complement?
It can be both.
They compete when a company is deciding whether to use Lago as the main system for usage measurement, rating and invoicing — or use Verdix to automate billing through its existing stack. The overlap grows when commercial teams can configure custom enterprise plans directly in Lago.
They complement each other when a business needs Lago's metering depth but also manages a large portfolio of bespoke signed agreements. A combined workflow could be:
- Verdix interprets the customer-specific terms from the signed agreement;
- Lago supplies metered usage and performs complex rating;
- an approved invoice is generated;
- payment provider and ERP are updated;
- Verdix separately reconciles incoming partner invoices.
Implementation and pricing considerations
Lago offers a free open-source core and paid cloud or self-hosted premium plans. Its paid packages may include usage-based dimensions such as events ingested, invoices generated or active customers. Exact commercial terms are available from Lago directly.
The licence cost is only one consideration. A Lago implementation may also require:
- event instrumentation;
- customer and subscription mapping;
- billable-metric design;
- plan configuration;
- invoice and payment integrations;
- ongoing monitoring of the usage pipeline.
Verdix reduces this work where suitable operational endpoints already exist, although those endpoints, authentication rules and data mappings still need to be configured.
The takeaway
Choose Lago when you need an open-source, event-based metering and billing engine that can become a central part of your product infrastructure.
Choose Verdix when the main problem is turning bespoke signed agreements and existing operational data into approved customer-billing and partner-reconciliation workflows.
Use both when you need Lago's real-time metering depth and Verdix's agreement interpretation and two-sided financial operations.
Lago measures and bills product consumption. Verdix operationalises what bespoke customer and partner agreements require.