Your staff, without the Supabase dashboard
The table editor is for you. Adminium gives the people who run the business a sign-in of their own and only the tables and actions their role allows.
Supabase
Supabase is PostgreSQL, so Adminium builds the back office straight from your schema: editable tables, a page for each record with its related rows, roles for your staff and an audit log. Your app does not change.
npx @adminiumjs/adminium new my-admin The table editor is for you. Adminium gives the people who run the business a sign-in of their own and only the tables and actions their role allows.
Your policies are written for your app’s users, so a new role sees empty tables. The docs show how to let Adminium’s role see every row, with one statement or a policy per table.
Adminium leaves out the schemas its role may not read, such as Supabase’s own auth and storage. Grant just the columns you want, like a customer’s email, and orders show who placed them.
Every Supabase connection string works. The session pooler or the direct connection is the better choice; the transaction pooler on port 6543 works as well.
Setup only reads the schema. Adminium keeps its own users, roles and page layouts in a store of its own, which can be a file or a separate database. After that, people change rows through it, within the roles you set.
Row Level Security. Postgres leaves out the rows no policy lets the role see, without an error. Give Adminium’s role BYPASSRLS, or a policy on each table; the PostgreSQL guide in the docs has both.
Yes, when the app keeps its data in a Supabase project you can copy the connection string from. Adminium connects to that database the same way, and the app itself does not change.
Nothing. Adminium is AGPL-3.0, with no limit on tables, pages or users.
Keep reading
Supabase is a trademark of its owner. Adminium is not affiliated with Supabase.
Free and open source. Running on your own machine in about a minute.