Skip to content

Subspace

Subspace is an operating system for knowledge work. Your notes, your mail and messaging, your task queue, and durable AI agents live in one system, in a place you control. Nothing slips through the cracks, nothing leaks to a vendor, and your assistant actually remembers you.

A Subspace page: an outliner with a labeled value and a live pipeline table

A single page holds bullets, a labeled value, and a live table, everywhere is the outliner.

Under the hood it is a single self-hosted process: one embedded PostgreSQL database holds every page, message, task, and agent run, and every surface (web, desktop, mobile, browser extension) is a thin client of it. Because the whole graph is yours, agents can read across all of it, act with your permission, and their work is journaled row by row.

A programmable knowledge graph

An outliner where every bullet is a node in a graph. Pages, directories, [[links]], #tags, ((embeds)), backlinks, tables with formulas, code cells, and files, all speaking one command protocol.

Comms that live in the graph

Gmail, calendar, meetings with live transcription, and Slack / Telegram, mirrored into the same graph your agents and notes use. People become CRM pages automatically.

An ops spine

Every state change emits an event; a triage layer routes it by severity; an inbox, task queue, reminders, and scheduler turn “things that happened” into “things to do”.

Durable AI agents

Agents defined as editable pages, running on a durable engine that survives restarts, pauses for your approval, spawns sub-agents, and records every step.

Subspace is one system that reshapes itself around who is using it. The marketing site frames this as four audiences; the underlying graph is the same.

One system, one database, one transaction boundary

Every durable fact lives in one embedded PostgreSQL instance. A user edit commits atomically with its link, label, and dependency reindex, its command-log row, and its outbox notice. An agent step’s checkpoint, output nodes, and approval task commit in a single transaction. There are no guarantee-free seams between domains.

In a place you control

Subspace runs on your laptop first (or a box you own), binds to localhost or your tailnet, and never opens a network listener on the database. Moving to an always-on server is moving one data directory. Your comms and knowledge never transit a vendor you did not choose.

Everything is a page, everything is a command

Agents, skills, MCP servers, judges, and settings are all ordinary pages you can edit, version, and deploy from git. Every change to the graph is an audited command produced by a pure reducer that runs identically on client and server.

Agents you can trust because you can see them

Agent runs are durable and inspectable: a run tree with per-step logs, the exact model input at any step, approval gates on every outbound or irreversible action, and a capability broker that decides what secrets a run may touch.