Skip to content
Ledger by RODMEN/A
Menu

Insights

What a ledger must get right

Short articles for the people who sign off on the books. Each is drawn from the ledger’s own specification and audit record, and each says where its claims come from.

Articles

Newest first

  1. 2026-09-05

    Build or buy a ledger: the ten problems you inherit either way

    The data model is the easy part. The failure modes are the product.

  2. 2026-09-05

    Embedded ledgers for platforms: giving every client their own books

    One set of books with a client column is one missing filter away from disaster. A ledger per client is the shape that cannot leak.

  3. 2026-09-05

    Ledger versus metering: what a quota service cannot do

    If the units can be bought, refunded or disputed, they are property, and property belongs on a ledger.

  4. 2026-09-05

    Safe retries: how an idempotency key stops a payment happening twice

    Send the same request twice and you should get the same answer once. Getting that right under a crash is harder than it looks.

  5. 2026-09-05

    What “bank-grade” should mean: verified, not declared

    A claim is worth the evidence behind it and the auditor who tried to break it.

  6. 2026-09-05

    Why a ledger’s rules belong in the database, not the application

    Application code has many paths and many authors. A rule the database enforces holds for every path, including the one nobody remembered.

Free today. Access is provisioned personally by RODMENA.

Tell us what you keep books of and we will set up a tenant, mint your first key and walk you through the tour.