Interweave

Admin UIs for API-backed products kept collapsing into the same hosted-builder compromise, a tool that did not quite fit the data model. Interweave generated those UIs from response shapes, including forms, tables, RBAC, and encrypted tokens, and tried to stay in step as the APIs changed.

It worked well enough that we still use it to manage content on API-driven apps. The miss was architectural: we put a cloud proxy in front of private APIs, which made demos easy and production uncomfortable. Local-first would have been the better shape, generating the UI where the data already lives without shipping secrets through our servers.

The useful residue is a sharper rule. If the product is a window onto someone else's API, do not become the network path.