Your product needs nine backends.
Ship one.

Your whole backend, provisioned and run by an agent — not by you across a row of consoles.

One operations registry defines everything Lath can do, and the REST API, the MCP server and the CLI are all derived from it. One entitlement answers what a customer may do, whichever service took the money.

Start a projectRead the docs
Every customer, one page.

Identity, plan, effective access and live usage — resolved, not stitched together from four dashboards.

CustomerPlanAccessUsage
Verano Studiohello@verano.studioProActive1,219 left
Petal Groceryops@petalgrocery.comFreeActive7 left
Marchmont & Cobilling@marchmont.coTeamPast dueunlimited
Ostrom Roboticsplatform@ostrom.systemsEnterpriseActiveunmetered
Kestrel Freightapi@kestrelfreight.comTeamActive12,480 left
Entitlement

One customer,
one answer

Three stores can take the money. Plan, grant, override and cap resolve in a fixed order and produce a single answer — with its working visible.

Mobile storesubscriptionCard on filesubscriptionManual grantsupportEffective accessPro · 1,500 / monthone answer
Applied in this order, always
1PlanPro Monthly100 GB
2GrantTemporary · expires Sep 1+ 50 GB
3Overridenone set—
4Capno account ceiling—
Effective150 GB
Change any input and the answer recomputes. Nothing is cached that can go stale.
Provisioning

One command.
A whole backend.

$ lath init ridgeline --region eu-west
✓ domain ridgeline.io
✓ postgres ep-cool-sun-a1b2.eu-west
✓ auth google, github
✓ email mail.ridgeline.io · verified
✓ payments live + test
backend ready in 41s
Surface

Nine services.
One account.

Every one ships at launch; none is held back. Each is provisioned, billed and operated through the same API and the same dashboard: no separate signups, no separate invoices, no credentials pasted between providers.

Domains and DNSRegister, transfer, and manage records.provisioned
MailboxesReal inboxes on your own domain.provisioned
HostingIsolated compute per project, deployed on push.provisioned
PostgresProvisioned databases with branches and backups.provisioned
AuthenticationGoogle, Microsoft and GitHub, under your name.provisioned
PaymentsCheckout, subscriptions and payouts.provisioned
Transactional emailSending domains, templates and delivery.provisioned
AnalyticsEvents, funnels and revenue attribution.observed
Error monitoringExceptions, traces and alerts.observed
Which of these an agent can call today, operation by operation, is on the operations page — generated from the same registry the API and the MCP server serve.
Pricing

One percent of what you make.
Nothing before that.

Infrastructure is billed on top, at its published list price times 1.5. All in, that is 1.7% at $10,000 a month and 0.8% at $250,000. The share falls as you grow, and both ledgers are below.
At $10,000 USD collected in a month
Collectedacross 412 payments$10,000.00
Lath fee1%$100.00
Requests3,000,000 requests$1.35
CPU time24,000,000 CPU-ms$0.72
DB compute365 CU-hours$58.04
DB storage12 GB-months$6.30
Email27,000 messages$6.48
Invoiced$172.89 USD
You keep $9,827.11 — 98.3% of what you collected.
Above $100,000 USD in a month
First $100,000.001%$1,000.00
Next $150,000.000.5%$750.00
Fee on $250,000.00$1,750.00 USD
0.7% blended. The rate falls as you grow, not as you negotiate.
With no revenue collected
Collectedno payments yet$0.00
Lath fee1% of nothing$0.00
DB storage5 GB-months$2.63
Invoiced$2.63 USD
Every figure on this page is in United States dollars (USD), the currency Lath invoices and settles in. The pricing page shows which units each rate is billed in, why egress is not billed at all, and what the 1.5× does and does not cover.

Build the product.
Let the backend resolve itself.

Start a project
An email and a card. Nothing is charged until your agent asks for a resource.