Architecture in 3D
Fly through folders, files, types, functions, and dependencies. Search, isolate, bookmark, and trace the shortest path between any two symbols.
Local-first developer intelligence for macOS
See the system.
Change it with confidence.
CodeAtlas turns Swift, Objective-C, C, C++, and Python codebases into explorable architecture maps, then layers in Git-aware review, impact paths, hotspots, coverage, architecture rules, and CI-ready findings. Your source stays on your Mac.
- 5connected workspaces
- 100%on-device analysis
- 0source uploads
One model, five ways to reason
Move from orientation to decision.
Every workspace uses the same project graph, so context follows you from the broadest system view to the exact relationship behind a risky change.
Review the blast radius
Compare against a Git baseline, separate added and modified files, and follow every transitive dependent before approving a change.
Find concentrated risk
Combine structural complexity, dependency pressure, code churn, and contributor activity into a prioritized maintenance view.
Put test gaps in context
Import Xcode result bundles, xccov JSON, or LCOV and see weak coverage beside the architecture it is meant to protect.
Read the whole system at once
Scan a compact dependency matrix for unexpected coupling, isolated modules, cycles, and relationships that do not fit the intended design.
Git-aware review
A diff tells you what changed. CodeAtlas shows what the change can reach.
Choose a branch, tag, or commit as the baseline. CodeAtlas overlays added and modified files on the architecture, then walks dependencies in both directions to expose upstream requirements and downstream blast radius.
- Baseline comparison
- Review the current working tree against any Git revision without leaving the app.
- Impact radius
- Traverse every transitive dependent, not only the first visible edge.
- Path finding
- Reveal the shortest architectural path between the selected symbol and a suspected consumer.
- Navigation memory
- Move back and forward through selections, or bookmark the nodes that matter to the review.
Deeper relationships, still build-free
Trace more than imports.
Optional call enrichment adds likely function relationships to the map while preserving the fast, source-first workflow. CodeAtlas also reports the semantic tooling already present on your Mac—including SourceKit-LSP, clangd, and compilation databases—so teams can see which deeper analysis paths are available.
Designed to be explicit: inferred calls are a fast beta signal, not a claim of compiler-exact resolution. You decide when to enable them.
Architecture as an executable agreement
Make intended boundaries visible.
Define lightweight layer rules and let CodeAtlas identify relationships that cross them. Cycle detection finds strongly connected areas that make systems difficult to separate, test, or replace.
Layer violations
Catch dependencies that contradict the direction your team intended.
Strong components
Surface groups that can no longer evolve independently.
Inspect in place
Select a finding and return to its files, symbols, and surrounding graph.
Prioritize where engineering attention pays back
Risk becomes a ranked, explainable signal.
Hotspots combine churn and contributor history with graph pressure. Coverage overlays add test evidence. Quality gates bring the signals together without hiding the ingredients behind a single opaque score.
Churn × structure
Rank files where frequent edits and dense dependencies make the cost of mistakes unusually high.
- Commit frequency
- Contributor activity
- Dependency pressure
- Structural complexity
Tests in context
Import existing reports and see weak coverage on the same map used to reason about architecture.
- .xcresult bundles
- xccov JSON
- LCOV
- File-level overlays
REVIEW
A decision, with evidence
Combine new risk, architectural findings, and available coverage into a CI-friendly review result.
- Readable summary
- SARIF findings
- Nonzero CI exit
- Configurable workflow
From the desktop to every pull request
The graph can join your CI.
Run the same local-first project analysis from the CodeAtlas command-line target. Export JSON for your own tools, emit SARIF for code-scanning interfaces, or install the included GitHub Actions template and fail a review when new risk crosses the gate.
CLIJSONSARIF 2.1GitHub Actions
zsh — code review
$ CodeAtlasCLI ./MyProject \
--baseline origin/main \
--sarif codeatlas.sarif \
--json-output codeatlas.json \
--fail-on-risk
Analyzed 186 files · 1,420 nodes · 4,968 relationships
Quality gate: REVIEW
3 architecture findings · 2 new high-risk filesBuilt for the investigation loop
Keep context while the code keeps moving.
Saved projects
Reopen recent security-scoped project folders directly from the welcome screen.
Live reanalysis
Optionally watch the project fingerprint and refresh the model as source files change.
Selection history
Navigate back and forward across an investigation without rebuilding your mental path.
Node bookmarks
Pin important files and symbols so the next question starts from known landmarks.
Search + filters
Narrow the graph by name, type, relationship, change state, or lens.
Portable exports
Share graph JSON, findings, and starter CI workflow files without sharing source.
What’s new in this release
From visualizer to architecture workspace.
The release opens with an in-app briefing and keeps these notes available from the CodeAtlas menu, so every new capability has a clear starting point.
Five workspaces
Map, Changes, Hotspots, Coverage, and Matrix turn one project model into purpose-built views.
Git context
Choose a baseline and inspect changed files, commit activity, contributors, and blast radius.
Impact paths
Trace dependencies, dependents, and the shortest route between important symbols.
Guardrails
Check layer direction and circular relationships before design drift becomes permanent.
Quality evidence
Rank hotspots, import coverage, and evaluate a transparent quality gate.
Automation
Run analysis from the CLI and export graph JSON, SARIF, or a GitHub Actions workflow.
Investigation tools
Return to recent projects, watch for changes, bookmark nodes, and revisit selection history.
Learning center
Eight guided tutorials live inside the app and remain available whenever you need a reset.
Tutorial center
Learn with the project already in front of you.
Open Tutorials from the CodeAtlas menu or Resources control. Each lesson explains the goal, the controls to use, and what to look for in your own graph.
See every lesson- 5 min
Take your first flight
Open a project, orbit the graph, use keyboard flight controls, search, and inspect a symbol.
- 7 min
Review a branch
Select a Git baseline and move from changed files to the dependencies each change can affect.
- 6 min
Trace impact
Follow direct and transitive dependents, then find the shortest path to a consumer.
- 8 min
Set architecture rules
Describe intended layers, read violations, and identify circular components.
- 6 min
Prioritize hotspots
Interpret churn, ownership, graph pressure, and complexity without treating a score as truth.
- 5 min
Overlay coverage
Import an Xcode or LCOV report and focus testing on risky, weakly protected code.
- 5 min
Enrich likely calls
Enable the beta option, distinguish inferred edges, and review toolchain readiness.
- 9 min
Add CodeAtlas to CI
Export the workflow, generate SARIF, and choose when new risk should block a pull request.
Support without a data handoff
Your code stays yours.
Project parsing, Git inspection, graph construction, coverage import, and exports run locally. CodeAtlas does not need an account or a source-code upload to explain your architecture.
Which projects can I open?
Select a repository or folder containing Swift, Objective-C, Objective-C++, C, C++, or Python source. CodeAtlas understands the common source and header extensions for those languages, and analysis does not require a successful build.
Does CodeAtlas change my repository?
Analysis is read-only. Exports are created only where you explicitly save them, and live reanalysis watches for changes without editing source.
Is call enrichment compiler-exact?
No. The optional inferred-call layer is labeled beta and is designed as an additional navigation signal. Toolchain readiness is reported separately.
Can my team use the results?
Yes. Export the graph as JSON, findings as SARIF, or a GitHub Actions starter workflow for repository automation.
Where do I get help?
Start in the in-app Tutorial Center, review the open-source project, or contact Orbitus Robotics for product support.
CodeAtlas for macOS
A codebase is a place.
Know where you’re going.
Explore the source today and follow the first Mac App Store release from Orbitus Robotics.