There has been a steady drumbeat of acquisitions in the developer-tooling space over the past couple of years, and another landed on my radar this month. I will not pretend I can recite the exact terms from memory, and I would rather be vague than invent a figure, but the shape is familiar: a tool I use most days, made by a small team I had come to trust, now belongs to a much larger company. The blog post had all the usual words. Excited. Journey. Nothing changes for existing users.
That last sentence is the one I have learned to read carefully, because it is true right up until the day it is not.
I am not reflexively against acquisitions. Small teams run out of runway, and a bigger backer can mean the thing I depend on actually survives, gets a security team, stops being one burnt-out maintainer away from disappearing. Some of the best-supported tools I use are the ones that found a home. So the announcement itself does not worry me. What I have learned to watch instead is the slower stuff that no press release mentions.
The first thing I look at is the pricing model, because that is usually where the change arrives first. A tool that was a flat licence has a way of becoming a per-seat subscription, then a per-seat subscription with a "Team" tier where the feature I actually use now lives. Nothing is taken away, exactly. It just quietly moves up a shelf I now have to pay to reach.
The second thing is the data. If the tool holds anything of mine, configuration, history, the artefacts of months of work, I want to know I can get it out in a format I can use elsewhere. The single most reassuring thing a newly-acquired tool can do is keep its export working and its file format open. The least reassuring is a roadmap that talks about "deeper integration" with the parent company's ecosystem, which is often a polite way of describing a one-way door.
So this week I did the unglamorous thing. I checked that my export still worked and stashed a copy. I noted which features I would actually miss if they moved behind a paywall, and which I could live without. And I had a quiet look at what the alternatives are now, not because I am leaving, but because the cost of finding out is far lower today, while I am calm, than it will be the morning a migration is forced on me.
Maybe nothing changes for years. Maybe the team gets the resources to make the tool better than it ever was on its own. I genuinely hope so, because I like it and I do not want to move. But I have been burned enough times to treat "nothing changes for existing users" as the start of a countdown rather than a promise. The tool has not changed today. My relationship to it has, slightly, and the sensible response is not outrage. It is to make sure that whatever happens next, I am holding my own data and I know where the exits are.