Should software subscriptions be required to disclose a sunset date?

[DeanAmbrose11]

Curious what people think, should companies selling ongoing software subscriptions be legally required to disclose some kind of end of life or sunset timeline upfront, the way some physical products now have to disclose expected support windows

[Matt_81]

Genuinely think this should be standard practice, paying monthly for something with zero visibility into how long it'll actually be supported feels like a real information imbalance favoring the company

[Donna48]

Hard to enforce in practice though, a company's own honest answer at signup time might just be we don't know yet, priorities change and committing to a firm date creates its own liability

[Drift Vector]

Even a rough support tier system, like guaranteed for at least 3 years versus no commitment, would be more useful than nothing at all

[Anvil33]

This matters way more for software tied to physical hardware specifically, a subscription service can pivot but a smart device that stops working because the app got killed is a much bigger problem

[Quiet Depot]

I'd settle for just a clear policy on data export and notice period before shutdown rather than a firm date, at least that protects you from losing everything overnight

[SilverSurfer51]

A sunset disclosure sounds great in theory, but software lifecycles are messy in practice.

A company might plan for 5 years and then pivot in year 2 because the market shifts. Locking them into a declared date could either scare users unnecessarily or become meaningless boilerplate.

That said, a minimum support guarantee feels reasonable. Something like "we commit to security updates for X years" would already be a big improvement.

It's similar to how hardware warranties signal confidence without freezing the future.

Right now the problem is less about uncertainty and more about total opacity

[TheRock96]

There's a middle ground here that doesn't get enough attention: tiered commitments.

Instead of a fixed sunset date, companies could declare something like "full support," "maintenance only," and "end of life" phases with estimated timelines.

Microsoft has done this for years with Windows and enterprise products, and it works well enough for planning.

Users don't need exact dates, they need predictability.

A vague roadmap beats radio silence every time.

[Glenn]

Part of me wants this purely out of spite for services that vanish overnight

Nothing like paying monthly for something and then getting a "we're shutting down in 30 days" email.

Even a soft commitment would force companies to think twice before pulling the plug abruptly.

On the flip side, startups would probably just slap "no guaranteed lifespan" on everything and call it a day.

So regulation might help, but only if it has teeth.

[Anvil33]

Not sure a sunset date is the right metric.

Software doesn't age like a product on a shelf. Some tools last decades, others get replaced in a year.

What matters more is exit planning. Can you export your data? Is there a migration path? Are formats open?

A service with no sunset date but great portability is less risky than one with a clear end date but locked-in data.

That's where regulation could be more impactful.

[Klingon]

A required "minimum viable lifespan" would probably be the cleanest solution.

Say, if you sell subscriptions, you must guarantee at least 2-3 years of continued service or provide refunds if you shut down early.

That aligns incentives without forcing companies to predict the distant future.

It also protects customers from the worst-case scenario of paying for something that disappears quickly.

Feels like consumer protection 101 rather than overreach.

[Violet Dean]

There's also a psychological angle. Seeing a sunset date might make people avoid perfectly good software.

Imagine buying a tool labeled "supported until 2029." Even if that's far away, it suddenly feels temporary.

Meanwhile, unlabeled software gives the illusion of permanence, even if it's not real.

So disclosure could unintentionally hurt adoption.

Humans are weird about timelines

[James78]

One practical issue: enforcement across regions.

A company might comply in the EU or UK but not elsewhere, leading to fragmented policies.

Users would then have different expectations depending on where they live.

We've already seen this with privacy laws.

So any rule like this would need fairly broad adoption to avoid becoming confusing.

[Theo50]

From a developer perspective, committing to a sunset date early could be risky.

Roadmaps change, funding changes, entire companies pivot.

A bad estimate could either lock you in or damage trust when you inevitably revise it.

That might discourage smaller teams from even offering subscriptions.

And those smaller teams are often where innovation happens.

[Kieran88]

Would love to see refunds tied to shutdown timelines.

If a service closes within X months of your subscription, you get partial money back automatically.

That creates a financial incentive not to overpromise or shut down abruptly.

It's also easier to enforce than predicting future dates.

Follow the money, fix the behavior

Users get protection without needing to interpret vague policies.

[Messi]

A lot of this comes down to trust signals.

Big companies can get away without sunset dates because people assume they'll stick around.

Smaller services don't have that luxury.

So ironically, the companies that would benefit most from clear commitments are the ones least able to guarantee them.

Bit of a catch-22.

[Buffer]

There's a case for labeling rather than strict rules.

Think of it like nutrition labels, but for software: support commitment, data portability, offline capability, and dependency risks.

Let users compare products more transparently.

Some will choose stability, others will gamble on newer tools.

Information beats guesswork.

[Leah_68]

Another angle is enterprise vs consumer expectations.

Businesses already demand SLAs, support windows, and lifecycle documentation.

Consumers rarely get that level of clarity.

Extending a lighter version of those standards to consumer SaaS could close that gap.

Doesn't need to be as complex, just more transparent.

Right now it's a bit of a guessing game, and that's where frustration builds.

[Layla93]

The comparison to SaaS vs physical ownership is doing a lot of work here.

When you bought boxed software, it didn't "sunset" in the same way. It just stopped getting updates but still ran.

Subscriptions flip that entirely. The vendor can turn off the lights.

That power imbalance is why people are asking for guarantees.

A sunset policy is really about restoring some sense of control.