Edge Functions
Write a handler, push to main, and it answers from 38 regions in milliseconds. No servers to size and no regions to pick.
- Cold start
- 4 ms median (demo)
- Regions
- 38
- Billing
- Per millisecond
- Runtimes
- Node, Bun, Python, Go
From one file to every region.
Three steps, the same on day one and on day five hundred. Pick a tab to see each one.

functions/orders.ts
Write a handler
Export one function. Lattice gives it the request and your bindings, so the database and queue are already connected when it runs.

terminal
Push to deploy
Push to main and Lattice builds the function once, then ships it to all 38 regions. Every branch gets its own preview URL.

lattice logs
Watch every request
Logs and traces stream in from every region as they happen, in one view you can search for 30 days.
The same handler on two hosts.
We deployed one checkout function to a single cloud region and to Lattice, then called it from six cities. Demo figures for the template.
Cold start
280 ms→4 msp95 from Sydney
410 ms→38 msMonthly bill at 50M requests
$412→$96Call it
Reach it from anything that speaks HTTP.
Every function gets a URL in each region and a typed client for your app.
Questions
Before you deploy.
Which runtimes are supported?
Node 22, Bun, Python 3.12 and Go 1.23. Pick one per function.
How long can a function run?
Up to 15 minutes per request, and longer with background tasks.
Where does my code run?
In the region closest to each request, or pinned to the regions you choose.
Can I keep data in one country?
Yes. Pin a function and its database to a region group, such as the EU.
What happens when a region fails?
Requests move to the next closest region within seconds.
Is there a free tier?
One million requests and 400,000 GB-seconds every month.
Moving from another host?
Bring your existing handlers. Most move over with no code changes.
