Pricing

A monthly floor, and metered sync operations charged against it. Generated from the pricing contract, so every number here is the one the invoice uses.

Pricing version: 2026-08-28.

You pay a monthly floor, or your metered usage, whichever is greater. Usage is charged against the floor rather than added to it, so an organization on Scale that sends nothing pays the floor, and one that sends four times the floor pays four times the floor. There is no separate subscription line.

Tiers

	Monthly	Operations included	Per day	Connections	Audit storage included
Free	$0	100K	10K	25	1 GiB
Scale	$250	50M	No limit	5,000	50 GiB
Enterprise	Custom pricing	Committed	No limit	Committed	Committed

Free. Free for early-stage teams building against the real engine.

Scale. Built for scaling teams with production traffic.

Enterprise. Custom infrastructure, security, and support for critical workloads.

On Free, 100K operations are included. With billing enabled, usage above that allowance continues at the published rate; without billing, requests stop at the allowance. On every plan with a paid floor, the included figure is what the floor already covers.

For organizations without billing enabled, the daily figure on Free is a burst guard rather than an allowance. It spreads the free month over at least 10 days. Enabling billing unlocks pay-as-you-go usage above the free allowance.

Included	Free	Scale	Enterprise
Single sign-on	No	No	Yes
Audit log export	No	Yes	Yes
Customer-managed encryption keys	No	No	Yes
Private networking	No	No	Yes
Custom limits	No	No	Yes

What counts as an operation

An operation is every time someone does something: changes something, reads something, or takes ownership of something. One number covers all three.

Meter	Counts
writes	One every time someone changes something. Adding, editing, and removing all count the same, and changing 500 things is 500 operations however they are sent.
model reads	One every time someone reads something the engine answers. Reads a client already has locally never reach us and never count.
claim creates	One every time someone takes ownership of a row so others wait their turn. Holding it and releasing it are free.

A write counts the same whether it arrived over HTTP or over the WebSocket. The transport is not part of the price.

Two rules decide whether a request is counted at all:

Only successful requests count. A rejected or failed request is never metered.
A retry with the same Idempotency-Key counts once. The key the SDK puts on a write is the same key the meter deduplicates on.

Rate card

Scale uses one flat operation rate. The rate does not change as usage grows.

Monthly operations	Per million
All operations	$5.00

What a month costs

Monthly operations	Free	Scale
100K	$0	$250
1M	$4.50	$250
50M	$249.50	$250
500M	$2,499.50	$2,500
1B	$4,999.50	$5,000

Enterprise uses custom pricing with committed volume, negotiated limits, and an uptime guarantee.

Audit storage and connections

Free includes 1 GiB and Scale includes 50 GiB of audit-log storage. With billing enabled, both charge $1 per additional GiB-month. Enterprise storage is contract-priced. Concurrent connections remain a cap, not a meter.

Watching usage

Every metered response carries its own accounting, so you can see the position without opening a dashboard.

X-Usage-Limit: 50000000
X-Usage-Used: 12480311
X-Usage-Remaining: 37519689
X-Usage-Reset: 2026-08-01T00:00:00.000Z

Ablo emails the organization at 80 percent of a limit and again when it is reached. Past the limit the engine returns quota_exceeded, and past the connection cap connection_limit_exceeded. Both are retryable, once the period rolls over, the limit is raised, or other connections drain.

Metering follows successful product API operations regardless of transport. Short-lived browser and agent credentials do not create a separate free allowance.