At the weekend, team Undo joined hundreds of runners for Chariots of Fire, the Cambridge relay that's been raising money for good causes since 1992. Congratulations to everyone who ran 👏🏻 #ChariotsOfFire #Cambridge
Undo
Software Development
Cambridge, Cambridgeshire 5,482 followers
Providing runtime context for AI agents. Fully automated root-cause analysis on the world’s most complex codebases.
About us
Undo provides the runtime context that makes coding agents work on the most complex codebases. AI performance = model + context. Models are getting better all the time; context is now the bottleneck. On large, mission-critical codebases, agents can only solve around 40% of problems — they guess at runtime behavior because source code alone doesn't tell them what actually happened. Undo closes that gap. Undo produces a deterministic recording of program execution. Complete control-flow and dataflow, within and across every module. Coding agents query the recording to reason about dynamic behaviour the way they already reason about static code. The result: fully automated root-cause analysis, with engineers able to see exactly what agent-generated code did and why. Recordings are the antidote to hallucination. Thousands of developers at the world's most demanding software companies, including Nvidia, AWS, Bloomberg and Palo Alto Networks, rely on Undo to solve problems up to 100x faster, release on time, maintain stability at scale, and deliver better customer experiences. Undo is more than a tool. We partner with enterprise engineering teams through concierge onboarding, expert training, and dedicated support to deliver measurable impact within the first six months of deployment.
- Website
-
https://undo.io
External link for Undo
- Industry
- Software Development
- Company size
- 11-50 employees
- Headquarters
- Cambridge, Cambridgeshire
- Type
- Privately Held
- Founded
- 2012
- Specialties
- C/C++, Software Engineering, Software Development, Engineering Productivity, Developer Velocity, agentic debugging, ai debugging tools, ai code debugger, Runtime Context, Root-cause analysis, Runtime behavior, time travel debugging, time travel debugger, and Java
Locations
-
Primary
Get directions
Unit 21 Hope Street Yard
Hope Street
Cambridge, Cambridgeshire CB1 3NA, GB
-
Get directions
2 Embarcadero Center
Office 8-135
San Francisco, California 94111, US
-
Get directions
05-117
WeWork Forum, DLF Phase III
Gurugram, Haryana 122002, IN
Employees at Undo
Updates
-
We're #hiring a new Senior Customer Success Manager in Cambridge, England. Apply today or share this post with your network.
-
Whoops! When legacy defects escape because they were left lingering in the codebase...
⚠️ If you're responsible for a mission-critical engineering organisation, this should make you uncomfortable. On 8 September UK air traffic control went down, affecting around 200,000 passengers. The cause was a legacy software defect involving a timing interaction (effectively a race condition) with an exposure window of about 1 millisecond. The report from National Air Traffic Services (NATS) makes that sound like a very narrow window. It really isn’t. In computing terms, 1ms is huge. What I find frustrating about this is that we keep treating these incidents as exceptional. They aren’t. 💸 In 2023, NATS had another major software failure, that time triggered by a flight plan the system couldn’t process. That disruption reportedly cost ~ 65m in airline costs and £75m-£100m in total costs. Yet the investment required in software quality to prevent such incidents would have been a tiny fraction of that. Obviously most software failures don’t ground thousands of flights. But flaky tests, intermittent failures, race conditions and bugs that only appear under very particular circumstances in mission-critical systems happen all the time. And as an industry, I think we’ve become far too accepting of them. We know the drill. A test fails once. Someone reruns it and it passes. Fixing it properly means reproducing something that may only happen once in a thousand runs, so it gets put on the backlog. There’s always something more urgent to do. I understand why. Engineering time is expensive. Adding more test coverage takes time. Chasing intermittent failures can take days. And the return on fixing something that might cause a serious problem at some unknown point in the future is almost impossible to put on a spreadsheet. But we need to rethink that calculation. 🤖 The tools we have now are radically better. AI makes it much cheaper to generate more tests. Thread fuzzing can deliberately provoke these sorts of concurrency failures. We can record software execution when something fails rather than spending days trying to reproduce the failure. And AI agents can increasingly investigate those recordings and determine what actually happened. So the old argument that we can’t afford to chase every flaky test or difficult-to-reproduce failure is getting pretty weak. The cost of improving software quality in mission-critical environments is coming down dramatically. The cost of not doing it clearly isn’t.
-
-
Fully automated and verifiable root cause analysis, from dev through CI to production. On 29th September, Undo's CEO Greg Law and CTO Mark Williamson will share how they’re seeing AI agents deployed to automate root cause analysis on complex codebases. Sign up now ⬇️
Coding agents are helping teams ship more code, faster. But what happens when all that code fails? Join Undo’s CEO and CTO on the 29th of September to see how AI agents can fully automate root cause analysis - from dev and CI through to production.
How to Automate Root Cause Analysis with AI - in Dev, Test and Production
www.linkedin.com
-
Would it be CppCon, The C++ Conference without an Undo LEGO prize draw? Congratulations to this years winners: Ben Gonzalez, Benjamin Sherman, Floris Bob van Elzelingen, Yi-Cheng Tien, Sandor Dargo and Mike Shah. Here at CppCon? Check out Chris Croft-White and Mike Shah's talk "Code You Didn't Write: Understanding Large and Unfamiliar Codebases" tomorrow, Friday September 18, 13:30 - 14:30 (MDT)
-
-
Undo reposted this
CppCon, The C++ Conference this week, and the Undo booth is up in Colorado. I'm stateside, though I'm busy visiting users at Cadence, Siemens EDA (Siemens Digital Industries Software), Palo Alto Networks and AMD. Chris Croft-White, Colin Dowd, Sharon King-Livesey, Greg Law and Mark Williamson are at CppCon, and I'm already hearing great reports from it. CppCon is one of the few rooms where you're surrounded by exceptionally talented engineers working on genuinely hard codebases. It's such a good opportunity for us to understand some of the common issues engineers are facing, especially in this ever-changing world of AI. If you're there, go find the team and tell them Danni says hi 😆 While you're there, ask for a quick demo of Undo and sign up for the LEGO DeLorean raffle! #CppCon #cplusplus
-
-
Undo reposted this
What a fun and exciting week at DVCon India 2026. Great to meet some old friends and glad to make loads of new ones. Special thanks for my company Undo for giving me this opportunity. I participate in so many conferences but the warmth and hospitality at DVCon India 2026 was incredible. Everybody was so friendly and ready to cooperate. Nice to see the presence of teachers and student fraternity who are going to shape the future of the semiconductor industry. #aidebugging #dvconindia2026 #systemc
-
-
Last year at CppCon, The C++ Conference, Mark Williamson and Daisy Sophia Hollman debugged C++ live on the main stage. No slides, no safety net. 📺 https://lnkd.in/eqJhXPiz Twelve months later the question isn't "can an agent debug C++?" It's "what does an agent actually need in order to get it right?" That's what we're at CppCon 2026 to talk about. Two talks: 🎤 You're absolutely wrong! How to get agents to solve complex problems with complex code Tuesday 15th, 4.45pm — Mark Williamson and Greg Law 🎤 Code You Didn't Write: Understanding Large and Unfamiliar Codebases Friday 18th — Chris Croft-White and Mike Shah Plus: 🎤 Good boss, bad boss: how to be a good manager, and how to manage a bad one Tuesday 15th, 3.15pm — Greg Law We will also run poster sessions Sunday evening and Wednesday lunchtime, and the team will be on the exhibition floor Monday to Wednesday. Chris Croft-White, Colin Dowd, Mark Williamson and Greg Law will all be there. Come and say hello. #cpp #CppCon2026
-
-
Undo reposted this
Meet Undo at DVCon India 2026! Visit them at the booth and explore with the team. Undo #dvconindia #dvconindia2026
-
-
We're exhibiting at DVCon India 2026 Undo gives AI agents design-specific runtime context to quickly diagnose functional defects in simulation models. Want to find out more? Come and find Chirag Goyal and Rashmi Khetan at booth 29, September 1 to 3. #DVConIndia2026 #Semiconductor #DesignVerification #ChipDesign #DVCon
-