Or always use tools that you have complete access to, i.e. that run entirely on equipment you own.

I think that ship has sailed. The entire world runs on SaaS tools which cannot / do not run locally. For mission critical ops, it can make sense to pay the enormous premium for local tools, but when one runs the risk/impact calculation, it rarely makes sense. Especially when there are four 9s attached to most of these online services.

	▲	awsglkhj a day ago \| parent \| next [-]
		> The entire world runs on SaaS tools which cannot / do not run locally. Some of us have made different choices and therefore have different exposure to these kinds of failures. Yes, sometimes those choices mean higher costs or fewer features, but a lower probability of getting kneecapped by others' problems is a pretty good feature. Life is tradeoffs.
	▲	toss1 a day ago \| parent \| prev [-]
		That ship is still very much available for boarding, but if your not already on it, it will take a bit of effort to get onboard. Many of us refused to go along with the subscription model, and so are not affected. I've used primarily LibreOffice for ~two decades, and even more emphatically when Excel became primarily Subscription. Stuck with Gimp even after buying Photoshop for the Pantone support, but killed PS when it went online model. Was very interested in Fusion 360, but stuck with RhinoCAD when Fusion was online-only. I refuse to use online accounting/payroll "solutions". I use Claude $20/mth a good amount, and am hesitant to use Chinese technology, but the last day makes it look a lot more sensible to setup local AIs, even at the cost of higher initial cost, lower capability, more system management effort, and potential compromise. It's just one small shop, but many others could make similar decisions, instead of going with what's "just easier today".