Lath bills for the infrastructure you run, per unit, and the units are ones a provider sells by name. What that costs for a given workload is below.
Pricing is being replaced. Usage-based billing with a spending cap supersedes what this page described, and the rates are not set yet. What follows is the shape of the bill — the units, the worked examples, and what is not metered at all; it does not publish a price, and it will say so until one exists.
Requests 3,000,000 requests $3.00
CPU time 24,000 CPU-seconds $1.60
Database 1 project-month $2.92
DB storage 12 GB-months $4.00
Email 27,000 messages $14.40
───────────
Invoiced $25.92 USDEvery figure on this page is in United States dollars (USD). USD is the currency Lath invoices in, the currency the fee ladder below is denominated in, and the currency payouts settle in.
Most units are ones a provider sells by name: a request, a CPU-second, a GB-month, a message. That is what makes a rate checkable rather than merely stated — those figures meter something somebody else also sells, so the comparison is available to you rather than asserted by us.
The database line is different, and it is the one worth reading twice. A database runs on a cluster shared with other projects, and that cluster costs the same whether it is busy or idle. So the database is billed as a flat monthly share of it rather than by measured consumption — there is no per-project reading of a shared cluster to bill from, and inventing one would mean charging you for a number nobody measured.
Two consequences follow, and neither is hidden. A paused project still pays that share, because its database still occupies the cluster. And a heavy project pays the same share as a light one, which means heavy users are the better deal until the day a per-project meter exists.
The worked examples below understate a real bill. Databases also incur I/O, we know what a unit of it costs, and nobody has yet measured how much of it a real workload does — so it carries no quantity here rather than a guessed one. It is a measurement somebody can take, and this sentence goes when they do.
Two costs are deliberately absent from the table. Egress is not billed at all, because it is not billed to us. And the fixed monthly cost of the platform underneath is not metered to anyone, because it does not vary with what you run — charging it per project would bill the second project for the first one’s existence. Where those two land is part of what the replacement pricing has to decide.
One caution about the second figure. It describes a customer collecting twenty-five times the first one’s revenue while running five times the infrastructure, and that ratio is an assumption rather than a measurement — Lath has no customer at that scale to read it off yet. Usage grows more slowly than revenue for every hosted product we know of, so the direction is sound; how far is a judgement. The first real customer at that scale replaces it.
Infrastructure you are running is billed, because it is still running — a dormant project with a database costs what the database costs. There is no month in which a running resource is free.
Database 1 project-month $2.92
DB storage 5 GB-months $1.67
───────────
Invoiced $4.59 USDA spending limit blocks new billable resources — a new service, a new database, a deploy that increases spend. It never stops serving what is already running, and neither does a failed payment. Production keeps serving while we retry, contact you, and give you dates in advance.