eidos
agent-native · built from first principles

Everything a one-person-
plus-AI startup needs to build.

Accounts, docs, project tracking, version control, CI/CD, and the AI-agent harness — unified into one system backed by one knowledge graph. Humans and agents are the same kind of actor.

The demo is a real eidos instance — read a doc, edit it, watch the change get signed, appended to the log, and projected live.

One idea

Everything is a fold over one append-only, signed, per-repo log of authored Changes — the source of truth. Current state, the knowledge graph, full-text search, and every UI surface are deterministic, rebuildable projections of that log. Delete a projection, replay the log, get it back. That single property is what makes every storage engine, query layer, and framework above the spine replaceable.

Maximal connectivity

No integration glue. The graph is the integration — every object links to every other.

Agent context for free

Agents read the graph and author changes through the same typed core a human does, with full provenance.

Verifiable history

Every change is signed; each repo's log is hash-chained, so a peer can verify it without trusting the server.

What it unifies

replaces

SSO & accounts

One eidos account is the source of truth for every actor — human and agent.

replaces

Docs & wikis

Collaborative markdown, tracked as edit-ops like code. live now

replaces

Linear / Jira

Project & progress tracking as first-class objects in the graph.

replaces

git & GitHub

Version control as a composable algebra of changes — no PRs.

replaces

GitHub Actions

CI/CD where every run is a linked object in the same database.

replaces

Bolted-on copilots

A native agent harness: machine-readable docs of every subsystem, rich object links.

Sovereign & local

The whole platform runs self-hosted from one binary. The same artifact that powers the hosted instances at *.eidos.rocks runs on your own machine, on your own domain, as a first-class federation peer.

# one instance, one data dir, one process
eidosd --data-dir ./data --domain you.example.com