The agent-native stack.
Built for agents. Built to compose. Atomic, Unix-like services — each does one job, small and focused — that agents drive through APIs, CLIs, and Skills. Use-first, claim-later: no signup to start.
Request access$ sys9 db create my-app One CLI launches everything — sys9 run, sys9 db, sys9 smith…
Read sys9.ai/skill.md and follow instructions Hand an agent the skill — it provisions what it needs on its own.
Built to compose.
Atomic, Unix-like services — each does one job — grouped by what they do. Every product pairs a plain-English label with its xx9 name; opt into only what you need.
forkable sandbox for agents.
Fork the whole OS in ~50ms; run up to 1,000,000 in parallel, pay only when running.
agent as a service.
Host agent fleets on run9 — wake on a message.
managed browsers for agents.
Headless sessions — stealth, captcha, screenshots.
serverless Postgres, from terminal.
Postgres + branching (fork the db, its data, and files together) + file storage with no S3, and zero signup.
any sandbox, one filesystem.
A shared FUSE filesystem across sandboxes and sessions, with semantic grep.
one memory, many agents.
Persistent memory across sessions and agents.
secrets, sealed and scoped.
Per-agent grants, rotation, sealed delivery.
one endpoint, every model.
Routing, caching, cost caps, fallback, and multi-provider keys behind one endpoint.
publish once, any agent installs.
A registry for skills, tools, and MCP.
offline evals, online quality.
Quality signals that complement owl9.
messaging, presence, streams.
Three atomic realtime services — agent-to-agent mail, liveness, and append-only streams.
atomic task claim.
Distributed work-claim; one winner.
agents and humans, one team.
Orchestrate heterogeneous agents.
cron and triggers for agents.
Run agents on a schedule or on events and webhooks — cron for agent work.
db9 · serverless Postgres
Serverless Postgres, from the terminal.
Create a database, branch it like code — db, data, and files together — then query straight from your shell. Zero signup, file storage built in, no S3.
| db | branch | region | rows |
|---|---|---|---|
| my-app | main | iad | 18,402 |
| my-app | review | iad | 18,402 |
| my-app | staging | fra | 9,210 |
run9 · forkable sandbox
Fork the whole OS in 50ms.
Serverless Linux sandboxes — fork the entire machine including data and apt packages, run up to 1,000,000 in parallel, and pay only while they run.
| id | base | state | uptime |
|---|---|---|---|
| sbx_acme | ubuntu | running | 2m |
| sbx_q1 | ubuntu | sleeping | — |
| sbx_dev | python | running | 41s |
drive9 · shared filesystem
Any sandbox, one filesystem.
A persistent filesystem shared across sandboxes, sessions, and handoffs. FUSE-mount it locally, semantic-grep (vector + BM25 in parallel), and grant secrets per agent.
| file | size | modified |
|---|---|---|
| report.md | 14 KB | just now |
| pricing.md | 8 KB | 2h ago |
| q3-plan.md | 22 KB | 1d ago |
Atomic primitives compose into real systems.
The recipe: a shared backlog, agent-to-agent mail, liveness, and agents spun up on demand — together, a hosted Claude Code agent team.
task9 + inbox9 + pulse9 + smith9 = a hosted agent team.
Drop a job on the shared backlog, spin agents up on demand, let them claim work atomically and coordinate over mail — while liveness auto-unassigns anyone who dies. No pipelines to declare; the workflow emerges.
$ task9 create "Triage flaky deploy" ✓ task #41 created $ smith9 spawn --skill triage ✓ agent woke on run9 $ task9 claim 41 # agent ✓ claimed · pulse9 holds the lease $ inbox9 send lead --payload '{"done":41}' ✓ delivered · FIFO, guaranteed
Native to your agent stack
sys9 works with the agents and runtimes you already use — agent-friendly APIs, CLIs, and Skills.
sys9 CLI
Developers
One install, launches everything. The umbrella CLI runs each atomic service — sys9 run, sys9 db, sys9 smith — so you opt into only what you need.
npm i -g sys9 sys9 skill
AI agentsPoint your coding agent at the sys9 skill and it provisions what it needs on its own — use-first, claim-later, no human in the loop.
Read sys9.ai/skill.md and follow instructions Start with one service. Compose the rest.
Hand an agent the sys9 skill, or install the CLI and create your first database in seconds. Use-first, claim-later — no signup to start.
Read sys9.ai/skill.md and follow the instructions