Billing & Invoicing
Lago
Rest of world Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 4 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Get Lago Corp. · getlago.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Lago at a glance
- Vendor
- Get Lago Corp.
- Headquarters
- Incorporated in United States source, captured 26 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 26 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 26 Oct 2026
- Panel verdict
- The AI panel rates Lago 3/5, the mean of 6 judges. Lago, from Get Lago Corp., a Delaware corporation, is an open-source usage-based billing platform offered as Lago Cloud or self-hosted on-prem or in a VPC. how scores are made
- As of
- Vendor pages captured 26 Oct 2026; evaluated by the panel 28 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Lago, from Get Lago Corp., a Delaware corporation, is an open-source usage-based billing platform offered as Lago Cloud or self-hosted on-prem or in a VPC. Its highest scores come on the subscription engine and collections and dunning: proration is documented to a formula with a worked example, price changes roll into future invoices while finalized invoices stay immutable, and dunning campaigns carry per-currency triggers, configurable attempts and a Dunning Agent reading twelve months of payment history. The lowest scores land on sovereignty and pricing transparency: the contracting entity is a Delaware corporation, we found no public information on cloud hosting location or subprocessors, and the captured pages show no price figures for the Starter, Pro, Business or Enterprise tiers, with tax integrations, quotes and accounting connectors on request. Tax handling rests on seller-configured VAT rates and an Anrok integration for US sales tax, with no public information on reverse charge, VIES validation or OSS reporting. No criterion split the judges by more than two points, and the flagged splits list none.
Speaks for it
- Mid-cycle subscription mechanics are documented to an explicit proration formula with a worked example, and price changes roll into future invoices while finalized invoices stay immutable.
- Structured e-invoicing to EN 16931 ships as Factur-X PDF/A-3 and standalone UBL XML for invoices, credit notes and receipts, downloadable from the interface and the API.
- Corrections run through credit notes as separate records with six reasons and allocation across offset, refund or wallet, and accounting documents are retained for seven years.
- Dunning is configurable per billing entity or customer with per-currency triggers and configurable attempts, and a Dunning Agent reads twelve months of payment history and escalates large accounts to a person.
- MRR reporting splits movements into new, expansion, contraction and churn with upgrades counted at the difference only, filterable down to a single customer.
Held against it
- The contracting entity is Get Lago Corp., a Delaware corporation, and we found no public information on hosting location or subprocessors for the cloud service.
- The captured pages show no price figures for any tier, and tax integrations, quotes and credit notes sit behind premium or on-request gates.
- VAT rates are configured per charge or as a customer default rather than computed by location, and we found no public information on reverse charge, VIES validation or OSS reporting.
- We found no public information on Peppol, XRechnung, sequential numbering or GoBD archiving, and the French mandate role is document generation for a partner platform rather than transmission to the tax authority.
- Revenue recognition is marked private beta, and we found no public information on a DATEV export or a complete export of customer and subscription data a successor system could import.
Best for
- You bill metered usage — per-token-type rates, prepaid credits, plan overrides — alongside subscriptions and want mid-cycle changes handled by documented rules.
- You rely on dunning to recover overdue invoices and want campaigns scoped per billing entity or customer, with recovery reported per currency.
- You will run the system yourself on-prem or in a VPC to keep the billing chain under your own control.
- You need EN 16931 e-invoice files (Factur-X or UBL) for invoices, credit notes and receipts to hand to a partner platform.
Avoid if
- You need to budget an annual cost from public pages — tier names are published without price figures and final pricing runs through an order form.
- You sell B2B across the EU and need location-driven VAT — the documented model is seller-configured rates plus an Anrok integration, with no public information on reverse charge, VIES validation or OSS reporting.
- You must sign with a European entity for a hosted billing system — ask the vendor: the public pages we read do not show it
The scores
| Criterion | Panel median |
|---|---|
| Plans, pricing models & subscription lifecycle | 4 of 5 |
| Invoices & e-invoicing compliance | 3.5 of 5 |
| Cross-border VAT & tax handling | 2.5 of 5 |
| Payment collection, dunning & portability | 3.5 of 5 |
| Revenue reporting & accounting handoff | 3.5 of 5 |
| European sovereignty | 1.5 of 5 |
| Pricing transparency | 1.5 of 5 |
Plans, pricing models & subscription lifecycle
Show reasoningHide reasoning
How this is scored
How the product models what is sold and to whom: plans, add-ons and price points, trials, upgrades and downgrades with proration, usage-based and seat-based pricing, contract terms and renewals, quotes, and a self-service portal where the customer changes or cancels their own subscription.
0 — No subscription model; recurring charges are set up by hand per customer or per invoice.
3 — A recurring invoice or a fixed plan that repeats on a schedule, but no proration, no trials, no add-ons and no usage component.
5 — Plans with add-ons and trials, upgrades and downgrades with proration, renewals and cancellations handled by the system, and a customer portal for viewing and changing the subscription.
8 — Usage-based, tiered, volume and seat-based pricing with metering through an API, contracts with minimum terms, ramps and notice periods, quotes that convert into subscriptions, multiple currencies and price books, and the subscription history kept per customer.
10 — The commercial model lives in the product: hybrid pricing (commitments, prepaid credits, overage) without custom code, price changes rolled out to existing customers with grandfathering, entitlements exposed to the selling application, and every change to a subscription versioned and attributed.
The SaaS Founder
Usage metering, prepaid credits, entitlements and quotes are all present, and the mid-cycle mechanics are documented in real depth: a worked proration example, anniversary versus calendar anchors, upgrades that preserve the original billing date, terminations that credit unused advance days, and price changes that propagate into draft and future invoices while finalized invoices stay immutable. The captured pages show customers remaining on older plan versions and audit logs for activity, but give no managed grandfathering choice for a price change and no stated versioned record of every subscription change. 1 2 5 6 10
The Finance Lead
Usage metering with billable metrics, prepaid credits and per-token rates, a customer portal, plus quotes and entitlements modules, put the commercial model in the product; upgrades prorate by a documented formula, and price changes flow into draft and future invoices while finalized invoices stay immutable. I found no public information on trials for my customers' own plans, grandfathering on price changes, or seat-based and tiered price books. 1 2 5 6
The Billing Engineer
Usage metering through the API with billable metrics, prepaid credits, plan overrides per client, a customer portal, and quotes and order forms (on request) are all documented, and mid-cycle changes prorate by an explicit days-remaining formula with calendar and anniversary anchors. A price change on a plan rolls into future invoices while finalized invoices stay immutable, and entitlements exist as a module the selling application can use. I found no public information on contract minimum terms, ramps, or grandfathering for existing customers, so I score the level the documents reach. 1 2 5 6
The Service-Business Owner
Metered usage billed through an API, proration with a worked example, mid-cycle upgrades that keep or reset the anniversary anchor, and price changes that flow into draft and future invoices while finalized invoices stay immutable — that is close to how I need retainer price increases handled. A customer portal, prepaid credits, plan overrides and grace periods are documented, though quotes sit behind a request. What I found no public information on: contract minimum terms, notice periods and ramps, or seat and volume tiers. 1 2 5 6
The Tax Adviser
Proration is documented down to the formula and a worked example, mid-cycle upgrades preserve the anniversary date when the same external ID is used, and plan overrides, prepaid credits combined with subscriptions, per-customer usage attribution and entitlements are all on the public pages — a genuine hybrid usage-plus-subscription model. Quotes and order forms exist as an add-on and invoices carry multiple currencies. We found no public information on tiered or seat-based price models, price books, or contract minimum terms with notice periods. 1 2 5 6
The Skeptic
Usage metering through an API, subscriptions combined with prepaid credits and commitment top-ups, entitlements as a listed module, plan overrides per client, and documented proration with mid-cycle upgrades that preserve or reset the billing anchor put the commercial model inside the product. Price changes on a plan roll onto existing customers' future invoices with finalized invoices immutable. We found no public information on grandfathering, end-customer trials, or contracts with minimum terms and ramps, and quotes and order forms are an add-on on request. 1 2 5 6
Invoices & e-invoicing compliance
Show reasoningHide reasoning
How this is scored
Whether the invoices the product issues are legally valid where the customer is: mandatory invoice content, sequential numbering, credit notes and cancellations instead of edits, retention and archiving to GoBD, and structured e-invoices (XRechnung, ZUGFeRD/Factur-X, Peppol) for business customers and public bodies.
0 — No invoices; the product charges cards or sends payment requests and the seller writes invoices elsewhere.
3 — PDF invoices from a template, but numbering, mandatory content, corrections and retention are not described.
5 — Invoices with sequential numbering and the mandatory content stated, credit notes and cancellations instead of edits, invoices in several languages and currencies, and a documented archive.
8 — Structured e-invoices to EN 16931 issued as XRechnung or ZUGFeRD/Factur-X and sent through Peppol, GoBD-compliant numbering and unalterable archiving stated, invoice data exportable for a tax audit, and the e-invoicing mandates in named EU countries addressed.
10 — Invoicing that stands up in any audit it may face: e-invoicing to public bodies and businesses in several EU countries with the channels named, clearance and reporting models (France, Italy, Poland) supported where they apply, a Verfahrensdokumentation or equivalent offered, and every invoice traceable to the subscription event that produced it.
The SaaS Founder
Structured e-invoices to EN 16931 are real — Factur-X and standalone UBL XML covering invoices, credit notes and payment receipts, downloadable in the UI and via the API — with the French mandate addressed and the vendor stating plainly that it generates the documents a PDP requires and is not itself a registered PDP transmitting to the tax authority. Credit notes are modeled correctly as separate records that never rewrite the invoice, with offset, refund and wallet destinations, and seven-year retention of accounting documents is stated. We found no public information on XRechnung, Peppol transmission, sequential numbering or GoBD archiving, which I would need across nine EU countries. 7 8 3 2
The Finance Lead
Credit notes are separate records that never rewrite a finalized invoice, finalized invoices are immutable, invoices and accounting documents are kept for seven years, and the engine generates Factur-X PDF/A-3 and UBL EN 16931 documents for invoices, credit notes and receipts, downloadable from the interface and the API — with a clearly stated role in the French reform as a document generator working with a partner platform rather than a transmitter to the tax authority. I found no public information on sequential numbering rules, mandatory invoice content, Peppol transmission, XRechnung, or GoBD-conform archiving, so I cannot confirm audit readiness for Germany from these pages. 3 6 7 8
The Billing Engineer
Credit notes are a separate record that never rewrites a finalized invoice, finalized invoices are immutable, and invoices are kept seven years in accordance with accounting laws. Structured e-invoicing to EN 16931 is real — Factur-X as PDF/A-3 with embedded XML and standalone UBL XML, downloadable from the UI or API for invoices, credit notes and receipts — and the French mandate is addressed with a clear role statement: Lago generates the compliant documents a certified French platform requires and does not transmit to the tax authority itself. I found no public information on sequential numbering rules, Peppol transmission, GoBD archiving or a Verfahrensdokumentation, so I cannot take this to the audit-proof level. 3 6 7 8
The Service-Business Owner
Structured e-invoices to EN 16931 are documented as Factur-X PDF/A-3 or standalone UBL XML, covering invoices, credit notes and receipts, and credit notes are separate records that never rewrite a finalized invoice — solid correction mechanics. For my public-sector customers the gaps decide it: XRechnung, Peppol, sequential numbering, GoBD archiving and a Verfahrensdokumentation are not named anywhere, and for the French reform the vendor states it generates documents for a PDP but transmits nothing to the tax authority itself. 7 8
The Tax Adviser
Finalized invoices are immutable and every correction runs through a credit note recorded as a separate document with six stated reasons and allocation across offset, refund and prepaid wallet — exactly the discipline I want to see at year-end, with invoiced accounting documents retained for seven years. Structured invoices come as Factur-X PDF/A-3 with embedded EN 16931 XML and as standalone UBL, covering invoices, credit notes and receipts, and the French mandate role is stated plainly: Lago generates the compliant documents a PDP requires and does not transmit to the tax authority itself. We found no public information on sequential numbering rules, GoBD-compliant archiving, XRechnung, Peppol or a Verfahrensdokumentation. 3 6 7 8
The Skeptic
Structured e-invoices to EN 16931 ship as Factur-X PDF/A-3 and standalone UBL XML for invoices, credit notes and receipts, with corrections made by credit note rather than edits, finalized invoices immutable, and seven-year retention of accounting documents stated. For the French mandate the vendor says plainly it is not a PDP and does not transmit invoices to the tax authority — it generates files a third party must send. We found no public information on sequential numbering, mandatory invoice content, GoBD archiving, XRechnung, Peppol transmission or a Verfahrensdokumentation, so the formats are ahead of the audit posture. 3 6 7 8
Cross-border VAT & tax handling
Show reasoningHide reasoning
How this is scored
How the product gets tax right when the seller sells across borders: VAT rates per country and product type, reverse charge for business customers with VAT ID validation (VIES), the EU One-Stop-Shop, US sales tax — or, for a merchant of record, which tax liability it takes on in its contract and which it leaves with the seller.
0 — No tax handling; the seller types the rate on every invoice.
3 — One configurable VAT rate or a manual rate table, with no customer-location logic and no VAT ID check.
5 — Tax rates applied by customer country and status, reverse charge for business customers with a VAT ID field, and tax shown correctly on invoices and in reports.
8 — Automatic VAT per country and product type, VIES validation of VAT IDs, OSS reporting data, evidence of customer location kept, US sales tax through a named engine — or a merchant-of-record contract that states the tax liability it assumes and in which countries.
10 — Tax is discharged and evidenced: filings or filing data for OSS and the countries sold into, rate changes maintained by the vendor with a stated process, tax decisions per invoice explainable, and the division of liability between seller and vendor written into the terms.
The SaaS Founder
An Anrok integration resolves tax jurisdictions from customer addresses and raises an error when they are incomplete, but it is an add-on, and although customer records carry a tax ID (the analytics filter on it proves that), we found no public information on reverse charge, VIES validation or OSS reporting — exactly what I need to stop thinking about when selling B2B across the EU. 9 10 2 13
The Finance Lead
VAT rates are configured on each recurring charge or fall back to a customer default rate — manual assignment rather than country-automated — while a named engine, Anrok, resolves US sales tax from customer addresses, with errors surfacing through a webhook. Tax IDs are stored per customer and tax appears on invoices and in the recovery reports, but I found no public information on reverse charge for business customers, VIES validation, or One-Stop-Shop reporting, which is what I would need for EU cross-border sales. 2 9 10 13
The Billing Engineer
VAT is applied at the charge level with a customer-level fallback rate on the whole invoice, and the Anrok integration resolves US sales tax jurisdictions from address fields, with a documented webhook fired when the address is too incomplete for the engine to compute. That is automatic, engine-backed tax in both directions. 2 9 10
The Service-Business Owner
VAT is set at charge level with a customer-default fallback, and US sales tax runs through a named engine, Anrok, with address rules and error webhooks documented — but the configuration is manual, not location-driven. For selling across the EU I found no public information on reverse charge for business customers, VAT-ID validation via VIES, OSS reporting, or automatic rates by customer country. 2 9 10
The Tax Adviser
Tax is seller-configured: rates defined per recurring charge, otherwise the customer's default rate lands on the whole invoice, and a named engine — Anrok — computes tax from the customer address, though notably state and region are not sent in that computation. A tax-ID field exists on customers and tax treatment shows up in the reporting. We found no public information on reverse charge for business customers, VIES validation, OSS reporting data, or VAT rates per country maintained by the vendor — the cross-border VAT core is undocumented. 2 9 10 13
The Skeptic
Tax on invoices is a configured rate — per charge on the plan, or a customer default applied to the whole invoice — with US sales tax computed through the named engine Anrok, whose address requirements and failure modes are documented in unusual detail. For the EU side we found no public information on automatic VAT per country, reverse charge, VIES validation of VAT IDs or One-Stop-Shop reporting data, and no statement of who carries tax liability. 2 9 10
Payment collection, dunning & portability
Show reasoningHide reasoning
How this is scored
How invoices turn into money: which payment providers and methods the product works with, SEPA direct-debit mandates, automatic retries and dunning sequences, payment reconciliation, collections handover — and whether the seller can move subscriptions and stored payment details to another provider.
0 — No collection; invoices are sent and payment is chased by hand.
3 — One built-in payment provider with card payments, and failed payments reported but not retried or chased.
5 — Several payment providers or methods including SEPA direct debit with mandates, automatic retries of failed payments, dunning emails with configurable steps, and payments matched to invoices.
8 — Gateway-agnostic collection across named providers, smart retries and card updaters, dunning with escalation and service suspension rules, bank-transfer reconciliation, a handover to a collection agency, and recovery reported.
10 — Collection is portable and measurable: subscriptions and payment tokens importable and exportable with a documented migration path, routing across providers per country or method, recovered revenue reported per dunning step, and no lock-in to the vendor's own payment service stated in the terms.
The SaaS Founder
This is the strongest area for my priorities: dunning campaigns with per-currency overdue-balance triggers, configurable attempts and delays, billing-entity or per-customer scope, grouped payment requests across all overdue invoices per currency, and an agent that reads twelve months of payment history, waits out a customer's usual payment lag, chases the net after a partial payment, sends a card-fix link on failure and escalates to a human. Recovery is measurable — recovered revenue per currency, recovery-time buckets and per-invoice attempt summaries — and collection runs through connected providers, with Stripe named in the fallback behavior and GoCardless in the failed-payment exception. We found no public information on a documented migration path for subscriptions and payment tokens, or on handover to a collection agency. 11 12 2
The Finance Lead
Dunning is campaign-driven with configurable attempt counts and delays, applies billing-entity-wide or per customer, and I can pull a key account out entirely with an exclusion switch — exactly the control I want before a chase sequence reaches a strategic logo. Recovery is genuinely measured: chased invoices paid versus unpaid, recovered revenue per currency, recovery-time buckets and a per-invoice attempt summary, and a Dunning Agent escalates large or unanswered accounts to a person. I found no public information on SEPA mandate management, bank-transfer reconciliation, a collection-agency handover, or a documented migration path for subscriptions and payment tokens. 11 12
The Billing Engineer
Dunning is genuinely engineered: multiple campaigns scoped to a billing entity or an individual customer, thresholds per currency, configurable attempt counts and delays, grouped payment requests per currency and entity, and a Dunning Agent that reads twelve months of payment history, chases the net after a partial payment, sends a card-fix link and escalates large accounts to a person. Stripe and GoCardless are the named providers, failed payments fall back to an emailed payment link, and recovery is reported in outcome, per-currency and recovery-time dashboards. I found no public information on card updaters, collection-agency handover, bank-transfer reconciliation, or a documented path to move subscriptions and payment tokens to another provider — the migration story I get paged about is the piece the captured pages do not cover. 2 11 12
The Service-Business Owner
Dunning is genuinely built out: multiple campaigns with thresholds, delays and attempt counts per billing entity or customer, automatic payment attempts via a connected PSP, an agent that reads twelve months of payment history, and recovered revenue reported per currency with recovery-time buckets. GoCardless and Stripe appear by name, but SEPA mandate management is not described, and a migration path for subscriptions or payment tokens to another provider is not documented. 2 11 12
The Tax Adviser
Dunning is deep and measurable: campaigns with configurable delays, attempt counts and per-currency overdue triggers, scoped per billing entity or individual customer, an agent that reads twelve months of payment history before chasing and escalates large or unanswered accounts to a person, and recovery reported per attempt and by time bucket after the first chase. Collection runs through named providers Stripe and GoCardless with automatic payment intents, grouped payment requests per currency, failed-payment emails and invoices marked succeeded on payment. We found no public information on SEPA direct-debit mandates, card updaters, a collection-agency handover, or a documented migration path for subscriptions and payment tokens. 2 11 12
The Skeptic
Dunning is genuinely built out: configurable campaigns with overdue balances, currencies, delays and attempt counts, a Dunning Agent that reads twelve months of payment history and adapts per account, grouped payment requests per currency, Stripe and GoCardless named as providers, and recovery reported per invoice with recovery-time buckets. We found no public information on card updaters, bank-transfer reconciliation, service suspension rules, collection-agency handover, or any documented path to move subscriptions and stored payment details to another provider. 11 12
Revenue reporting & accounting handoff
Show reasoningHide reasoning
How this is scored
What finance gets out of billing: MRR, ARR, churn and cohort reporting, revenue recognition and deferred revenue, the export or sync to the accounting system and to DATEV, CRM and data-warehouse integrations, an API and webhooks, and a complete export of customer and subscription data.
0 — No reporting and no export beyond downloading individual invoices.
3 — A revenue overview and a CSV export of invoices, with no subscription metrics and no accounting integration.
5 — Subscription metrics (MRR, churn) on a dashboard, an export or sync to at least one named accounting tool, and a documented API with webhooks.
8 — Revenue recognition with deferred revenue schedules, a DATEV export or booking-ready journal for the ledger, native CRM and accounting integrations named, MRR movements explainable per customer, and a full data export documented.
10 — Billing is the system of record for revenue: recognition to IFRS 15 / ASC 606 stated, month-end close supported with reconciled reports, data-warehouse sync, audit trail of every financial event, and a complete export of customers, subscriptions and invoices that a successor system can import.
The SaaS Founder
MRR reporting is deep and honest: movements split into new, expansion, contraction and churn, upgrades linked so only the difference is counted, breakdowns by customer, plan, currency and country, and the exclusions stated openly rather than hidden. Revenue recognition offers recognized revenue, deferred revenue, statements and double-entry journal details for posting to the general ledger — marked private beta — while CRM, CPQ and accounting integrations are listed as an add-on without the tools named. We found no public information on a DATEV export or a documented complete export of customers and subscriptions a successor system could import. 13 14 2
The Finance Lead
MRR is defined precisely — subscription fee only, excluding tax, converted per interval — with movements broken into new, expansion, contraction and churn per customer, and the revenue recognition section, currently in private beta, exports recognized and deferred revenue plus journal entry details with double-entry lines for posting to the general ledger, traceable back to the billing event. There is an API, webhooks and a data pipeline integration, and CRM, CPQ and accounting integrations are offered as an add-on. I found no public information on a DATEV export, a named accounting tool, or a complete export of customer and subscription data that a successor system could import. 1 2 9 13 14
The Billing Engineer
The MRR dashboard decomposes run rate into starting, change and ending values with new, expansion, contraction and churn movements, filterable down to a single customer, and upgrades are linked so only the difference counts. Revenue recognition exists in private beta with recognized and deferred revenue and journal-entry details described as the line-level source of truth for posting to the general ledger, with every report exportable in multiple formats. CRM, CPQ and accounting integrations are on-demand add-ons without named tools, and I found no public information on a DATEV export, an IFRS 15 or ASC 606 statement, or a complete export of customers and subscriptions a successor system could import. 2 13 14
The Service-Business Owner
MRR with new, expansion, contraction and churn movements, breakable down to the individual customer, plus a revenue-recognition export with recognized revenue, deferred revenue and double-entry journal lines for posting to a ledger — that is close to what my tax adviser needs. But recognition is in private beta, accounting and CRM integrations are an unnamed add-on on demand, and DATEV is not named anywhere in the captured pages. 2 13 14
The Tax Adviser
MRR is unusually well documented — movements split into new, expansion, contraction and churn, upgrades linked so only the difference counts, filters down to individual customer and tax ID — and revenue recognition exports recognized revenue, deferred revenue and line-level double-entry journal details for posting to the general ledger, though that module is flagged private beta. An audit trail, an API with webhooks, and accounting, CRM and CPQ integrations as add-ons round it out. We found no public information on a DATEV export, an IFRS 15 or ASC 606 statement, or a complete documented export a successor system could import. 1 2 13 14
The Skeptic
MRR is explained down to the movement — new, expansion, contraction, churn — with upgrades linked so only the difference counts, and revenue recognition exports deferred revenue, statements and double-entry journal lines for the ledger; but revenue recognition is marked Private beta. Accounting, CRM and CPQ integrations exist as an add-on on request with no tool named. We found no public information on a DATEV export, recognition to IFRS 15 / ASC 606, or a complete export of customers, subscriptions and invoices a successor system could import. 1 2 13 14
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where customer, invoice and payment data are hosted, and who the subprocessors are (hosting, payment providers, tax engines, email delivery). Independently sourced by the sovereignty pipeline; billing data is personal and financial at once, so the whole chain counts, not only the database.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.
5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (tax engine, email, analytics, support) run through non-EU providers without a stated safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor, data export and deletion documented, and certifications published with their scope rather than implied.
The SaaS Founder
A privacy policy and processor terms exist, with an EU representative in Ireland, a DPO contact, listed transfer safeguards, SOC 2 Type II stated, and self-hosted or VPC deployment as an option — but the contracting entity is Get Lago Corp., a Delaware corporation, and hosting location, ownership and subprocessors are unknown to me. For a billing system holding my customers' personal and financial data at once, I would need that chain named before signing; on-prem deployment is the workaround the captured pages actually evidence. 3 4 2 1
The Finance Lead
The contracting entity is Get Lago Corp., a Delaware corporation, and the cloud terms carry US export control and binding individual arbitration; hosting location for the cloud service is not stated and I found no published subprocessor list, though on-premises and VPC deployment are available. An EU representative in Ireland, a DPO contact, standard contractual clauses and SOC 2 Type II are documented, which lifts this above the floor but leaves the chain far from sovereign end to end. 2 3 4
The Billing Engineer
The contracting entity named in the cloud terms is Get Lago Corp., a Delaware corporation subject to US export-control terms, and I found no public information on where Lago Cloud hosts data or which subprocessors run hosting, payments or email — the chain that carries invoice and payment data is not visible on the captured pages. GDPR posture is present in the privacy policy — Belgian and French data protection law, an EU representative in Ireland, a named DPO contact, transfer safeguards — and SOC 2 Type II is stated, and deploying on-prem or in a VPC lets a customer keep data inside Europe; for the hosted offering itself, though, the proven facts stop at the US entity. 2 3 4
The Service-Business Owner
The contracting entity is a Delaware corporation whose terms carry US export-control language, the cloud hosting location is not stated, and subprocessors are unnamed; an EU representative in Ireland, transfer safeguards and SOC 2 Type II are stated, and self-hosting on-prem or in a VPC is offered. I could keep billing data in Europe by running it myself, but the cloud chain itself is not evidenced as European, which for my German customer base is the decisive fact. 2 3 4
The Tax Adviser
The contracting entity is Get Lago Corp., a Delaware corporation, and we found no public information on where Lago Cloud is hosted or which subprocessors sit in the chain — only that processors are bound by instruction and authorization clauses in the privacy policy. The European posture is real but thin: an EU representative in Ireland, a DPO contact, SOC 2 Type II, and disputes routed to binding US arbitration. The one genuine escape is deployment: open source on-prem or in a VPC, which is the only evidenced way a customer keeps billing data on European soil. 2 3 4
The Skeptic
The contracting entity is Get Lago Corp., a Delaware corporation, with binding individual arbitration, a class action waiver and US export control in the cloud terms; an EU representative in Ireland and a DPO mailbox do not change who you sign with. We found no public information on where Lago Cloud hosts customer data or who the subprocessors are — the privacy policy commits to authorizing subprocessors but names none — and none on a published data processing agreement or ISO 27001. Self-hosting, VPC and on-prem deployment are genuine mitigations and SOC 2 Type II is stated, so a buyer who runs it themselves can keep the chain short. 2 3 4
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: platform fee, percentage of billed revenue or per-invoice fees, which modules (revenue recognition, e-invoicing, tax, extra gateways) cost extra, overage above a revenue band, setup and minimum term, and the merchant-of-record fee where it applies.
0 — No public prices at all; every customer is a sales call.
3 — A starting price or a free tier exists, but how cost scales with billed revenue, invoices or modules is unclear.
5 — Tiers are public with their main inclusions and revenue bands, but at least one commonly needed piece (e-invoicing, revenue recognition, extra gateways, overage) is unpriced or "on request".
8 — Every tier priced publicly with its scaling rule (revenue percentage, per invoice, per subscriber), overage and add-ons listed, minimum term and VAT treatment stated.
10 — Complete price computability: annual cost derivable for a given billed revenue, invoice volume and module set, with every add-on, setup, support and payment or merchant-of-record fee and the cancellation and data-return terms published.
The SaaS Founder
Tier names (Starter, Pro, Business, Enterprise) and a time-limited trial are public, the terms state fees exclude taxes, and past-due amounts carry interest of one and a half percent per month — but we found no price figures for any tier in the captured pages, and premium items such as credit notes, tax integrations and CRM/CPQ/accounting integrations are marked available on request only. I cannot compute my annual cost from these pages. 2 4 11
The Finance Lead
The tiers are named — Starter, Pro, Business, Enterprise — but the plan and its price live in an order form, and I found no public price figures on the captured pricing page; a time-limited free trial of the service exists. The pieces I would actually need — tax integrations, quotes and order forms, credit notes, accounting integrations, custom branding, billing entities beyond the cap — are marked premium or available on request, so I cannot compute an annual cost from public pages. 2 4 8 11
The Billing Engineer
Four named plans with their inclusions are public, the terms state fees are exclusive of taxes, and a time-limited trial may be offered — but no price figures for any tier appear on the captured pages, while several pieces a buyer needs (tax integrations, quotes and order forms, CRM and accounting integrations, professional services) are marked premium or available on request only, and billing entities are included up to an unspecified capped number. Final pricing runs through an Order Form, so I cannot compute an annual cost from public information. 2 4 11
The Service-Business Owner
Four plans are named, a time-limited trial exists, and the terms state fees are exclusive of taxes, with the customer paying applicable taxes. But no price figure appears on the captured pages, and tax integrations, dunning premium features, quotes, billing entities beyond the cap and professional services are all on request or on demand — I cannot compute an annual cost for my two hundred contracts. 2 4 11
The Tax Adviser
The tiers are named — Starter, Pro, Business, Enterprise — but no price figures, revenue bands or scaling rules appear in the pages we captured, with the open-source option as the visible free entry point. A string of commonly needed pieces is explicitly "upon request" or "on demand": the premium add-on, quotes, tax integrations, accounting and CRM connectors, custom branding and professional services, so a buyer cannot compute an annual cost from public pages. The terms do state that fees are exclusive of taxes, with auto-renewal and thirty days' notice not to renew. 2 4 11
The Skeptic
The captured pages name four plans — Starter, Pro, Business, Enterprise — with feature inclusions but no price figure anywhere: no starting price, no scaling rule, no revenue bands, and fees stated exclusive of taxes. The features that touch money sit behind contact-us gates — dunning and tax integrations as premium add-ons upon request, quotes and order forms on request, credit notes premium, billing entities included up to a capped number with no figure given for the cap. The only numbers the terms publish are late-payment interest of one and a half percent (1.5%) per month and a $100.00 trial liability cap, so a buyer cannot compute an annual cost from public pages. 2 4 8 11
European sovereignty — proven facts
1 of 4 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Incorporated in US ⚠ unverified | 0/3 pts | 4 Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined | — | uncited Report an error |
| Subprocessors | Not determined | — | uncited Report an error |
Questions about Lago
Is Lago European?
No. whats-best.ai classifies Lago as Rest of world. Its vendor, Get Lago Corp., is incorporated in United States, per the vendor’s page captured 26 Oct 2026.
Where does Lago store data?
Not stated on the vendor’s pages as of 26 Oct 2026.
Does Lago have a free plan?
Not stated on the vendor’s pages as of 26 Oct 2026.
What are the best alternatives to Lago?
As of 28 Oct 2026, the panel rates Chargebee (3.5/5), Younium (3.5/5) and Stripe Billing (3.5/5) highest among the other 12 Billing & Invoicing products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Younium (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Lago alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 26 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Legal entity. Despite an EU-facing posture (privacy policy citing Belgian and French data protection law and an appointed EU representative in Ireland), the contracting legal entity is a Delaware, USA corporation.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 7 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
Sources (14)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage getlago.com Checked 26 Oct 2026 Details →
- 2 Pricing page getlago.com Checked 26 Oct 2026 Details →
- 3 Privacy policy getlago.com Checked 26 Oct 2026 Details →
- 4 Terms of service getlago.com Checked 26 Oct 2026 Details →
- 5 Plans, pricing models & subscription lifecycle — found from sitemap knowledge.getlago.com Checked 26 Oct 2026 Details →
- 6 Plans, pricing models & subscription lifecycle — found from sitemap knowledge.getlago.com Checked 26 Oct 2026 Details →
- 7 Invoices & e-invoicing compliance — found from sitemap knowledge.getlago.com Checked 26 Oct 2026 Details →
- 8 Invoices & e-invoicing compliance — found from sitemap knowledge.getlago.com Checked 26 Oct 2026 Details →
- 9 Cross-border VAT & tax handling — found from sitemap knowledge.getlago.com Checked 26 Oct 2026 Details →
- 10 Cross-border VAT & tax handling — found from sitemap knowledge.getlago.com Checked 26 Oct 2026 Details →
- 11 Payment collection, dunning & portability — found from sitemap getlago.com Checked 26 Oct 2026 Details →
- 12 Payment collection, dunning & portability — found from sitemap getlago.com Checked 26 Oct 2026 Details →
- 13 Revenue reporting & accounting handoff — found from sitemap getlago.com Checked 26 Oct 2026 Details →
- 14 Revenue reporting & accounting handoff — found from sitemap getlago.com Checked 26 Oct 2026 Details →