Blocks
Table, record detail, form, kanban, calendar, gallery, chart, text, image, button, filter bar and tabs, with formulas, row actions and conditions.
Small apps on your own data, without code
Build small apps on your Tables or Sheets data with pages, forms and roles, and share them with people outside your team.
An app is pages of blocks: table with search, sort, paging, column formulas and inline edit, record detail, form with conditional fields and validation, kanban, month calendar, gallery, chart (bar, line, pie, number), text with formulas, image, button, filter bar, record picker and tabs. Actions open a page or address, create, update or delete a row, set page state, reload, or start a Workflows automation. Sources are sample data, Tables (records API), Sheets (add rows only) and read-only lists from other catalogs' /api/v1 through service bindings; keys stay on the server, sealed per domain or the workspace key. Every call is checked on the server: page and block roles, edit roles, per-source read, create, update and delete permissions, row filters per role and per user, hidden fields stripped, writes limited to the form's fields, and rows cannot be moved out of view. Outside users get a 6-digit emailed code (10 minutes, 5 tries), a 7-day session bound to the app and a per-user variable for filters; removing a person ends access at once. Drafts, published versions with restore, unpublish, a 30-day trash, preview as a role, email and variables, seven templates (CRM-lite, order tracker, inventory lookup, field visit log, approval requests, client directory, asset checkout), and optional Claude features that propose pages over a source and explain a formula. Tables choices are derived from up to 200 rows and scans are capped at 2000 rows per call. API /api/v1/apps and a workspace feed; webhook app.published.
What Interfaces does for you.
Table, record detail, form, kanban, calendar, gallery, chart, text, image, button, filter bar and tabs, with formulas, row actions and conditions.
Tables and Sheets sources, or a read-only list from another catalog; page and block roles, row filters per role and hidden fields are enforced on every call.
Drafts and versions, a shared link and embed, people you invite by email, preview as a role, and seven templates.
A suggested path for Interfaces. What you can do depends on your access in the app.
Connect a Tables base, a Sheets tab or a catalog list.
Start from a template or describe the app and review what AI proposes.
Add the people who may open it and share the link.
Live host, inventory, governance, health checks, verification, dependencies and history.
An app is pages of blocks: table with search, sort, paging, column formulas and inline edit, record detail, form with conditional fields and validation, kanban, month calendar, gallery, chart (bar, line, pie, number), text with formulas, image, button, filter bar, record picker and tabs. Actions open a page or address, create, update or delete a row, set page state, reload, or start a Workflows automation. Sources are sample data, Tables (records API), Sheets (add rows only) and read-only lists from other catalogs' /api/v1 through service bindings; keys stay on the server, sealed per domain or the workspace key. Every call is checked on the server: page and block roles, edit roles, per-source read, create, update and delete permissions, row filters per role and per user, hidden fields stripped, writes limited to the form's fields, and rows cannot be moved out of view. Outside users get a 6-digit emailed code (10 minutes, 5 tries), a 7-day session bound to the app and a per-user variable for filters; removing a person ends access at once. Drafts, published versions with restore, unpublish, a 30-day trash, preview as a role, email and variables, seven templates (CRM-lite, order tracker, inventory lookup, field visit log, approval requests, client directory, asset checkout), and optional Claude features that propose pages over a source and explain a formula. Tables choices are derived from up to 200 rows and scans are capped at 2000 rows per call. API /api/v1/apps and a workspace feed; webhook app.published.
The data itself lives in Tables or Sheets; public websites belong to Websites and Landing Pages; automations belong to Workflows.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
interfaces.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.