Catalogs
Every Table, One Browser
Raw, Clean, and Ready, all in one place. Schema history, who can touch what, and whether a table is falling behind, without hunting across three separate views.
What It Is
The single place every table you have shows up, no matter which layer wrote it.
A pipeline produces a table in Raw, Clean, or Ready, and it appears here automatically: no separate registration step, nothing to keep in sync by hand. Catalogs is where you go to find a table you know exists, check what changed about its schema recently, see who can write to it, and tell whether it's actually being kept up to date.
Five Tabs
Each one answers a different question about the same tables.
Tables
Every table across Raw, Clean, and Ready. Search by name, filter by layer, and select several at once for a bulk delete. Deleting is soft by default: a pending banner shows what is queued, so nothing disappears without a chance to undo it.
Collections
Named, taggable groups of tables. Useful for grouping everything behind one feature or one team, so you can find them together without renaming a single table.
Schema
A timeline of real schema changes: columns added, types changed, and more. Breaking changes surface as their own alerts with an unacknowledged count. A pipeline run that only adds new rows, without touching the schema, will not show up here; that history lives on the table's own Snapshots tab instead.
Access
Every workspace member gets implicit read access to every table. Write or admin access is explicit: request it, and an admin approves or denies it from a pending queue, with full history kept after the fact.
Health
A freshness score for every table, computed from when it last updated, against a threshold set per layer (Raw, Clean, and Ready age at different rates on purpose). Anything falling behind shows up as an issue you can acknowledge or resolve.
Access, in Three Levels
Everyone can look. Not everyone can write, by default.
Read
Every workspace member has this on every table, automatically.
Write
Can build pipelines that write to this table. Requested, then approved.
Admin
Can grant access to others and manage the table itself. Requested, then approved.
What Counts as a Schema Change
Only real structural changes show up on the Schema tab's timeline.
Column added
A new column appeared in the table.
Type changed
A column's data type was altered.
Breaking
A change likely to break something reading this table downstream.
Deleting a Table Is Soft, by Default
Select one table or several and delete them from the Tables tab, and they move to a pending-delete state with their own banner, not straight to gone. That gives you a window to catch a mistake before it's permanent.
What's Next
See how these tables connect to everything else, or go deeper on quality.
No separate registration step. A pipeline writes a table, and it's already here.