Specbase

Your Supabase data, searchable on your own computer.

Specbase is the store Spec builds from your database. Give it a Supabase or Postgres dump file. It reads the file without connecting to anything, and never runs a statement from it.

Rows and links. Every row becomes a record, linked to the rows it refers to.
Your tables, explained. Tables, columns, views and your own descriptions of them become searchable too.
Who may see what. Your database’s row-level security rules decide which rows each person can find.

Nothing has to move. Your app and its live database stay where they are, on Supabase, AWS or wherever they run today, and keep working as before. Specbase works from a copy.

When Spec runs on your computer, searching that copy doesn’t go over the internet, and keeps working with the internet switched off.

See it in the demo

What Specbase sees in a database

This is what it found in the made-up bakery’s dump file, without connecting to anything:

5 tables and 1 view

customers: 501 rows
products: 6 rows
orders: 20,020 rows. “One per customer order; a refund keeps the row with status refunded”
order_items: 33,333 rows
favourites: 429 rows
open_orders (a view): orders not yet delivered, refunded or cancelled

Links between rows

Each order is linked to its customer.
Each order line is linked to its order and product.
Each favourite links a customer to a product.

These come from the database’s own foreign keys.

Who may see what

The customers table has a row-level security rule, staff_read.

Specbase applies rules like these, so each person finds only the rows they may see.

What Specbase is not

It doesn’t replace Supabase or run your app. It reads and searches, and your app keeps running where it is.
It never runs a statement from your dump file.

Try the demo About Spec