Three primitives. One runtime. Services that compose.
run9, drive9, and db9 give an agent a computer, a Linux filesystem, and PostgreSQL — dedicated in meaning, shared in implementation. smith9 runs persistent agent sessions on run9. Around them, small composable services handle memory, coordination, transcripts, teamwork, and identity. Pick what you need; authentication, quotas, and retention differ by service.
Three infrastructure primitives. Each exposes a familiar abstraction — a computer, a Linux filesystem, PostgreSQL — with fast provisioning, logical isolation, and shared physical resources underneath.
Compute available
Linux Boxes from images or Snaps; fork a Snap into independent Boxes.
run9 →Filesystem available
Persistent files over a FUSE or WebDAV mount, semantic search, vault grants.
drive9 →Database available
Serverless Postgres with branching and file storage SQL can read.
db9 →One agent runtime, assembled from run9 compute and a persistent workspace. Agents wake on a message and release their sandbox between turns.
Composable services around the primitives — memory, coordination, transcripts, a workbench, and identity. Each is independent; your application connects them.
Agent memory available
Persistent memory across supported agents and sessions.
mem9 →Queues available
Shared tasks with dependencies and atomic claims.
task9 →Realtime available
inbox9 messages, pulse9 leases, tape9 append-only logs.
inbox9 · pulse9 · tape9 →Agent transcripts available
Capture native agent sessions into a private space you configure.
owl9 →Teamwork available
Coding-agent Sessions on local or cloud Hosts, with shared artifacts.
chord9 →Auth available
Sign-in for people, revocable credentials for agents and services. db9 runs on it today.
auth9 →task9 for task claims, inbox9 for messages,
pulse9 for worker leases, and smith9 for hosted Sessions.
Your application connects these APIs and implements scheduling, acknowledgements, retries,
and recovery. This is an architecture pattern, not an automatic integration.
— the composition story Start with one primitive. Compose the rest.
Install the CLI and follow the setup guide for your first service. Agents use the same commands with the credentials and permissions you provide.