nozle
    nozle

    Nozle — the billing platform AI companies actually need

    Know what every customer actually costs you.

    Subscriptions, metering, entitlements, dunning — plus true unit cost per customer across your AI and infra stack. One SDK, no hard-coded billing logic. Stripe is just the rail underneath.

    app.ts
    typescript
    1import { Nozle } from '@nozle-js/node';
    2
    3const nozle = new Nozle({
    4 apiKey: process.env.NOZLE_SECRET_KEY!,
    5});
    6
    7// 1. Subscribe a customer to a plan
    8await nozle.subscribe('customer_123', 'pro_monthly');
    9
    10// 2. Meter what they use (AI, infra, anything)
    11await nozle.track('customer_123', 'llm_tokens', {
    12 model: 'gpt-4o', tokens: 4_420,
    13});
    14
    15// 3. Invoice + true unit cost — handled.
    16// → nozle.margin.byCustomer() returns revenue, cost & margin
    ─── Price any cost in your stack ───

    Track what you spend on the tools you already pay, build & ship with.

    soonsoon
    + any provider via Cost Sheets·OpenAI + Anthropic auto-captured·Bring your own provider
    Never hard-code your billing logic

    One engine. Three jobs. No glue.

    Pricing as configuration — plans, entitlements and dunning declared as data, not buried in if-statements. Change a tier without shipping code. Run an experiment without a migration.

    LAYER 01

    Your product

    Wherever a user triggers a billable action

    chatagent runimage gensummariseembed
    LAYER 02 · nozle

    One engine. Three paths. One ledger.

    I
    hot path

    Every event, in real time.

    Meter, gate, and bill from one stream — streaming, not nightly batch.

    meteringentitlementswallets
    II
    money path

    Pricing as configuration.

    Plans, proration, and dunning declared as data — change a tier without a deploy.

    subscriptionsinvoicesdunning
    III
    truth path

    Margin, not just revenue.

    The engine that bills the customer also knows what they cost — margin becomes a query.

    LLM costmargin intelwallets
    the ledger

    Every event lands in one shared record. Finance, product, and ops all read the same number.

    Subscriptions, usage, and cost write to the same timeline — append-only, so nothing is rewritten or lost. One source of truth for invoices, dashboards, and audits.

    append-only · signed · auditableledger.v1
    LAYER 03

    Pluggable payment rails

    The processor is plumbing — Stripe or Razorpay, assigned per customer

    StripeRazorpayAdyen (coming soon)Cashfree (coming soon)

    Revenue lies.Margin doesn't.

    Every customer has a true margin. Most billing tools never compute it — so you ship plans that look profitable and quietly aren't. Nozle attributes every line item back to the customer who triggered it.

    customercus_initech
    last 30 days
    True margin
    −157%
    ▼ 184pp below your median

    For every $1 they pay, you spend $2.57 serving them.

    In plain English

    Initech pays you $42. Serving them costs $108.

    You lose $66 every month they stay on the Pro plan — and the gap widens as they use more.

    Revenue
    $42.00
    True cost
    $108.00
    Net
    −$66.00
    What's eating it
    $108.00
    • Claude Sonnet 4.6$64.00
      3.2M tokens · chat + agents · anthropic59%
    • OpenAI embeddings$21.06
      8.1M tokens · re-indexed 4× · openai19%
    • Lambda inference$14.10
      9,400s · cold-start heavy · aws13%
    • Transactional email$8.84
      42k sends · digest loops · resend9%
    What-ifMove Initech to usage at $0.024 / 1k tok, or cap inference at 2M tok / mo.
    projected margin+34%·+$108 / mo
    Margin distributionevery customer · ranked

    Some customers print money. Others quietly bleed it.

    Every account ranked on a single axis — from the ones carrying your business to the ones you're paying to keep.

    ↑ profitableunderwater ↓
    • Healthy
      fat margin
    • Comfortable
      room to grow
    • Thin
      watch closely
    • Marginal
      barely paying
    • Underwater
      you pay them
    Sorted bytrue margin
    What we attributeany vendor · any unit

    Every line item on your bill, pinned to a customer.

    Tokens, queries, milliseconds, rows, GBs, sends, transactions, seats — if it meters, we attribute it.

    • LLM inferenceper token
    • Embeddingsper token
    • Vector & searchper query
    • Computeper ms · GB
    • Databaseper row · GB
    • Storage & CDNper GB
    • Observabilityper event
    • Commsper send
    • Paymentsper txn
    • Auth & identityper MAU
    Plug inCost Events API + SDK →

    Build on nozle. Swap rails underneath.

    The SDK, components, and engine you ship on stay constant. Stripe or Razorpay sits in the slot below — assigned per customer. Adyen and Mollie are coming soon.

    No vendor lock-inProvider per customer

    → Tap a rail to slot it in

    Yours · from nozleconstant
    SDK
    Node · Python · Go · React
    Components
    <Checkout/> · <FeatureGate/> · <BillingPortal/>
    Engine
    subscriptions · invoices · ledger
    Active rail · Stripe
    Theirs · pluggableswappable

    From npm i to first event in 60 minutes.

    Native SDKs for Node, Python and Go, plus React components for the surfaces your customers see. One engine, four SDKs.

    packages.nozle.dev
    install$npm install @nozle-js/node
    importimport { Nozle } from '@nozle-js/node'
    track.ts
    typescript
    1import { Nozle } from '@nozle-js/node';
    2
    3const nozle = new Nozle({
    4 apiKey: process.env.NOZLE_SECRET_KEY!,
    5});
    6
    7await nozle.track(
    8 'customer_123',
    9 'llm_tokens',
    10 { model: 'claude-sonnet-4', tokens: 4_420 },
    11 { transactionId: 'tx_unique' },
    12);
    Response200
    "tx_unique"
    → Cost is rated async within seconds — read it with nozle.margin.byCustomer().
    ✓ typed · ✓ idempotent · ✓ signed webhooksTyped end-to-end · server-side, sk_ keys only
    01DX

    Typed SDKs

    Typed clients for Node, Python, Go and React — one API surface.

    02DX

    Webhooks you can debug

    Signed with JWT or HMAC, with delivery logs and one-click retry in the dashboard.

    03DX

    Docs your AI can read

    Full API reference plus an MCP server, so your tools scaffold the integration.

    Pricing models · supported by the engine

    Whatever shape your pricing takes, we model it.

    Ten common strategies, ready out of the box. Mix, match, or switch — without rewriting your billing code.

    • 01

      Flat subscription

      One product, one price — predictable, blind to load.

      subs × price
    • 02

      Tiered subscription

      Three or four plans, each gating features and caps.

      Σ tier × price
    • 03

      Per-seat

      Charge per active human user.

      seats × price
    • 04

      Pure usage

      Pay-as-you-go — per request, token, or event.

      Σ units × rate
    • 05

      Tiered usage

      Per-unit rate steps down as volume crosses bands.

      band × rate
    • 06

      Prepaid credits

      Top-up wallets burned across any feature.

      balance −= cost
    • 07

      Base + usage

      Platform fee plus metered overage above an included pool.

      base + overage
    • 08

      Seats + usage

      Per-seat platform plus per-action consumption.

      seats + actions
    • 09

      Per-action (agentic)

      Bill per resolved task — agents, not seats.

      Σ actions × price
    • 10

      Outcome-based

      Bill on realised value: a take-rate on results.

      value × take-rate
    10 strategies · 1 enginenot nozle's pricing — capabilities
    + primitives
    trialscouponsgrandfatheringmulti-currencyminimum commitsoveragesprorationdunningwalletstrialscouponsgrandfatheringmulti-currencyminimum commitsoveragesprorationdunningwalletstrialscouponsgrandfatheringmulti-currencyminimum commitsoveragesprorationdunningwallets
    Two paths · one engine

    Wherever you are, nozle slots in.

    Whether you're shipping your first plan or replacing rented billing, the same engine carries you.

    01For AI startups

    Ship pricing in 60 minutes.

    Meter usage, model your plans and send your first invoice in one sitting.

    • Time to live60 min
    • Card requiredno
    • Free until$5k MRR
    ›nozle.track(customerId, 'llm_tokens', { tokens })
    02For scaling teams

    Outgrowing Stripe Billing? Good.

    Replace the rented stack with one engine for billing and margin.

    • Stripe migration< 1 day
    • ProcessorsStripe + Razorpay
    • Audit trail100%
    ›nozle.checkout(customerId, 'pro_monthly')

    From npm i to your first margin report in 0minFrom npm install to your first margin report — across 0SDKsNode · Python · Go · React with 0OpenAI + Anthropic auto-captured — add any other cost to Cost Sheets at your own rates LLM providers auto-captured.

    Stripe + Razorpay·OpenAI + Anthropic auto-capture·Any cost via Cost Sheets
    FAQ · 03

    Honest answers, no fluff.

    The questions founders, finance leads and engineers ask before they switch. Direct answers — no marketing hedge.

    Platform5 questions
    Anything that scales with usage: AI tokens (OpenAI, Anthropic, Mistral…), vector queries, database reads, object storage, compute seconds (Lambda, Modal, Replicate), and third-party APIs (Twilio, Resend). You wire each cost model in once; Nozle attributes every event to the customer that triggered it.
    Can't find it?

    20-min teardown of your current billing — get a real answer on whether Nozle fits.

    Talk to us →

    Stop guessing.
    Start knowing.

    Wire Nozle into your stack and see your first margin report in 60 minutes.

    Setup
    60 min
    Card required
    no
    Sales call
    no
    First invoice
    in 60 min