Loading…
developer hub
Browse the platform database, download integration prompts, manage access. Admin only.
Joining the waitlist does not create a usable account. An admin approves you in Clerk (who are you), then separately grants database access (what may you see). This hub itself is admin-only.
developer hub
The audit trail: who changed what, and the old → new values. Writes from the terminal or loaders show as owner/CLI. Currently audited: app_users; new tables opt in per migration.
CRM edits queued by app users (change_requests). Apply the change at the source system, then mark it here.
A generated build prompt for wiring this Clerk instance and the Data API into a new app — paste it into Claude Code or Cursor. It embeds the live table reference, the token discipline, the error taxonomy, and the RLS contract, so a new app starts where this hub finished.
Every request: a fresh Clerk token (they live ~60 s) as Authorization: Bearer, plus Accept-Profile: app on reads / Content-Profile: app on writes. Paths are unprefixed. The database decides every row via RLS — send no client-side scope filters. Full details live in the Prompts tab's starter prompt.
The path from idea to scaffold, like Pocket CRM or TiplistToGo. An app is two things here: an entitlement key in users' apps arrays (what has_app() checks), and a client application built on this Clerk instance + Data API. This generates a tailored build prompt for the second and the registration email for the first.
New tables and policy changes are applied by the platform owner through migrations — this builds the request, it does not execute anything. Fill it in, copy, and email it.
Everything here is written through the Data API and enforced by RLS — a non-admin calling the same endpoints gets nothing.
Create their identity in Clerk first (invite below), then grant access here. The sub is their Clerk User ID.
Invitations, session revocation and bans run through a small server function holding the Clerk secret key; the database never sees it, the browser never sees it. Password resets stay self-serve: the person uses “Forgot password” on the sign-in screen.
The same grant, from the terminal — for when the hub or the Data API is unavailable. Run from the doka-platform repo, where DATABASE_URL lives.
Gate 1 · Clerk answers who are you. Gate 2 · this command answers what may you see. Gate 1 alone is a working sign-in that sees zero rows everywhere — correct, not broken. Nothing per-user ever happens in Neon or GitHub.
Traps: flags are space-separated pairs (--flag=value silently mis-parses) · the flag is --extkey · email is unique — if their Clerk account was recreated, delete the old row first or the insert dies with 23505.
is_active = false on their row darkens every table instantly (app.me() filters on it), then ban or delete in Clerk. Deleting the row cascades away their user_state, change_requests and tiplists.
Decoded client-side; the signature is verified by Neon, not here.
No token acquired yet.
Clerk says who you are; this table says what you may see.
The role Postgres actually ran your query as, and the sub it resolved.
Every table, graded against what your app_users row should produce.
Each probe inserts a throwaway row and deletes it. Expected outcomes are shown per step.
Last 50 requests, newest first.
Empty is the correct state.