db2.eduz.ai

Personal DB inventory — Supabase, Neon, Firebase. Live data via db2-api Worker.

⏳ fetching live inventory from db2-api-eduz
Supabase projects
Supabase accounts
Neon projects
2Firebase projects

Supabase (live)

Auth: account-master PATs only. Project-level keys fetched on demand via Mgmt API.

accountproject namerefregionstatuscreated
loading…

Neon (live)

Auth: account-master PAT only. Connection URIs fetched on demand.

orgproject nameidregionpgcreated
loading…

Firebase (static — Admin SDK not yet wired into Worker)

projectSA fileused by
eduzdbeduzdb-firebase-adminsdk-fbsvc-e5f6013ba0.jsonFirestore (future db2-api v1), FCM push (future)
brain2pk(efus3 — auth IdP)Google sign-in for auth2 + dash2

Aux PgSQL (planned)

Local Postgres on pk2 (home server) — Tailscale (100.96.58.52:5432) or LAN (192.168.1.3:5432).

v1+ not yet exposed; needs the db2-api Worker on a path that proxies via CF Tunnel or a Tailscale-attached compute.

Endpoints & v1 roadmap

Worker URL: db2-api-eduz.ky6p-eduz.workers.dev

Endpoints: / · /inventory · /supabase/projects · /neon/projects

v1: /firestore/collections (needs FIREBASE_EDUZDB_SA_JSON as Worker secret); per-project table browser + row sample (read-only first); CSV/JSON export. Edit gated by allowlist.

The keepalive sister Worker (eduz-db-keepalive) pings each project every 3 days to prevent auto-pause.