Inside the platform

Built to keep changing.

The technical detail behind your app: its blueprint, change review and connections. For setup instructions, read the documentation.

Your system lives in a blueprint, not someone’s head.

Read the architecture

A versioned spec, not tribal knowledge.

Your app has a saved blueprint. You can review its structure without searching old chats. When people leave, the knowledge stays.

Maintained as your business changes.

We handle hosting and ongoing maintenance within your agreed service. Describe a change and review what it affects before applying it.

01 Dependency map

See what a change touches. Before you apply it.

Learn more

Every saved version carries a map of its own structure: fields, tables, APIs, components, pages, routes, workflows, integrations and roles, with the relationships between them. Select anything to see what depends on it, search it, filter by type or read the relationships as a list. Viewing the map is read-only and uses no AI credits.

Running on our development environment. The map is static analysis, not proof: it tells you what to review, and your own tests still decide whether a change is safe.

Blast radius

Safe, affected or breaking

A proposed change is compared with the saved version: additions, modifications, removals and the dependents of each. Removed items stay visible with their dependents instead of disappearing.

Review and apply

Read the change, then decide

Open the pending change in the map or the editor and apply or cancel the same candidate. Applying saves a new version, which refreshes the map and the preview.

Version history

Compare and restore

Browse saved versions, compare them and restore one behind a version guard. A restore does not reverse data edits, sent messages or payments.

Field edits flag the consumers of the whole table, and dynamic table names or custom code can have effects the map cannot see. How change review works

02 AI client connections · Scoped access

Connect your AI client. You control access.

Use MCP to share selected app records, chart data and saved PDF text with a compatible external AI client. Connect through OAuth sign-in or a scoped token, with permissions you choose in App settings.

Check the connection controls available in your app before setting up an external client. Contact us about availability. External clients use their own provider’s data-processing terms. MCP supports Global mode and EU mode with separate owner consent for each external connection.

Your app

Built and hosted by Chromoly

External AI client

OAuth sign-in, or a scoped token

App actionsUse the app’s business actions: Request supported booking, invoice or other saved actions. The app validates the request, and you review it before execution.
Workflow monitoringFollow work through to its result: See progress and failures. Approve cancellation or safe resumption of an eligible failed step without restarting completed work.
Connection controlsChoose what each client can do: Select tables, fields, actions and workflows. Review activity, revoke one connection or disconnect all clients. Cancel approved workflows separately.

Actions depend on what your app supports. Business actions and workflow controls require owner approval; optional automatic approval is limited to eligible draft-only design edits. Explore MCP setup and permissions