Volume 03
VR IDEs & Commercial Code Maps
What happens when someone tries to make money from "see the whole codebase": one VR IDE startup that nearly happened, one codebase-map product that got swallowed, a graph navigator that died and came back, and a row of enterprise architecture tools that draw boxes-with-arrows and call it a day.
The research prototypes in Volumes 01 and 02 mostly died of being theses. The tools here mostly died — or are dying, or got acquired — of being businesses, which is a different and in some ways harsher filter. A pattern runs through them: the closer a tool gets to rendering actual code at scale, the rarer it is; the more it stays at "boxes and arrows about the code," the more comfortably it survives. Volume 06 takes that up.
The VR IDE that almost happened
Primitive VR commercial zombie — site & Steam page up, development stalled
Primitive.io · founded ~2017 · raised a ~$1.1M seed, sought a Series A that didn't land · public feedback repo's last real activity ~2020; Steam app still listed "free for non-commercial use"
The most serious commercial attempt at a VR code IDE. Primitive ingested real Java / C# / C++ / JS codebases — "several million lines" — and rendered them as 3D architectural structures: call graphs you could walk through, multi-thread runtime animations, filename labels floating in space. It shipped IDE plugins for Visual Studio and JetBrains, sold org licenses, got the obligatory Road-to-VR write-up, and is cited by basically every academic VR-IDE paper as the commercial reference point.
And then it stalled. The site lingers, the Steam / Viveport / SideQuest listings linger, but the company is to all appearances dormant — not acquired, not shut down, just quietly out of runway. It also wasn't quite this thing, even at its peak: Primitive rendered architecture — graphs, blocks, labels — not the source text itself. The closest the commercial world got, and it both undershot the rendering ambition and ran out of money. Useful as a cautionary tale on both axes.
primitive.io · PRIMITIVE-IO/primitive · Road to VR write-up
Commercial codebase maps
CodeSee / CodeSee Maps 2D commercial acquired — standalone product gone
CodeSee · shut down Feb 22, 2024 · acquired by GitKraken May 14, 2024 · folded into the GitKraken DevEx platform
The polished commercial "code map" — auto-generated diagrams of how a codebase's pieces connect, with the signature "stadium of arrows" overview, code-review walkthroughs, the works. It was the closest thing to a productized codebase-cartography tool with real momentum, and then it announced its own shutdown in early 2024, got bought by GitKraken weeks later, and dissolved into their paid DevEx platform. codesee.io still resolves; the standalone product does not.
GitKraken acquisition announcement
CodeScene 2D dashboards commercial · free tier alive
Adam Tornhill / Empear → CodeScene · the commercial descendant of "Your Code as a Crime Scene" · free tier for individuals/small teams; paid from ~€18/mo per active author
Mature, actively sold, genuinely good — and not spatial. CodeScene mines git history for "behavioral" signals (hotspots = high churn × high complexity, knowledge maps colored by author, change coupling, code health trends, the "X-Ray" function-level drill-down) and renders them as 2D circle-packing diagrams and dashboards. It's the productized form of Tornhill's crime-scene tooling. Worth listing here precisely to mark the boundary: this is the state of the art in "make the whole codebase legible at a glance," and it does it in 2D, with circles, deliberately.
codescene.com
CAST Imaging 2D zoomable map enterprise alive
CAST Software · enterprise code cartography · handles systems up to ~60M LOC; AWS Marketplace listing
The big-enterprise answer to "we have sixty million lines and nobody understands them": a browser-based, zoomable interactive map that descends from UI layers through application logic to the database, with elements rendered as nodes and icons. It scales further than anything else here — but it renders the system as a diagram of components, not as source text. The "code cartography" name is doing a lot of work; it's a very good architecture map.
castsoftware.com/imaging
AppMap runtime maps alive · OSS
AppMap (getappmap) · open source, actively developed across Java / Python / Node agents · free; lives inside VS Code and JetBrains
Different category, included so the boundary is clear: AppMap records a program running and draws the resulting call sequences and dependency maps inside your editor. It's runtime-dynamic, not whole-repo-static — the map is "what executed during this test," not "what the codebase is." Genuinely useful, genuinely maintained, genuinely not the thing glyph3d-js does.
appmap.io · github.com/getappmap
CodeMR 2D dashboards commercial · crippled community edition
CodeMR · Eclipse + IntelliJ plugins (Java / Scala / Kotlin / C++) · alive, but the free edition caps at ~50 files / ~60 classes — effectively a demo
Static quality analysis with dependency and complexity dashboards. Listed mainly because it shows up in any "code visualization tools" search; the community edition is too small to use on a real project, and the paid edition still produces 2D dashboards, not a spatial scene.
codemr.co.uk
Architecture / dependency tools (boxes and arrows)
A whole product category exists for "show me the architecture, flag the violations." None of it renders source at scale; all of it is alive, because drawing a labeled box is cheap and managers will pay for the red arrow that means "you broke the layering."
| Tool | What it is | Renders source text? | Status |
|---|
| Structure101 | DSM & architecture diagrams; layering conformance | no | alive — acquired by Sonar, Oct 2024 |
| Lattix | dependency-structure-matrix architecture analysis | no | alive |
| NDepend | .NET dependency & metrics dashboards | no | alive |
| Teamscale (CQSE) | code intelligence; architecture-conformance view (green = allowed, red = violation) | no | alive |
Code-graph navigators
One step closer to the code: tools that index a whole codebase and let you walk its symbol graph, usually with a real source pane alongside a 2D graph. The graph isn't spatial in any load-bearing sense, but the text is real.
Sourcetrail renders text (in a pane) 2D graph dead upstream, alive in a fork
Coati Software → community forks · original archived Dec 14, 2021 (final release 2021.4.19) · the petermost/Sourcetrail fork shipped release 2025.12.8 — 3000+ commits, Clang/LLVM 20, Qt 6.9, VS 2026
The best-loved of the code-graph navigators: click a symbol, see its callers and callees as a graph on one side and the actual source on the other, for C/C++/Java/Python. Coati Software shut it down and open-sourced it in 2021; the living continuation is the petermost fork, which is genuinely maintained. Not spatial — but the closest thing to a polished, interactive, whole-codebase symbol explorer that still works, and a good reference for "what does navigating a real codebase's structure feel like when someone sweated the UX."
github.com/petermost/Sourcetrail · CoatiSoftware/Sourcetrail (archived)
CodeCompass renders text 2D alive
Ericsson + ELTE Budapest · ICSE / SANER tool track 2018 · actively maintained; used at industrial scale inside Ericsson
A web-based, server-backed codebase explorer for C/C++/Java/Python: full source with deep cross-references, call graphs, build-system views, version-control overlays. The layout is conventional (source pane + side panels + graph popups), not spatial — but it ingests genuinely huge codebases and it's one of the few tools here that an actual large company runs in anger.
github.com/Ericsson/CodeCompass
emerge 2D graph alive · OSS
Glenn Lasse Tews (glato) · latest release v2.0.7, July 2024 · MIT; pip install emerge-viz or Docker
Point it at a source directory in ~12 languages and it produces a browser-based, force-directed dependency graph plus metrics. Solid, small, maintained — and a graph, not a city or a text-scape. A reasonable "I just want to see the module structure" tool.
github.com/glato/emerge
Sourcegraph renders text (search results & file views) 2D alive · independent · well-funded
Sourcegraph · Code Search · Cody · Amp · independent (not acquired), substantial revenue
Worth a line only to confirm what you already assumed: Sourcegraph indexes enormous codebases and exposes that index as search results and file views and as fuel for AI tools. There is no map view, no spatial view, no city. The "code graph" is an internal data structure, not a thing you fly through. If you were wondering whether the biggest player in "understand a large codebase" had quietly built the spatial thing — they haven't.
sourcegraph.com
codemap.app · CodeAtlas · VS Code "Code Map" 2D assorted, mostly dormant
various small tools
The long tail of "call-graph in a sidebar": codemap.app (multi-language 2D call graphs, last visible activity around 2020/2024, treat as link-rot risk), CodeAtlas (old Sublime plugin riding on the Understand engine; a GitHub Action wrapper survives it), and the oleg-shilo.codemap VS Code extension (a lightweight per-file symbol outline — useful, but it's a file outline, not a codebase map). None of these scale to "the whole repo as one view"; all of them are worth a glance for UI ideas.
The power tool: Glamorous Toolkit & Moose
Glamorous Toolkit / Moose / Roassal renders text (as moldable objects) 2D alive — unusually active
feenk / the Pharo community · Pharo + Rust; "Bloc" rendering engine; Roassal visualization engine; "Moldable Development" · multiple releases a week; steep Smalltalk learning curve
The serious software-analysis platform you can actually download and point at a codebase today. Moose parses and models systems; Roassal draws the visualizations; Glamorous Toolkit wraps it all in a "moldable" environment where every object — including every chunk of source — gets bespoke, composable views, and the text editor itself was rebuilt (in Bloc) to carry attribute spans, cursor indexes, and live inline previews. It's genuinely powerful and genuinely alive.
It's also not a "whole repo, all at once, spatially" tool — it's per-object and analytical, it has known performance pain on very large text buffers, and it has no repo-scale text-wall view. The right way to file it: the closest thing to a peer on rich, programmable, annotated source, on a completely different axis from scale.
gtoolkit.com · moosetechnology.org · Roassal
The web IDEs — confirming the obvious
GitHub Codespaces · vscode.dev · Gitpod · CodeSandbox renders text (one file at a time) 2D alive
the "VS Code, but in a browser / in the cloud" category
You know all of these; this is here so the survey is complete. Every one of them is a remote or web build of VS Code (or an equivalent): file tree on the left, tabs across the top, one file open at a time. Zero whole-repo spatial rendering. Whatever else they do — and they do a lot — none of them competes with, or even gestures at, the thing in Volume 01. "Code on the web" turned out to mean "the editor, but somewhere else," not "the codebase, as a place."
Where this volume lands. The commercial filter is specific: the further a tool stays from rendering real code at scale, the better it survives. Boxes-and-arrows architecture tools — Structure101, Lattix, NDepend, Teamscale, CAST Imaging — are all alive and selling. CodeScene is alive having chosen 2D circles on purpose. Sourcetrail died and was resurrected by a volunteer. CodeSee was acquired and dissolved. Primitive aimed at VR and real codebases, undershot the rendering ambition, and ran out of money. No commercial tool renders an entire repo's source text spatially; the web IDEs settled for "the editor, elsewhere."
→ Volume 04: the hobbyist and generative end — ambition back, link rot severe.
Continue → 04 · Web Toys & Generative Art