Superpowers
A vault can't be handed over. A Workspace can.
You can hand someone a repo. What arrives is instructions — a schema they have to apply, steps they have to follow, a setup that works once they finish. Hand someone a Workspace and what arrives is the running thing: data already typed, Views that render, Automations that fire.Superpower is our word for the six kinds of thing that travel: what you and your agent build on a Data Pod, published as a package and installed on someone else's pod.
The six
Workspace
LiveA whole app: data model, Cards, Views, Automations and its onboarding — declared as one file.
Publishing one serializes a Workspace you are already running — see the loop below.
26 published
Capability
LiveA credentialed tool your agent can call — the API key stays in your pod.
24 published
View
Live · limitedA way of looking at entities — board, calendar, gallery, bento.
Installs on the pod today; the CLI cannot install one yet.
3 published
Automation
Live · none publishedA repeatable triggered process — each execution is an inspectable run.
The loop works end to end; nobody has published one yet.
0 published
Card
Live · none publishedHow one entity renders — and how a View renders, and what sits in a bento.
Rendering code from a package runs in a null-origin sandbox that cannot reach the network, and its writes are proposals like any other. Nobody has published one yet.
0 published
Skill
ComingA verb your agent knows. Skills ride inside a Capability today — a standalone one has no schema of its own yet.
Until it does, we would rather refuse the publish than accept one we cannot version.
0 published
The loop
Author, validate, publish, install.
Four commands, and the last three are the same whether the package is a Capability you wrote by hand or an entire Workspace you have been living in for a month.
01
Scaffold
synap market scaffold <slug>A starting file for a Workspace template, or a Card or View package. Capabilities are authored directly — by hand, or by your agent — rather than scaffolded.
02
Validate
synap market validate <file>Checks the declaration against the schema for its kind, so the failure lands on your machine rather than on someone else's pod.
03
Publish
synap market publish <file>One catalog, one write door. The package gets a version, and the version is what other pods install.
04
Install
synap market install <slug>On the receiving pod the package becomes real: a Workspace arrives as an actual surface with its own dock row in the Browser, not a document describing one.
The shortcut that is the whole point
Your running Workspace is the package.
synap market publish --from-workspace <id>There is no manifest to write describing the app you built. You point at the app you are already running — its data model, its Views, its Automations, its playbooks, its onboarding — and it is serialized into something installable.
The Workspace you use on Monday is the thing someone installs on Tuesday.
What an installed package may do to your pod
Installing does not hand over the keys.
An installed Workspace brings Automations, and its Capabilities hold credentials — so the question is what they are allowed to do. The answer is the same one that governs your own agent: consequential writes arrive as proposals you approve. You see the change before it becomes true, whoever authored the package.
This is the part a folder of Markdown cannot offer, at any price.
The catalog, live
Published today.
Read straight from the catalog that install reads. Nothing here is a mockup; if a kind is empty below, it is empty.
Everything below is ours, so far. The loop is open — the interesting version of this page is the one where most of it isn't.
53 packages published
Workspace 26 published
Research
Adds the IBIS decision-analysis method to the Research substrate — weigh options with evidence and record the decision, not just the winner.
Research
Turn a question into a fully-recorded investigation — sources ranked, hypotheses weighed, findings mapped onto a living graph of fields and concepts.
Outreach & Comms
Personalized LinkedIn and email outreach — sequenced touches against real people and companies, drafted and sent by an agent.
Networking
A brokerage workspace layered on your CRM — client needs, a provider roster, and the intros that connect them.
Meetings & Knowledge
Import and summarize meetings — transcripts become notes, action items become tasks, and attendees become tracked people.
CRM
A focused pre-sale workspace for lead qualification and commercial proposals.
and 20 more
Capability 24 published
Governance Tighten Recommender
Proton Mail (self-hosted bridge)
SOVEREIGN self-host path for Proton Mail: a locally-run Proton Bridge (headless, `synap proton-setup`-provisioned) decrypts Proton's end-to-end-encrypted mail and exposes it as…
Mailgun Inbound Email
Arch Client Intelligence
The Arch's PROACTIVE client-intelligence layer (Waves 3+4), expressed entirely as config — automations + playbooks, zero backend code.
Apollo — People & Company Enrichment
Proactive Digest
and 18 more
View 3 published
Pre-configured views for task management: Kanban board, priority matrix, and calendar
Calendar and list views for events and scheduling
Grid and feed views for bookmarks, articles, and web captures
Nothing published yet: Automation · Card
Build the thing, then hand it over.
Get a pod, build a Workspace in it, and the publish path is already there when you want it.
Get started