Use an anon/publishable key for views protected by your RLS policies.
Included operator console
Run the live game. Skip the emergency build.
Publish content, tune configuration, support players and review activity against the systems installed in your Supabase project—without routing credentials through ShipIt.
Operating model
A static console that works against your own Supabase project.
The dashboard is included as a self-hostable HTML console. It does not require a ShipIt account, a ShipIt server, or a separate backend deployment. You choose which key to enter depending on the task.
Use service-role only on a trusted machine for admin actions like bans, rewards and global config.
Keep it local, place it behind your internal tooling, or host it on your own static site.
Operator workflows
The controls a small team actually needs.
Announcements
Publish news, maintenance notices, events and promotions with scheduling and priority.
Remote configuration
Retune values and flip feature flags without waiting for store review or a player update.
Rewards and mail
Send trusted reward payloads through the secure mailbox workflow installed by the backend pack.
Player support
Find player records, review account state, and move directly into a support or moderation action.
Moderation
Review reports, ban or unban players, and preserve an auditable administrative trail.
Operational visibility
See game KPIs and inspect the tables created by the packs your project actually uses.
Security boundary
The dashboard and source are delivered inside the paid toolkit. Administrative credentials remain on the operator's machine, and player-facing builds never receive service-role access.