← All product featuresDeclarative product
Config-first
Workspaces, automations, views — created as configuration, not code forks.
Synap is built so the product can be extended by configuration: workspace templates, property overlays, automations, packages. Agents propose config; you approve what becomes true.
A builder workspace, a CRM lens, an automation — same pod, different config, no custom fork required to start.
What this makes possible
Three concrete capabilities
Templates install structure
Workspaces, views, and automations arrive as inspectable packages — not opaque binaries.
AI edits config under governance
Agents can propose property defs, views, or workspace overlays; you keep the approval seat.
Same model for people and machines
There is one product shape: config and data on the pod, not a secret admin schema.
How it connects
Config composes with cells, capabilities, and playbooks. The Browser is where you inspect and adjust what was installed.
Config-first is not config-hidden — consequential changes stay reviewable.