Lago logoReqKey vs Lago · checked September 2026

A Lago alternativethat enforces inside the request.

Lago turns events into invoices, wallets, and alerts. ReqKey deducts and blocks in the request itself — and issues the keys and limits Lago doesn’t.

Start building freeSee ReqKey pricing
  • A source for every claim
  • Where Lago wins, too
  • Free for 5M requests a month

The short answer

Lago is open-source usage-based billing: billable metrics, plans, wallets, and invoices. It doesn’t issue keys or rate-limit. ReqKey enforces credits synchronously per request, with nothing to host.

Lago is an open-source usage billing. ReqKey is API keys, credits, rate limits, and request analytics for the API you sell.

ReqKey, in one line

Free for 5M requests a month. $25 for 10M. No per-seat fees.

See every tier

ReqKey and Lago, line by line.

A filled mark shows who is stronger on that line; a dash means they’re comparable. Their wins are marked too.

  • How it runsReqKeySDK middleware inside your API — no proxy, no DNS changeLagoSend events from your app; self-hosted or Lago Cloud
  • API keys for your customersReqKeyYes — prefixed and hashed, one customer can hold many keysLagoNo
  • Credits and quotasReqKeyA balance per customer, any cost per call, refills every hour, day, week, or month, optional overageLagoWallets and entitlements in Premium; acts on alerts
  • Rate limitsReqKeyPer customer, set on the plan, windows from 1 second to 24 hours, 429 with Retry-AfterLagoNo
  • Request analyticsReqKeyEvery request — endpoint, status, latency, customer — 30 days on Pro, plus an Analytics APILagoBilling analytics
  • Free tierReqKey5M requests a month, 1,000 keysLagoOpen source (AGPLv3), self-hosted
  • First paid tierReqKey$25/mo for 10M requests and 100,000 keys, volume tiers to 1BLagoPremium not publicly priced
  • Takes paymentReqKeyNo — ReqKey meters and enforces; you take payment with your own providerLagoYes — invoices and billing logic

Lago details from their own pricing pages and docs, checked September 2026. Sources below.

Why teams pick ReqKey over Lago.

1

Keys, limits, and logs included

Lago is billing only; ReqKey adds the enforcement layer around each request.

2

Synchronous enforcement

ReqKey deducts and blocks inside the request. With Lago you send events and act on alerts.

3

Transparent pricing

ReqKey’s tiers are public; Lago Premium requires a quote.

4

Nothing to host

Lago’s free option means running AGPL software yourself.

When Lago is the better pick.

We’d rather you pick the right tool than switch twice.

  • You need self-hostable invoicing and billing logic.
  • You’re replacing Stripe Billing and want open source.

Moving from Lago in three steps.

  1. 1

    Keep your billing provider

    ReqKey doesn’t take payment. Keep charging customers the way you do today.

  2. 2

    Mirror plans as credits

    Give each plan a credit allowance, refill interval, and rate limit in ReqKey.

  3. 3

    Recharge on payment

    When a payment succeeds, recharge the customer’s credits or move them to a new plan with one API call.

Framework guides How ReqKey works

ReqKey vs Lago: common questions.

Something else? Ask the team or read the docs.

  • Yes — Lago for invoices, ReqKey for keys, credits, and limits in the request.

  • No. ReqKey meters and enforces; invoicing stays with your billing tool.

  • Every validated request is logged per customer, readable from the Analytics API.

Sources

Checked on Lago’s own pages in September 2026. Prices change — if something here is out of date, tell us and we’ll fix it.

Other comparisons.

Switching from Lago?It takes an afternoon.

Free for your first 5 million requests every month. No card, no gateway, no rewrite.

Start building freeRead the docs