Structured Data Integrations

Position

Prox OS is the OS for structured data apps. It should make many structured data sources visible, governable, and AI-readable without binding users to a single vendor or forcing the Prox OS repo to maintain a full database UI product.

First Recommended Reference: Grist

Grist is the first recommended white-box structured data app for Prox OS because it combines spreadsheet flexibility with database-like structure, supports self-hosting, and aligns with personal/team data sovereignty.

Recommended integration modes:

self-hosted Grist instance;
iframe app in Prox OS;
external app manifest;
API connector or import job;
future Prox OS app package protocol.

Grist is not the only path. It is the first white-box reference integration. Prox OS should not vendor Grist source, maintain a Grist fork, or make @prox-os/data-table depend on Grist runtime code.

Future Candidates

Candidate	Position	Why not default now	Future path
Baserow	Open-source no-code database and application builder alternative.	It is closer to a full platform, so the boundary is heavier than a primitive package.	iframe, API connector, external app.
Teable	Postgres-native Airtable alternative worth watching closely.	License, architecture, and self-hosting model need deeper review before becoming a default.	experimental candidate for Prox OS + Postgres.
NocoDB	Airtable-like database UI and SQL frontend compatibility target.	Source-available and commercial boundaries need review.	compatible connector or iframe candidate.
Univer	Spreadsheet/office-like and AI spreadsheet engine direction.	More relevant to future spreadsheet apps than current data surface primitives.	spreadsheet app, AI sheet automation, MCP sheet flows.
Airtable	Proprietary external structured data source.	Not white-box and not an official default.	user connector, import, or external source.

Integration Modes

OS shell discovers app/source by manifest.
Data contract describes dataset, fields, views, and chart specs.
Table/viz packages render OS-native surfaces.
External products keep their own runtime and internal routes.

Supported or planned patterns:

iframe app;
external app;
API connector;
CSV/data import;
Postgres view;
future package protocol.

Stewardship

The Frontend Package Steward role owns ongoing evaluation of table engines, chart engines, white-box data apps, license notes, benchmark notes, Storybook examples, and data package boundaries. AI agent hats can split the detailed work into Data Contract, Data Table, Visualization, Storybook Coverage, and License & Policy Watch scopes.