Edge platform for real-time apps

The backend that lives next to your users.

Functions, a database, queues and storage on one network of 38 regions. Deploy once and every request is answered close to where it started.
The Lattice console showing requests by region, latency, request volume, error rate and a live log stream
The Lattice console: every request, region and deploy in one place.

Built for teams like

OpenAI Cisco IBM Microsoft Zillow
Building blocks

Six primitives. One bill.

Start with one, add the rest when you need them. They share a network, a dashboard and an invoice.

See all products →
Compute layer drawing

Edge Functions

Code runs in 38 regions and starts in under 10 ms.

View docs →
Data layer drawing

Global Database

Postgres-compatible reads from the nearest replica, writes kept consistent.

View docs →
Network layer drawing

Queues

Durable jobs and retries that survive deploys and region outages.

View docs →
A team chat message from mia: Deploy finished in all regions

Object Storage

S3-compatible buckets with no fees for data going out.

View docs →
World map of Lattice regions

Realtime

Push updates to millions of open sockets from one API call.

View docs →
Lattice console p50 latency card: 9 ms, down 3 ms from last week

Inference

Call open models from your functions, in region, by the token.

View docs →

Closer is faster, by a lot.

Median response times from twelve client cities, Lattice against the same app on a single cloud region.

Source: Lattice lab test, October 2026. Demo figures for this template.

API read
Lattice9 ms
One region84 ms
Database write
Lattice14 ms
One region120 ms
Cold start
Lattice6 ms
One region410 ms
Closer is faster, by a lot.
MeasureValueOne region
API read9 ms84 ms
Database write14 ms120 ms
Cold start6 ms410 ms

Pick a workload. See what it runs on.

The same blocks become very different products. Choose one to see the pieces it uses and the code that ties them together.
Functions, Realtime, Database and Queues tiles above a twelve line chat backend in code

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
Open the chat template →
Templates

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.

A team chat message from mia: Deploy finished in all regions
Compute

Chat backend

Rooms, history and push notifications in one deploy.

Open template →
World map of Lattice regions
Data

Live dashboard

Stream rows from Postgres straight to the browser.

Open template →
Lattice console p50 latency card: 9 ms, down 3 ms from last week
Realtime

Multiplayer cursors

Presence and shared state for any canvas or doc.

Open template →
Lattice requests metric: 218k per minute
AI

Support agent

Answer tickets with an in-region model and your docs.

Open template →

Our network, end to end.

38Regions on hardware we own
212Peering partners on our backbone
4.2BRequests answered every day
99.99%Uptime over the last 12 months (demo figures)

Three layers, and we own all of them.

A competitor can match a price. Matching the stack under it takes years.

How the platform fits together →
Three function rows: two routes and a nightly job
01Layer

Compute

Functions, actors and scheduled jobs on every region's own servers.

Explore compute →
A replica table with one primary region and three replicas
02Layer

Data

Database, queues and storage, kept right next to your code.

Explore data →
Nodes joined by orange lines in a mesh
03Layer

Network

Our own backbone, anycast routing and peering in 38 cities.

Explore network →

Find the region next door.

Every region runs the full platform. Requests go to the closest one and fail over on their own.

A gray dot map of the continents
  1. 11 regions, from Ashburn to Vancouver.
  2. 9 regions, including two in the EU sovereign zone.
  3. 12 regions, Tokyo to Sydney.
  4. 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
Program comparison
What you getLattice38 regions, one billSingle cloud regionOne region plus add-onsBuild it yourselfYour team runs it all
Time to first deployFrom an empty folder to live traffic.Single cloud region1 dayBuild it yourself2 weeks
Database replicasRead copies close to every user.Single cloud regionExtra serviceBuild it yourselfYou run it
Realtime socketsOpen connections to browsers and apps.Single cloud regionThird partyBuild it yourselfYou run it
Data going outWhat you pay when users download.Single cloud regionPer GBBuild it yourselfPer GB
Private networkingLinks into your own cloud.Single cloud regionSome regionsBuild 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.

Writing a function

CLI

npm i -g lattice, then lattice init and lattice deploy. Built in seconds and live in 38 regions.

CLI reference →
Deploying a function

SDK

TypeScript, Python and Go clients for the database, queues, storage and realtime rooms.

SDK docs →
Observing a running function

MCP server

Give your agent tools to deploy, read logs, query and roll back through one MCP endpoint.

Connect an agent →

Deploy your first function in two minutes.

Free to start. No credit card, no sales call.

This is a demo

Explore the website. Payments, registrations, bookings, and form submissions are turned off.