Memor turns TypeScript and JavaScript codebases into architecture, flow, and impact you can actually see.
For fifty years, we've looked at software through files and folders. A metaphor borrowed from filing cabinets. From paper.
But software isn't documents in drawers. Software is a living system. It has organs. It has circulation. It has pressure points where one touch sends shockwaves through the whole body.
We keep trying to understand it by reading — scrolling through thousands of lines, tracing imports by hand, sketching boxes on whiteboards that go stale by lunch.
What if you could just see it?
Memor doesn't generate documentation. It doesn't summarize your code with an LLM. It does something different.
It reads your codebase the way an architect reads a building — structurally. It finds the systems, traces the connections, maps the zones, detects the flows, and computes the blast radius of every piece.
Then it projects all of that into four interactive views you can see, navigate, and reason about. In your browser. In seconds.
The architecture was always there. Memor just makes it visible.
Same code in, same result out. No randomness, no probabilistic guessing, no LLM in the loop. You can trust what you see because it comes from what's actually there.
Your code never leaves your machine. No cloud, no accounts, no telemetry. Run it on an airplane, in a vault, on a desert island.
No setup files, no plugins, no project configuration. If it compiles, Memor reads it.
Files and folders are a storage metaphor from the 1970s. Memor thinks in systems, zones, and connections — the way your architecture actually works.
MIT licensed. The code is the documentation. Read it, fork it, break it, fix it.
Memor just lets you hear it.