Spreadsheets are breaking out as API execution layers. Sourcetable — an operational spreadsheet that can read and write to any API — turns a sheet into a workflow engine [1].
Execution-layer spreadsheets and back-end rivals are changing who orchestrates what. Sourcetable uses natural language commands to drive actions across services; three integration modes (pre-built connectors, generative connectors, credential vault) and a full audit trail in cells push governance into the sheet itself [1]. Excel compatibility keeps it approachable, while a Python/ FastAPI backend with Ray handles distributed work and DuckDB WASM powers client analytics [1].
Three-schema backends are gaining mindshare. Nuvix — Open-source backend-as-a-service that aims to fix what people hate about Supabase and Appwrite — offers three schema types: Document, Managed, and Unmanaged [2]. Managed gives auto RLS and permissions; Document is rapid prototyping with manual security; Unmanaged unlocks full SQL power on Postgres [2].
Killer features push the idea further: APIs better than PostgREST (join without FKs, filter by nested columns), a dashboard with an auto RLS editor, a Type-safe SDK, the Bun runtime, and self-host in 2 minutes with Docker [2].
Taken together, these approaches remix DB access patterns and governance—shifting some logic into the data layer while strengthening visibility with audit trails and auto RLS.
References
Show HN: Sourcetable – Operational spreadsheets that can read/write to any API
Spreadsheets become execution layer with API reads/writes, NL commands, connectors to Postgres/DuckDB, vs traditional workflow tools, Excel compatibility, audit trails
View sourceShow HN: Nuvix – Open-source Supabase and Appwrite with 3 schema types, auto RLS
Show HN: Nuvix—TS backend-as-a-service with three schema types (Document, Managed, Unmanaged), auto RLS, and Postgres power.
View source