Early January, and the acquisition announcements are doing their usual post-holiday thing. One of them landed on a tool I use every day, a small piece of infrastructure software that's been quietly excellent for years, now joining a much larger company's portfolio. The blog post said all the usual words. Nothing changes for existing users. Continued investment. Excited about the journey. You've read it; I've read it; we all know how to translate it.
I want to be fair, because the cynicism here is too easy. Sometimes an acquisition is genuinely good for a tool. The maintainers get paid properly, the bus factor of one becomes a team, the thing that was a side project becomes someone's actual job. I've seen that happen. I've also seen the other version, where the interesting part gets folded into a platform you didn't want and the standalone tool is "sunset" eighteen months later with a migration guide nobody asked for.
The honest thing is that I can't tell yet which one this is, and neither can anyone confidently posting hot takes about it. So instead of predicting, I did the boring exercise: what would actually break for me, and how exposed am I?
The answer was reassuring and slightly embarrassing. I rely on this tool more than I'd realised. It's wired into my build, my deploy, and a couple of scripts I haven't looked at in a year. If it disappeared tomorrow I'd be fine, but it'd cost me a tedious week. That's not a disaster. It's also not the position you want to discover you're in via someone else's press release.
So the acquisition didn't change my tooling. It changed my homework. I spent an hour checking the licence I actually agreed to, confirming the file formats are open and that I can get my data out without the application's blessing, and noting whether there's a credible alternative I could move to if the worst happened. There was, in this case, which immediately lowered my blood pressure. A tool you can leave is a tool you can relax about.
The wider point, and the only durable one, is that the acquisition didn't introduce the risk. The risk was always there. I'd just stopped noticing it because the thing worked so well for so long. Every dependency you don't control is a small bet that the people who do control it will keep caring about it the way you do, and a press release is just the day the bet becomes visible.
I'll keep using it. It's still good this week, and it'll probably still be good next month. But I've written down the exit, which is the most useful thing any of these announcements ever prompts me to do. Best case, the new owners do right by it and I never open that note again. Worst case, I read it once, calmly, on a Tuesday, instead of in a panic.