Bill exactly what happened.
$ npm i @meridian/sdk50k events/mo free · no card required
Metering revenue for teams at
- 12.4B
- events metered daily
- 41ms
- p99 rating latency
- 99.99%
- ingest uptime, trailing 12mo
- $4.1B
- ARR invoiced through Meridian
01 · The platform
Metering is your revenue source of truth
Everything that happens between an event firing in production and a number your CFO signs off on.
02 · How it works
Event to invoice in three moves
Meridian sits between your product and your ledger. You describe what to count and what it costs — it does the rest, continuously.
Fire events from anywhere in your stack
- One SDK call per meter — batching, retries and back-pressure are handled for you.
- An idempotency key rides along with every event, so retries are free.
- SDKs for TypeScript, Python, Go, Rust — or raw HTTPS if you prefer.
import { Meridian } from "@meridian/sdk"
const meridian = new Meridian(process.env.MERIDIAN_KEY)
await meridian.track("tokens.generated", {
account: "acme-prod",
quantity: 1840,
idempotencyKey: request.id,
})03 · Pricing
Priced the way we think you should price
A real free tier, one production plan, and no percentage of your revenue. We meter events — it would be strange if we didn't charge by them.
Prices are fictional. So is the company.
04 · Customers
Billing teams that sleep at night
Quotes are as fictional as the companies — the failure modes they describe are very real.
05 · FAQ
Fair questions
The ones prospects actually ask on the first call.
06 · Get started
Stop estimating. Start metering.
Point an event at Meridian tonight and watch it become a rated line item before your coffee cools. The first 50k events a month are on us.
SOC 2 Type II · GDPR · usage data never trains anything