SaaS Lock-In Is More Than a Pricing Problem—It's a Daily Grind

I stumbled on this piece from misswaterfairy on Hacker News about the rising discontent with SaaS lock-in and pricing. It's a passionate critique—and it clearly struck a nerve, with 377 points and 224 comments. But as someone who spends way too much time thinking about the problems people actually report, I couldn't help but notice the article focuses on the big ideological battle and skips the everyday grind that's driving people crazy.

We don't collect data by survey or opinion poll. We listen to what people are actively complaining about—thousands of problem reports from developers, founders, and operators. And our data shows something more nuanced than "SaaS is evil." It shows a messy, frustrating, emotionally draining relationship with tools that are supposed to make life easier.

Let's start with the elephant in the room: subscription fatigue. It's not just about the total bill. It's the mental overhead of remembering which tool does what, who has access, when renewals hit, and whether you've actually logged into that $99/month analytics platform in the last quarter. We track problems that read like diary entries from burned-out ops people: "I have 14 SaaS subscriptions for a team of 5 and I don't know what half of them do anymore." That's not a pricing problem. That's a cognitive load problem. The article touches on cost, but misses the psychological weight of SaaS sprawl.

And then there's the data export nightmare. The article claims SaaS vendors can hold you hostage by making it hard to leave. Our data reinforces that, but the pain is worse than a hypothetical shutdown. People are hitting export friction every day, even when they're just trying to run a report or back up their data. One problem we track describes spending hours exporting CRM data into a usable format because the native export produced a jumbled CSV with broken relationships. Another mentions a project management tool that charges extra for API access to your own data. That's not "waiting for the vendor to die"—that's ongoing, active friction.

We're currently tracking 47 problems specifically related to data export and lock-in, with an average severity of 3.8 out of 5. That's high. For comparison, most problem categories hover around 3.2. People aren't just mildly annoyed; they're genuinely blocked.

But here's where the conversation gets interesting. The article waves the open-source flag, and our data shows real demand—8 separate app ideas in our database are requests for self-hosted, open-source replacements for popular SaaS tools. People don't just want to complain; they want to build alternatives. They're asking for an open-source Notion, an open-source Slack, an open-source Intercom. And they're not asking for ideological purity. They want practical features: data ownership, one-time payment, and the ability to run it on a $5 VPS.

Now, I have to push back on one point. The article implies that SaaS pricing inevitably becomes more expensive than self-hosting. That's an oversimplification. Our data tells a more complicated story. We see two camps: people furious about per-seat pricing that punishes growth, and people who tried self-hosting and got burned by maintenance, security patches, and the hidden cost of "just one more server." The total cost of ownership depends wildly on your team, your technical ability, and your willingness to be on call for your own tools. There's no universal answer—but that ambiguity is itself a signal. Builders who can offer a middle path—say, a single-tenant SaaS with transparent export and predictable pricing—might capture both camps.

The second point I'd challenge is the fear of vendor shutdown. The article paints it as the main data portability risk. In our data, shutdown anxiety exists, but it's not the top concern. The immediate, daily pain is the friction of moving data while the vendor is still alive and well. Proprietary formats, missing export features, rate-limited APIs, and "contact support to request a data dump" flows. That's the grind. And it's solvable without waiting for a company to die.

So where does that leave us? The OccupySaaS movement is right about the core problem: too many SaaS products treat your data as a moat and your wallet as a subscription. But the solution space is broader than "burn it all down and self-host." The real opportunity for builders—solo devs, indie hackers, agency folks—is to solve the micro-frictions that the manifesto glosses over. Build the subscription manager that actually syncs with your bank. Build the migration tool that turns proprietary exports into clean, open formats. Build the open-source alternative that doesn't feel like a downgrade. The demand is there, and it's not going away.

Because at the end of the day, people don't want to occupy SaaS. They just want their tools to stop making them feel tired.