OctoractIntent becomes software you can trust.

Describe the system. Octoract builds it, governs it, and proves it, on infrastructure you own.

Described, then built

Tell Octoract what you need in plain language. It turns intent into a real, running system, interface and data together, and rebuilds it whenever the intent changes.

Proven, not promised

Every build and every change is recorded as verifiable, replayable evidence. You can always see what was produced and why, and check it for yourself.

Yours to run

The whole platform stands up on a server you own, secures itself, and keeps itself healthy. One ecosystem, the Hive, or many, federated as a HyperHive.

Honest by construction

From identity and storage to apps and integrations, the pieces are content-addressed and tamper-evident. Trustworthy, repeatable, accountable.

The scenic route

Read the docs in harmonic order: each stop is a golden-angle step off the last, so you cover the whole map without the cold linear march. The scenic route, not the alphabetical one.

(Golden-angle step 7 over 10 stops.)

What is Octoract?: Home
Hive: one ecosystem on your server
aim: content-addressed store
aiMe: the engine beneath
HyperHive: many Hives, federated
aim server: durable source of truth
Crews: small units, one job each
OpenAPI: evidence-bound integrations
aimcr: your own container registry
Carbon: byte-exact bundles

Where to start

New here? Read What is Octoract? and aiMe.
Want the moving parts? Crews, Carbon, aim, aim server, and the container registry.
Running it for real? The Hive (one ecosystem) and the HyperHive (enterprise, multi-server).
Integrating other systems? OpenAPI support, make any model's output repeatable and accountable.