All spotlights

Product spotlight · October 2026

Store records at the edge with indexes, transactions and ledgers

Format 2 KV stores give edge functions strongly consistent reads, indexes, transactions and append-only ledgers, and you can test them on your own computer.

Updated KV stores For developers

What changed in October 2026

The October 2026 changelog has the full details.

  • Format 2 stores

    A format 2 store keeps its keys in an index. Reads are strongly consistent, and an edge function can list one collection without scanning the whole store. Format 2 is the default for new dashboard stores. Stores created through the API stay format 1 unless the request asks for format 2.

  • Indexes, unique constraints and counts

    An index lists a collection by up to three fields, in a sort order you choose. A unique index refuses a write that would give two keys the same value. A count index keeps a running count for each group. A store can have up to 20 indexes, with up to 5 on one collection.

  • Append-only ledgers

    A ledger is a collection for records that must stay as written. Nobody can change or delete an entry, and each entry records which writer added it.

  • Usage, cost and export

    A store's page shows its item count, size, estimated monthly cost, and daily reads and writes for the last 30 days. An Export tab downloads every item as compressed JSON Lines files, for stores of up to 1 GiB.

  • Permissions and roles

    KV stores and ledgers now have their own role permissions, separate from content permissions. Two new optional organisation roles are for records and privacy staff. Records Officer can read stores and ledgers. Privacy Officer can also reveal personal fields and complete erasure requests. Personal fields stay hidden until someone with permission reveals them, and an erasure makes one person's personal data unreadable while the ledger stays verifiable.

  • Tools

    The v2 KV API, the TypeScript, PHP, Python and Go SDKs, and Terraform now cover format 2 stores. Sites created from a template get their KV stores in format 2.

By the numbers

read in one getMany() call
100 keys
in one atomic() transaction
25 operations
to roll back a format 2 upgrade
14 days

Action needed

  • Use ttl instead of expiration or expiresIn in edge function writes, because writes that pass those options now fail.
  • Add a uuid to every entry in your functions manifest before you upgrade to Quant CLI 7 or move a workflow to deploy action v7.

Who it is for

  • Edge developers

    Format 2 lets you create a record only once, or update several keys together without overwriting another writer's change.

  • Compliance teams

    Ledgers are for records that must stay as written, such as audit trails, registers of AI use, and consent or approval logs.

  • Records and privacy staff

    Records Officers can read stores and ledgers. Privacy Officers can also reveal personal fields and complete erasure requests.

How it works

In a format 2 store, a key’s collection is the text before its last :.

key: customer:abc:world:w1
collection: customer:abc:world

In an edge function:

  • kvStore.getEntry() returns a value with its version and timestamps.
  • getMany() reads up to 100 keys in one call.
  • Writes can be conditional with ifAbsent or ifVersion, and deletes with ifVersion.
  • atomic() applies a transaction of up to 25 operations completely or not at all.
  • Failures throw a KVError with a code.

A unique index can allow one account for each email address, and getBy() looks up a record by that value. count() returns a group’s count in one call.

For ledgers, edge functions add entries with kvStore.append(). On the Ledgers tab, you can run an integrity check and keep the signed report.

The @quantcdn/edge-kv npm package gives you the edge kvStore API and a local store on your own computer, with no Quant project or API token. It needs Node.js 20 or later. Use it only for development and tests, not for real secrets or personal data.

Get started

  1. Create or upgrade a store

    Create one in the dashboard, or upgrade one from its page with a 14-day rollback.

  2. Declare indexes

    Use the Indexes tab, the API, or quant/meta.json with quant kv-indexes (CLI v7.1).

  3. Test locally

    Use @quantcdn/edge-kv, or quant serve with quant kv --local (CLI v7.1).

  4. Declare ledgers

    Use the store's Ledgers tab. Read KV Ledgers.

  5. Manage stores as code

    Use Terraform quant_kv_store with format, quant_kv_index and quant_kv_ledger.

Related: Explore Edge functions · Documentation · October 2026 changelog

Ready to try it on Quant?

Use KV stores on your own project, or read the docs first.