Edge platform for real-time apps
The backend that lives next to your users.
Built for teams like
The platform
One platform from first request to last byte.
Every part of your backend gets the same global footprint, so you stop stitching vendors together and get back to shipping.
-
Bring your framework
Deploy Node, Bun, Python or Go handlers with the tools and libraries you already use.
-
Pay per request
Usage pricing with no idle servers and no long-term contract to sign.
-
Streams by default
Responses, queries and events stream as they happen, with no extra setup.
-
Dedicated capacity
Reserve isolated compute for steady, high-volume workloads.
-
Global from day one
Code runs in the region closest to each request, automatically.
-
Private networking
Reach your own cloud over private links in every region we run.
Six primitives. One bill.
Start with one, add the rest when you need them. They share a network, a dashboard and an invoice.
Pick a workload. See what it runs on.

Runs on Functions, Realtime, Database and Queues. One deploy, one bill, no extra vendors.
Chat and messaging
Messages land in under 40 ms for both people, wherever they are.
- Runs on
- Functions, Realtime, Database, Queues
- Vendors
- One

Runs on Database, Realtime and Functions. No polling, no cache to warm.
Live dashboards
Stream rows from Postgres straight to the browser as they change.
- Runs on
- Database, Realtime, Functions
- Vendors
- One

Runs on Realtime, Functions and Storage, in the region closest to each player.
Multiplayer apps
Presence and shared state for any canvas, doc or game room.
- Runs on
- Realtime, Functions, Storage
- Vendors
- One
Start from something that already works.
Clone a template, push to main and it is live in every region. Change what you like after that.
Our network, end to end.
Three layers, and we own all of them.
A competitor can match a price. Matching the stack under it takes years.
→Find the region next door.
Every region runs the full platform. Requests go to the closest one and fail over on their own.
-
11 regions, from Ashburn to Vancouver.
-
9 regions, including two in the EU sovereign zone.
-
12 regions, Tokyo to Sydney.
-
6 regions, Sao Paulo to Johannesburg.
What you get, side by side.
Most teams run a cloud region and five services on top. Here is the same app on each setup.
Regions included
Where your code runs on day one.
- Lattice
- 38
- Single cloud region
- 1
- Build it yourself
- 0
| What you get | Lattice38 regions, one bill | Single cloud regionOne region plus add-ons | Build it yourselfYour team runs it all |
|---|---|---|---|
| Time to first deployFrom an empty folder to live traffic. | Lattice2 minutes | Single cloud region1 day | Build it yourself2 weeks |
| Database replicasRead copies close to every user. | LatticeBuilt in | Single cloud regionExtra service | Build it yourselfYou run it |
| Realtime socketsOpen connections to browsers and apps. | LatticeBuilt in | Single cloud regionThird party | Build it yourselfYou run it |
| Data going outWhat you pay when users download. | LatticeFree | Single cloud regionPer GB | Build it yourselfPer GB |
| Private networkingLinks into your own cloud. | LatticeEvery region | Single cloud regionSome regions | Build it yourselfYou build it |
Demo comparison for this template.
Built for agents and the people who write them.
Every product on this page is also an API. Point your coding agent at Lattice and it can deploy, query and roll back on its own.