Our story
Built by engineers
who lived the problem.
Buildpathio was founded in Austin in 2021 by James Whitfield and Priya Menon — two platform engineers who had each spent years watching the same incident pattern repeat: a renamed field, an undocumented consumer, a 2am page. They built Buildpathio to make that pattern impossible.
Our origin
The incident that started it all.
In 2020, James was the platform engineering lead at a growing logistics software company in Austin running 60+ microservices across seven squads. A payments team renamed a field in their core API, updated the OpenAPI spec, bumped the version, and opened a PR. The PR passed all tests — because the tests only covered their service. Three downstream consumers silently broke in production. The incident cost four hours of customer-impacting downtime. The postmortem listed "lack of dependency visibility" as root cause — for the third consecutive quarter.
That was the moment. James called Priya, who was running platform infrastructure at a separate company and dealing with the same problem in a different form. By early 2021 they had a working prototype. Buildpathio has been bootstrapped and independent ever since.
The team
Six people. One problem.
Previously platform engineering lead at a logistics software company in Austin, where he spent three years maintaining a 60-service mesh and watching the same dependency incident repeat quarterly. Co-founded Buildpathio in 2021 to make that incident pattern structurally impossible.
Led platform infrastructure at a developer tools company before co-founding Buildpathio. Designed the static graph engine that parses OpenAPI, AsyncAPI, and proto schemas to build the dependency graph without runtime instrumentation.
Previously senior backend engineer at a cloud infrastructure company. Leads the core product engineering team and owns the CI integration layer — the GitHub and GitLab check actions that surface impact analysis in PR review.
Spent five years designing developer tooling interfaces before joining Buildpathio. Responsible for the dependency graph visualization and the dashboard that makes a complex directed graph readable to an on-call engineer at 2am.
Previously on the platform team at a fintech infrastructure company where he owned the internal service mesh. At Buildpathio he works on the schema parser and the risk scoring engine — the core analysis that classifies changes as zero-impact, warning, or breaking.
Runs the engineering community side of Buildpathio — documentation, technical content, and the onboarding experience for new teams. Previously developer advocate at a distributed systems tooling company. Maintains the blog and the public changelog.
How we work
What matters to us.
Bias for platform engineers
Every decision is made by asking: does this make life better for the person maintaining a 50+ service platform? Not the manager, not the CISO, not the CFO. The engineer staring at the dependency graph at 11pm.
Transparency in the product and the company
We publish our changelog publicly, including fixes. Our pricing is on the website. We are bootstrapped and intend to stay that way — we grow when our customers benefit, not when a funding cycle demands it.
No lock-in
Your dependency graph is always exportable via the REST API. If you leave, you leave with your data. We want you to stay because the tool is valuable, not because switching is painful.