Pricing

The demonstration is free and stays free. What a plan buys is more of it — more pools, more history, and more readings a month, which is the number that actually costs us anything.

Free, on any Leumas account

One pool, five sources, twenty-four hours of history, two keys, 100,000 readings a month at two a second. Every browser source, the LivePools Node, the socket, all three SDKs and alerts — none of that is gated. The demonstration has to work or nobody ever learns what this is.

Any Leumas membership

Ten pools, twenty-five sources each, a week of history, twenty keys, a million readings a month at ten a second, one outbound webhook, and the right to make a pool public.

Fusion, $9 a month

Fifty pools, a hundred sources each, thirty days of history, a hundred keys, ten million readings a month at fifty a second, five webhooks. For a workshop, a farm, a fleet of vehicles or a building.

Team, $29 a month

Five hundred pools, five hundred sources each, ninety days of history, a thousand keys, a hundred million readings a month at 250 a second, twenty-five webhooks. For a company building a product on top of it.

Enterprise

Unlimited pools, sources, keys and readings; a year of history; 4MB payloads. Granted rather than bought from a page, because at this size the conversation is a contract, a data-residency question and an SLA — and a checkout that skipped all three would be a promise nobody here made.

On your own machine: free, unlimited, no account

The local server runs the whole product on 127.0.0.1 with its own store, its own API and the same web page. There is no licence check and nothing to phone home to, because your computer costs us nothing to run. What the cloud is for is a pool your colleague, or your application in a datacentre, can also read.

Questions

What happens when I hit a limit?

A read never fails and nothing already in a pool is deleted. A publish answers 402 with the limit, how much is used and when the month resets. Going too FAST answers 429 with a Retry-After instead — a burst passes on its own and an upgrade would not fix it, so we do not ask you to buy one.

Why is it priced on readings and not on devices?

A device is not what costs anything. One sensor publishing a hundred times a second is a hundred times the work of a hundred sensors publishing once a minute, and a per-device price would charge the second one more.

Do rejected readings count?

Against your allowance, no — only accepted ones do. They are counted separately so the page can tell you how often you hit the ceiling, which is the number that says an upgrade is overdue.