Read the brain
maildescriptioncallchat_bubbleneurology
Use vector, full-text, and graph retrieval, with the same context your AI sees.
Pro Brainers / build on brains
Brains, but you write the program.
Spawn automations that read your brain, call any LLM, write to boards, and fire integrations, sandboxed with cost caps and human review for risky writes.
One program. Three superpowers.
Every automation can read memory, shape the workspace, and reach the tools your team already uses.
Shape the workspace
append_board_rowsupdate_board_rowpublish_mini_site
Read and write typed boards, then place a real web interface on top.
Reach the real world
await llm.call(prompt);
await integrations.draft(email);
await human.confirm();
await integrations.draft(email);
await human.confirm();
Call any model and more than 200 integrations with explicit scopes and review.
Automations
Sandboxed programs that run on your brain.
Automations can query memory, read and write boards, call Anthropic, OpenAI, Google, or local models, and reach more than 200 integrations. Every run is sandboxed, metered, scoped, and audit logged.
Brain
Vector, full-text, and graph retrieval, using the same context your AI sees.
Boards
Append, update, score, archive, and restore typed rows with schema validation.
LLMs
Call any supported model with per-call, per-run, and daily cost caps.
Integrations
Gmail, Drive, Calendar, Slack, GitHub, and 195 more without ambient network access.
Memory triggers
Run when reality changes. Not only on a clock.
A customer email lands. A meeting moves within 24 hours. A pull request opens. Memory triggers filter the pages entering your brain and pass the matching page directly into your handler, once per match.
Cron
Fire on a familiar schedule for briefs, reports, and recurring maintenance.
Memory
Match page kind and frontmatter such as sender, date, tag, attendee, or repository.
Webhook
Respond to an authenticated inbound request from your own systems.
trigger: memory({ kind: "email", from: "@acme.com" })
matched once / page passed as input / retries remain idempotent
matched once / page passed as input / retries remain idempotent
Boards
Each board is its own shared brain.
A hiring board remembers every candidate conversation. A deal board remembers each email touch. Rows, comments, attachments, edit history, and decisions compound into common context for the team and its agents.
- Scoped per boardThe hiring brain remains separate from the CRM brain.
- Permission awareOwners, contributors, and observers only see what their role allows.
- Same retrievalBoards use the same query model and MCP shape as personal memory.
- Live APIAutomation writes appear in the interface immediately, with schema validation and history.
Image placeholder - board and shared memory
Mini-sites
Publish tiny sites from live boards.
Turn a board into a focused mini-site: a customer portal, public intake form, internal dashboard, or shareable status page. The interface stays synced to the rows underneath, and access rules flow down from the board.
Pin a view
Share kanban, cards, tables, charts, and KPIs over live board data.
Collect rows
Embed a public form anywhere and send typed submissions directly into the board.
Version every publish
Diff a draft against live, publish a revision, or revert in one click.
Integrations
Reads are cheap. Writes are reviewed.
Fresh reads run inline and persist their result as memory. Risky writes use a two-phase draft, confirm, send flow with previews, expiry, idempotency, costs, and latency captured in the audit log.
Image placeholder - draft / confirm / send flow
- FetchRead fresh data and persist the result as a queryable page.
- DraftCreate a previewable draft with a time-to-live.
- ConfirmApprove once; repeated confirmations return the existing result.
- Auto-executeRead-only or reversible actions may skip the gate when explicitly configured.