Tanagram
Tools that give you confidence in complex codebases
Tools that give you confidence in complex codebases
You ever feel like your codebase is a little … spooky?
You ever feel like your codebase is a little … spooky?
There’s so much code. Millions of lines, ten folders deep; thousands of repos; half-a-dozen different languages. What does it all do? How much of it is ✨deprecated✨? It’s 3pm on a Thursday and you’re looking at a bugfix ticket, knowing in your heart that a user awaits a fix, but where do you begin? Maybe it's more complicated than it seems and you’ll still be working on it come sprint planning next week, and you don't have time for that, so you sheepishly close the ticket and hope that someone else will pick it up.
What could've been surprise-and-delight becomes another papercut.
You’re a senior engineer, a member of the technical staff, an architect. Your company promises five 9s to other companies your parents have heard of, and bears a heavy burden of reliability because you provide security, or financial infrastructure, or enable business-critical operations.
Big, important stuff.
But, day-to-day, you stare at a wall of text, an infinitesimally-small portal into the vast codebase. You try to figure out how things work from a mix of fallible memory, terse memoirs of long-departed founding engineers, yappy copilots, and the one staff engineer in your org who actually knows how things work.
Maybe you’re that staff engineer, and you are tired.
What you really want are better tools. A map of the codebase, labeled with entry points, abstraction layers, and related code you didn’t know existed. A list of all the tests that cover the code you’re changing, so you can just run 'em all and make sure you haven’t broken anything. A history of how a method came to be, and the people still around who’ve meaningfully touched it. And all that context would be nice when you have to review someone else’s changes too.
So that’s what we’re building at Tanagram — tools that give you confidence in complex codebases. I’d love to show you a demo:
There’s so much code. Millions of lines, ten folders deep; thousands of repos; half-a-dozen different languages. What does it all do? How much of it is ✨deprecated✨? It’s 3pm on a Thursday and you’re looking at a bugfix ticket, knowing in your heart that a user awaits a fix, but where do you begin? Maybe it's more complicated than it seems and you’ll still be working on it come sprint planning next week, and you don't have time for that, so you sheepishly close the ticket and hope that someone else will pick it up.
What could've been surprise-and-delight becomes another papercut.
You’re a senior engineer, a member of the technical staff, an architect. Your company promises five 9s to other companies your parents have heard of, and bears a heavy burden of reliability because you provide security, or financial infrastructure, or enable business-critical operations.
Big, important stuff.
But, day-to-day, you stare at a wall of text, an infinitesimally-small portal into the vast codebase. You try to figure out how things work from a mix of fallible memory, terse memoirs of long-departed founding engineers, yappy copilots, and the one staff engineer in your org who actually knows how things work.
Maybe you’re that staff engineer, and you are tired.
What you really want are better tools. A map of the codebase, labeled with entry points, abstraction layers, and related code you didn’t know existed. A list of all the tests that cover the code you’re changing, so you can just run 'em all and make sure you haven’t broken anything. A history of how a method came to be, and the people still around who’ve meaningfully touched it. And all that context would be nice when you have to review someone else’s changes too.
So that’s what we’re building at Tanagram — tools that give you confidence in complex codebases. I’d love to show you a demo:
We’re hard at work building Tanagram, but it’s not quite ready yet. If you’d like to have this at work; if these problems speak to your soul: add your email below 👇 and I’ll be in touch soon.
We’re hard at work building Tanagram, but it’s not quite ready yet. If you’d like to have this at work; if these problems speak to your soul: add your email below 👇 and I’ll be in touch soon.
P.S. I started Tanagram based on my 5-year experience as an engineer at Stripe building a new product from beta to global expansion. These are the tools I wish I’d had every day. We’re backed by Pear VC (PearX W25).
P.S. I started Tanagram based on my 5-year experience as an engineer at Stripe building a new product from beta to global expansion. These are the tools I wish I’d had every day. We’re backed by Pear VC (PearX W25).
© Tanagram, Inc. 2025