Lath provisions a whole product backend — domains, hosting, Postgres, auth, payments, email, analytics and error monitoring — through one API, one account and one bill. The services underneath are commodities. The product is the layer between them.
Ship anything real and you end up with a customer whose subscription lives in one system, whose usage lives in another, and whose access depends on which of them last succeeded. Every team writes the same reconciliation code, and every team gets it slightly wrong in a way that shows up as a support ticket from someone who paid and cannot log in.
Lath owns one object — the entitlement — and answers one question: what may this person do right now. Plan, grant, override and cap resolve in a fixed order and produce a single answer, with its working visible. It does not matter which store took the money.
The whole surface is an API, an MCP server and a CLI, derived from one registry rather than written three times. That is not a bolt-on: it is why the safety model is reversibility — soft deletes, an undo log and spending caps — instead of approval gates. An agent that has to stop and ask permission is not doing the work.
Early. The entitlement engine, the operations layer and the API are built and tested; several of the nine services are specified and not yet provisioned, and the landing page marks which. Production email access is under review, and nothing is generally available.
We would rather say that here than have you discover it after signing up. If you want to be told when it opens, mail support@trylath.com.