Ot/Documentation

Bring Your Own Database

By default your readings are stored in Ot's built-in storage and everything works out of the box. If you want full ownership of your data — for a school, a research project, or just principle — you can connect your own Supabase database and Ot will route your telemetry into it.

What you need

CredentialWhere to find it in Supabase
Project URLProject Settings → API → Project URL (looks like https://xyz.supabase.co).
Service role keyProject Settings → API → service_role secret key.
Connection stringSettings → Database → Connection string → URI (port 6543 or 5432). Used only to run the table migrations.

Connecting

  1. 1

    Create a Supabase project

    A free-tier Supabase project is enough to start.
  2. 2

    Open Settings → Supabase DB

    In your Ot dashboard, go to Settings and pick the Supabase DB tab.
  3. 3

    Paste your credentials and save

    Ot verifies the connection and automatically runs the SQL migrations to create the tables it needs in your database.

What changes afterwards

New readings from your devices are written to your Supabase project instead of the built-in storage, and your dashboards read from it. Devices don't change at all — they still authenticate with their token, and the bridge routes server-side.

Security notes

Your service key and connection string are stored server-side for routing and are never sent to browsers or devices. Device tokens remain the only credential on hardware, so a lost board cannot expose your database.

Keep the service key safe elsewhere too

The service role key bypasses row-level security in your Supabase project. Don't reuse it in client-side code of your own apps.
Next: Troubleshooting