Integrations / Supabase
Your Supabase schema, alongside your code.
Oynix ingests your Supabase schema (and optionally rows) so your database structure lives in the same graph as your code.
$ oynix connect supabasePrerequisites
- Your project URL and an API key (service_role recommended).
- The Oynix CLI installed and signed in (oynix login).
Setup steps
Install the Oynix CLI
Everything Oynix does runs from one small command-line tool on your own machine — there's nothing to deploy or host. Open your terminal (Terminal on Mac, PowerShell on Windows) and paste this in to install it:
$ curl -fsSL https://get.oynix.dev | sh- Don't have a terminal open? On Mac press ⌘+Space, type "Terminal", hit Enter.
- Paste the line, press Enter, and wait for it to finish — that's it.
- Check it installed: run oynix --version (it should print a version number).
Sign in
Tell Oynix who you are. This opens your browser to sign in with GitHub and links this computer to your workspace — it's how your edits, decisions and presence get attributed to you.
$ oynix login- Run the command; your browser opens automatically.
- Approve the sign-in with GitHub, then return to the terminal.
- If your team uses a workspace key, paste it when asked (a teammate with the master key issues it).
Get your keys
Supabase → Project Settings → API → copy the project URL and a service_role key.
Connect Supabase
Run the command, choose Direct, and enter the URL + key. Name specific tables to pull rows, or leave blank for schema only.
$ oynix connect supabaseSync anytime
Oynix ingests the schema (and any rows you chose) into the graph.
$ oynix connectors sync supabaseCheck it worked
List your connectors to confirm Supabase shows up and is syncing. Once it's synced, ask the graph a question that should now have an answer from Supabase.
$ oynix connectors- You should see Supabase listed as "connected".
- Try it: oynix ask "what did we decide about …?" — answers can now draw on Supabase.
What gets indexed
Schema
Tables and columns, linked to the code that uses them.
Rows (optional)
A bounded sample of rows from the tables you name.
Freshness
Re-syncs to track schema changes.