CEDX Tables · Developer & low-code
Tables is where the estate's working data lives: bases with owners and sensitivity labels, records that show their fill and their agent runs, and a schema-debt queue that ranks the cleanup instead of hiding it.
The overview's first alert is not storage or speed. It is 7 broken link fields, with the fix named: retarget or delete. Data tooling earns trust by showing its own mess first.
Runs on demo data — Northline ops data is the demo workspace, not a customer.
What it is
24 bases, each with category, table count, records, health, people, external shares, sensitivity and an owner. The incident log holds 892 records at health 93, Restricted; the API keys registry shows 38 people and 5 external shares. Sensitivity is a column, not a promise.
320 records with table, base, status, agent run, fill, edits and owner. Lead · Acme 505 sits at 55% fill with an agent run Done; Asset · Sync 878 shows its agent run Failed, with a re-run count of 6 across the workspace. When automation writes, the record says so.
120 views across grid, kanban, calendar, gallery and form, each with filters, opens and an external flag. Shared kanban 40 opened 1.2K times in 30 days; 24 views are shared outside the workspace — and the permission blast knows which ones.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/tables.
01 — Overview
320 records, 96 tables, 103 schema-debt items, 72 share edges and 502K cell edits in 30 days — rolled into a data health of 70 against a 72-to-85 target. The do-this-next queue is scored: revoke the Revenue pipeline's partner share at blast 83, fix the top 7 broken links, archive 51 unused fields.
02 — Bases
From the incident log at health 93 to the vendor register at 58, every base shows what it holds, who is in it and how exposed it is. The ops chip cuts the list to the bases the field teams actually run on.
03 — Records
Records carry a fill bar, an edit count and an agent-run state, so a half-empty record is visible before it poisons a report. Locked records keep their state on screen — 17 of them in the sample.
04 — Views
Views are the way data leaves the building: 90 of 120 are shared, 24 externally. Each carries its type, filters, opens and owner — the intake form opened 760 times in 30 days and is external. That is the list an audit starts from.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Run the bases their teams live in — incident logs, training rosters, field-service work orders — and own the health score that comes with the job.
24 bases · 625 collaborators
Works the schema-debt queue: temp col 3 at 76, the deprecated flag at 72, and 51 archive candidates with null rates above 50%.
103 debt items · 15 high
Own the agent runs writing into records — 48 of them in the sample — and re-run the 6 that failed before the fill rate becomes a lie.
48 agent runs · 6 failedThe shape of it
Every figure below is legible in the captures above. Nothing here is a projection of your estate — it is the state of the demo data.
How it runs
Data starts in a base with a category, a sensitivity label and an owner — Restricted, Internal, Confidential or Public, on the row.
Records carry fill percentages and edit counts, and agent runs write too — 48 records in the sample show automation's handwriting.
Views multiply the surface: 90 of 120 are shared, 24 of them outside the workspace, and the permission blast scores each edge.
The debt queue ranks the sweep: 7 broken links, 15 high-debt items, 51 unused fields over 50% null — each with the fix named.
One record
Tables is not a spreadsheet with logins. It is the structured record the estate's apps, automations and connections read and write.
Builder apps bind to these bases as data sources — which is why a broken link field shows up on both products' overviews.
CEDX ScriptsThe agent runs writing into records are Scripts automation — scheduled, priced per minute, and logged.
CEDX IntegrationsSynced records land in owned, sensitivity-labelled bases rather than an unmapped staging area.
CEDX APIEvery base is reachable through the governed routes and keys the API console scores for blast radius.
Limits
Finding this out on the third call is worse for you than reading it here, and worse for us.
Start
Open it right now
Your first bases
Tables with the rest of it
Questions
Yes. Every screenshot is a capture of the running build and you can open the same build at /app/tables. It runs on demo data from the Northline ops data demo workspace.
A scored queue of the cleanup a data estate accumulates: broken link fields, deprecated flags, unused fields over 50% null. The demo workspace carries 103 items, 15 of them high — each with the fix named, from retarget to archive.
Yes, and the record says so. 48 records in the sample show agent runs, with Done and Failed states and a re-run count of 6 — automation's edits are visible, not laundered into the edit count.
Views can be shared by link or domain, and 24 are. Each carries an external flag, an opens count and an owner, and the permission blast ranks the widest edges first — the Revenue pipeline partner share scores 83.
No certification has been issued. What we can evidence about hosting, encryption, tenant isolation and production access is written up on the security page.
Live build, demo data, no card. Then count the broken link fields in the base your team actually runs on.