Pricing

How the meter works

The pricing model is settled. The numbers are not, and we would rather tell you that than publish a rate we have to walk back.

No rates published yet — on purpose

We have estimates for what each operation costs us. Estimates are not measurements, and a free tier priced off a guess is how a service quietly loses money on every request until it has to reprice. Rates and free-tier limits publish once they are benchmarked against a real corpus. Until then this page describes the shape of the bill, not its size.

What the bill will be made of

Reserved before the work, not after

Credits are held atomically when a job is accepted and settled when it finishes. A job that would exceed your balance is refused up front rather than discovered in an invoice.

Priced per operation, not per seat

A thumbnail and a hundred-page OCR run cost different amounts because they consume different amounts. Charging one rate for both means somebody is subsidising somebody else.

A spend cap that actually stops

Set a monthly ceiling and processing halts at it. A cap that only sends an email is a notification, not a control.

Storage and delivery are separate lines

Processing, storage and egress are billed as what they are. Bundling them hides which one is growing.

You can always see the price first

Every operation returns a credit estimate before you commit to it, and every completed job records what it actually cost. If the two diverge, that is our problem to explain, and the record exists so you can hold us to it.