Data
Every project gets its own Postgres database and its own file storage, with no setup and no credentials in app code. Access is decided per signed-in person: Postgres row-level security for rows, and ownership rules plus app roles for files.
Database
One Postgres database per project, roles, and how your code connects.
Table editor
Create tables, edit rows, import and export CSV.
SQL editor
Run SQL with a timeout, read-only mode and saved snippets.
Row-level security
Policy templates, plain-English policies and identity helpers.
Schema view
The tables and relationships as a diagram.
Migrations
Versioned SQL applied on deploy, once each.
Data API
Supabase-compatible REST over your tables at /_tc/db.
Storage
Buckets, visibility and who can read or change a file.
Uploads and signed URLs
Upload, download, list and share files safely.
Quotas and limits
Project quota, file size, allowed types and cost.
How data access works
| You use | Runs as | Row-level security |
|---|---|---|
tc.db.from(...) in the browser (the Data API) | The signed-in person (tc_user) | Applies |
tc.db.asUser(req) in server code | The signed-in person | Applies |
tc.db.sql or DATABASE_URL in server code and jobs | The project's service role | Bypassed |
| The Studio in the console | The project's owner role | Bypassed (it's for builders) |
tc.storage in the browser or with the request | The signed-in person | Ownership rules and app roles apply |
tc.storage in jobs | The app | Manages every file |