Every engineering team deserves a complete, living map of the systems they build.Today, understanding a complex codebase means piecing together tribal knowledge, outdated docs, and scattered diagrams. Engineers spend more time figuring out how things are connected than actually building. When someone leaves, critical context walks out the door with them.
We think that's broken.
We're building a world where system understanding is automatic.
Opentrace exists to close the gap between what your systems actually look like and what your team knows about them. Not through documentation that someone has to maintain — but through intelligent, continuous analysis that keeps pace with your code as it evolves.
Where we're headed
We started with the knowledge graph — a single source of truth that maps the relationships across your code, services, and infrastructure. But that's just the foundation. Our goal is to make that knowledge actionable. We want engineers to ask natural questions about their architecture and get real answers. To see the blast radius of a change before they make it. To onboard in days, not months. To turn institutional knowledge into something that belongs to the team, not individuals.
The future we're building toward
Software systems will only get more complex. Teams will only get more distributed. The organisations that thrive will be the ones where understanding isn't a bottleneck — it's a given.
That's what we're working on.
