A living atlas, not a static diagram.
Onboardr's architecture is built to be inspected. Every layer is observable, every decision is versioned, every contract has an owner.
Onboardr maps your repo into a living atlas.
Every service, every contract, every boundary — visualized as a real-time graph that you and your AI co-pilot can navigate together.
From git remote to grounded answer.
Scroll to walk the pipeline. Each stage holds the diagram, narrates the layer, and shows the signals it produces.
- 01
Ingest the repo
Onboardr clones, walks, and chunks. Multi-repo, monorepo, polyglot — every file gets a typed handle and a freshness signal.
12,402 filespolyglot treefreshness signal - 02
Verify trust boundaries
Edge auth and customer-scoped keys gate everything. Code never leaves your tenancy, embeddings live next to your data.
SOC2zero retentionscoped keys - 03
Build the graph
Symbols, contracts, dataflow, and runtime traces fuse into a single live atlas you can navigate and reason over.
18,402 edgesownershiplatency overlays - 04
Reason with citations
A long-context model answers grounded in real files and lines. If we can't cite it, we don't ship the answer.
12.4M tokens0 hallucinationscite-rate 94% - 05
Store + replay
Embeddings in pgvector, metadata in Postgres, raw artifacts in S3. Replay the repo's history as a cinematic timeline.
pgvectorgit → motiondeltas, not rebuilds
scroll to advance · keyboard ↓ also works
Six layers. Tight contracts.
Each layer knows what it owns and what it doesn't. That clarity is why we move fast safely.
Edge runtime
Stateless, globally replicated. Auth, rate limiting, and orchestration live close to the user.
Reasoning core
Long-context model with retrieval over your repo's semantic graph. Always grounded.
Graph engine
Symbol, dataflow, dependency, and ownership data fused into a single live graph.
Vector + relational store
pgvector for embeddings, Postgres for metadata, S3-compatible for raw artifacts.
Workers
Indexing, watchers, and re-rankers fan out across an autoscaled queue.
Trust boundary
Encrypted in flight + at rest. Customer-scoped keys. Zero retention by default.
What we refuse to compromise on.
Every architectural call we make is downstream of these four principles. They are the load-bearing walls.
Calm by default
We push surface area down, not up. The default UI is quiet because the model is confident.
Cite or shut up
Every claim links to a real file, line, and commit. If we can't cite, we don't ship the answer.
Local feels good
An offline-first index runs on your laptop. Cloud is for scale, never for lock-in.
Speed is a feature
Sub-90s first index, sub-200ms search. We pay for milliseconds with engineering, not abstractions.