A database for every app your users build.
On a vibe-coding platform, every generated app needs somewhere to store data, and you cannot stand up a Postgres instance per app. Turso provisions a database per app through an API call, cheap and instant enough to ship with every project your users create.
Why platforms choose this pattern
A database per generated app
Each app gets its own isolated store. No shared schema, no noisy-neighbor risk between user projects.
Provisioned by API
Create a database in the same flow that creates the app, with no human in the loop.
Economics that work for free users
An idle database costs only storage, so you can give every user, including free users, a real database.
Minimal integration
Because Turso is SQLite-compatible and accessed over HTTP, a generated app can read and write with a few lines of client code. Teams have integrated per-app provisioning in under a day, and a full app reads and writes in roughly 17 lines.
Val Town provisions a managed SQLite database for every user-built app and treats per-app data as an architectural default, making it cheap and lightweight enough to ship as fast as users build.
Read the Val Town storyTry Turso for yourself
Spin up your first database in under a minute on the free Starter plan, or fork the open-source Turso Database on GitHub.
