> ## Documentation Index
> Fetch the complete documentation index at: https://docs.orbitagents.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Comparisons

> Honest comparisons with the tools people weigh against Orbit.

Orbit isn't the right tool for everyone. Here's how it compares to the alternatives — including when you should pick something else.

## Orbit vs. Claude's native memory

**Claude's memory** persists facts within Claude, for you, in Claude. It's great for personal continuity in one tool.

**Orbit** is cross-tool and cross-agent. Memory filed by your Codex agent is readable by your Claude agent and your n8n workflow. Orbit also adds decisions, an org chart, an Inbox, and a Vault — it's a control layer, not just recall.

**Use Claude's memory if:** you only use Claude, only for yourself. **Use Orbit if:** you run multiple agents or tools that need to share a brain.

## Orbit vs. Obsidian (knowledge graph)

**Obsidian** is a personal knowledge base you maintain by hand — excellent for human note-taking and linking.

**Orbit** is written and read primarily by *agents*, automatically, as part of their run lifecycle. It has trust levels, conflict detection, and decisions that govern agent behavior — concepts a note-taking app doesn't have.

**Use Obsidian if:** you want a personal, hand-curated knowledge garden. **Use Orbit if:** you want your agents to read and write the knowledge themselves.

## Orbit vs. Mem0 / Zep / Supermemory

These are **memory infrastructure** — libraries and APIs you wire into your own app to give it long-term memory.

**Orbit** is a finished product with a dashboard, an Inbox, a Briefing, an org chart, and a review workflow on top of memory. You don't build the UI — you use it.

**Use memory infra if:** you're a developer embedding memory into your own product. **Use Orbit if:** you want a ready-made operating layer for running agents, not a library to build with.

## Orbit vs. LangSmith / observability tools

**Observability tools** trace and debug individual agent runs — spans, tokens, latency. They're built for engineers tuning a pipeline.

**Orbit** is an operating layer: it not only shows what agents did, it governs what they do next via decisions and shared knowledge. Visibility is one part; control and memory are the rest.

**Use observability if:** you're debugging the internals of one agent pipeline. **Use Orbit if:** you're operating a workforce of agents and want shared memory plus control.

<Card title="Still deciding?" icon="circle-question" href="/start/is-orbit-right">
  Read the honest "Is Orbit right for me?" guide.
</Card>