LivePools for a company

Everything below already exists and is in the product — this page is a list of what a procurement review asks for and where each of them is, not a promise about a roadmap.

Your application, on your own domain

A key carries a browser-origin allowlist, so a React app on your domain can read a pool directly with no server of yours in the middle. A key with no origins listed cannot be used from any browser at all, which is what makes one found in a JavaScript bundle useless from a stranger's page.

Integration without holding a socket open

A pool POSTs every reading to a URL you own, signed with an HMAC over the exact bytes and the timestamp, so your receiver can prove it came from us. That is how a serverless function or a backend behind a load balancer integrates — neither can hold a WebSocket.

Get your data out

A streamed export in NDJSON or CSV over any window, in one request, without holding a month of readings in anybody's memory. There is no export queue and no waiting for an email.

Rotate a key without downtime

Rotation MINTS the successor first and leaves both working until you revoke the old one. Revoke-then-mint leaves a window with no working credential, and that window is as long as it takes a person to redeploy — which is not seconds.

An audit log

Key mints and revocations, origin changes, visibility flips, webhook changes and exports, with who and from where. Acts of administration, never the readings themselves.

Rate and quota in headers

X-RateLimit-* and X-LivePools-Quota-* on every answer, Retry-After on a 429, and an Idempotency-Key on ingest so a retry after a lost response republishes nothing.

Or run it yourself

Where readings are not allowed to leave a building, the local server is the same engine on your own hardware with no limits and nothing phoned home.

Questions

How do we buy it?

Enterprise is granted, not checked out. Talk to us — the size of the conversation is the reason there is no button.

Is there an SLA?

Contractual, agreed per customer. Nothing on this page is an SLA on its own.