Branching data
Every pull request gets a copy-on-write branch of your database. Merge the code, keep the data.
Public beta · free for small teams
Build your backend, layer by layer.
Strata gives small teams a database, functions, auth and an edge network that snap together like blocks. Scroll and watch it build.
01 · Data
Start with a database that grows with you.
Postgres-compatible storage with branching, backups and point-in-time restore. Every preview deploy gets its own copy of the data.
02 · Functions
Drop in functions. They snap into place.
Write TypeScript, push, and each function lands right next to your data. There are no servers to size or patch.
03 · Auth
Lock it down without a weekend of plumbing.
Passkeys, magic links and roles, wired to the same tables your app already reads.
04 · Edge
Ship it close to every user.
One command puts your app on a global edge network, with caching rules you can actually read.
05 · Flow
Follow one request through every layer.
Edge, auth, function, data: each hop is traced on one timeline, so you see the whole path instead of guessing.
GET /api/orders
- Edgecache miss, forward
- Authsession ok
- Functionorders.list()
- Dataread from main
200 OK
06 · Inspect
Pull the stack apart. See what talks to what.
Logs, traces and costs live on the layer they belong to. Hover a layer to see what it does.
- Data
- Functions
- Auth
- Edge
07 · Ship
Snap it back together. Ship it.
When it looks right, one command puts every layer live at once.
The platform
Four layers. One mental model.
Each layer does one job and talks only to the layer below it. Scroll and the stack opens up so you can see the whole request path at once.
- Edgerouting, cache
- Authusers, roles
- Functionsyour code
- Datatables, files
Features
Small pieces that fit together.
Functions next to data
Functions run in the same region as the tables they read, so most queries never cross an ocean.
Auth that reads your tables
Sessions and roles are rows you can query, not a black box with its own dashboard.
Edge by default
Static files and cached responses are served from the closest point of presence.
Traces you can follow
Follow one request from the edge to the function to the query, on one timeline.
One config file
strata.toml describes every layer. Review infrastructure changes like any other diff.
From zero to deployed
Three commands, in this order.
Create a project, add the layers you need, ship. Everything you just did is written to strata.toml, ready to commit.
1$ strata init my-app
2$ strata add data functions auth
3$ strata ship
›Live at my-app.strata.example
Pricing
Start free. Add layers as you grow.
Hobby
$0
For side projects and learning.
- 1 project
- Shared database
- Community support
Team
Most teams$24
Per month, for small teams shipping weekly.
- Unlimited projects
- Database branching
- Passkeys and roles
- Email support
Scale
Let's talk
For apps with real traffic and audits.
- Dedicated database
- Private networking
- SSO and audit logs
- Named engineer
FAQ
Questions, answered.
Is Strata a real product?
No. Strata is a fictional brand made for this template. Swap in your own product, copy and pricing.
Does the 3D scene need WebGL?
No. Every block is a few HTML elements turned in 3D with CSS. There are no canvas, WebGL or image files in the scene.
What happens in older browsers?
Browsers with CSS scroll-driven animations run them natively. Others get a small script that drives the same animations from the scroll position.
And with reduced motion turned on?
The pinned section becomes a normal section, the scene appears fully built and the chapters read as a list.
Can I change the blocks?
Yes. Each block is one div with its position, size and colour in Tailwind classes, plus the scroll range it builds in.
Start free
Lay the first block today.
Start on the free Hobby plan with one database. Add functions, auth and the edge when you need them. No card, no sales call.
- Free Hobby plan
- No card needed
- Upgrade when you ship