Skip to content

GaiaPut AI agents to work — on your terms

Open infrastructure for agent-driven development

The Stack

One machine, five layers — packaging down to surfaces, planes underneath.

Packaging

How everything installs, updates, and ships.

  • tamiasThe entrypoint — fetch, store, cache, dispense
  • scarabConfig loading & templated content packs
Planes

Cross-cutting services: releases and the CI gate.

  • tarsiThe release plane — changelog to publish
  • buphaThe gate — CI as tamias bundles
Engines

The machines — each a small engine owning one mechanism.

  • hyphaDistributed substrate — entities across machines
  • mycoThe ledger — durable work memory
  • kudaRepo memory — verified code maps
  • mimusThe critic — claims verified against code
  • sturnThe WAL — coordination in milliseconds
  • cuoraSecrets broker — sealed, not spilled
  • sepiaSession lifecycle — agents, agnostically
  • lasiusGit & workspace expertise
  • cicadaCalendars as code — scheduled work
Orchestration

Campaigns that drive work across machines.

  • peregrinCampaigns — event-driven orchestration
Surfaces

What humans and agents actually see.

  • pavoThe screen — renders every view

How it all fits together →

The Machines

Small engines, each owning one mechanism. Swipe through — every card links to its docs.

Why GAIA

The missing layers between coding agents and the repositories they work on.

We're building the missing layers between coding agents and the repositories they work on — packages (tamias), a ledger (myco, kuda), a WAL (sturn), an orchestrator (peregrin, sepia), and a queue (bupha, mimus, cicada). Open, minimal, composable. A stack agents can actually run on.

Our story and principles →

Recently shipped

Tags are releases — the latest across the org.

All releases & activity →

Get in touch

Open source, self-hosted — come build with us.

Questions, contributions, or just want to see the factory floor? Contact us →