Station Capora · all systems nominal

Establish your
base in orbit.

Capora gives you a Space — a versioned home base where your files, workflows, and apps live together, and where you and your AI crew dock to get work done. Every change is logged. Nothing drifts.

content-addressed versioned by default agent-native self-deploying
initializing station…
your Space · /base
✥ drag to orbit
01 / DOCTRINE

Not a drive.
A base.

Storage just holds cargo. A base runs it. Under .capora/ live the systems — schedules, change-driven pipelines, deploys — that turn a folder of files into a station that operates itself, whether you're at the console or not.

Address it by name — remote://you/… — and it's the same base for every human and every agent who docks. Work compounds instead of scattering across machines.

02 / SYSTEMS

Station modules, pre-fitted.

Six systems keep the base alive. Compose them — the output of one is the input of the next.

SYS-01

Versioned Space

Every write is a save point. Rewind, diff, and restore any moment. Content-addressed, so identical bytes are never stored — or sent — twice.

SYS-02

Workflows

A trigger — cron, file-change, or manual — plus a script, run in an orbital bay with your secrets. The base does the work while you're away.

SYS-03

Onboard AI

Claude Code rides in the runner. Have an agent edit files, review a diff, or write today's brief — then commit it straight back to the base.

SYS-04

Self-deploying apps

Save an app to your base; its workflow builds and ships it live to /x/you/app. Every deploy comes from a committed state — never a stray laptop build.

SYS-05

Base SDK

Deployed apps read and write their own Space and fire workflows — the station's modules talk to each other, no keys to wire.

SYS-06

Crew: humans + agents

One base, addressed by name. People and agents dock with scoped keys and share the same files, history, and running systems.

03 / OPERATIONS

How the base runs itself.

Docking cargo is the trigger. From there the station takes over.

01

Dock cargo

Copy files up — one primitive for people and agents alike.

capora cp ./app
  remote://you/apps/app
02

Log it

Every write becomes an immutable save point in the base's history.

→ save c_9f2a…
  (restorable)
03

Systems fire

Matching on.change / cron workflows run in the bay with your secrets.

▶ deploy-app
  [on change]
04

Go live

The build ships from the committed state to your public address.

✓ live →
  /x/you/app
04 / CONSOLE

One binary.
One line to dock.

The capora CLI is a single self-contained binary — your control console. S3-style commands you already know; a remote:// address; every write versioned. Upgrades in place with capora update.

cp · ls · run · secret zero runtime deps mac · linux · windows
capora@base — /dev/console
05 / SUPPLY

Dock a ready-made module.

Starter kits are whole-base scaffolds — pull one, review, and it's live. Don't start from an empty station.

◆ starter · daily-brief

An AI briefing that publishes itself

Fetches your sources, summarizes them with onboard AI, and deploys a dated brief site — on a schedule, from your base. Pull & go.

capora init daily-brief
capora run daily-brief
◇ Clearance granted

Bring your base online.

One command establishes your Space and puts capora on your PATH.

$ curl -fsSL https://capora.cc/install | sh