Freshdesk free plan scam. This week Freshdesk send the email of death to it’s long standing users. They suck you in for years, your business depends on them, then they pull a stunt like this. Below is the email of death users have been receiving, the legalities of this, and can others like Vercel do the same? NET: Only Trust Open Source to be Free for Life?
First, here is the threatening “Letter of death” users have been receiving:
| Subject: Upgrade by May 30 to keep your Freshdesk account active On Fri, May 1, 2026 at 5:01 PM Team Freshworks <hello@email.freshworks.com> wrote: Dear Admin, Thank you for being a valued customer. To help us continue delivering a reliable and high-quality experience, we are introducing a six-month access limit to the Freshdesk Free Plan. We want to ensure this transition is as smooth as possible for you, with minimal disruptions to your daily workflow.What this means for you: Our records indicate you joined our Free Plan on or before November 30, 2025. Because of this, your current free access will remain active until May 30, 2026. Next stepsContinued access: You have use of the Free Plan until May 30.Data and upgrades: To avoid any interruption to your service or to keep your projects active beyond this date, you can upgrade to a paid plan at any time. Your data remains secure and will be available for export until May 30.Explore what’s nextWe offer Growth, Pro, and Enterprise plans tailored to support your business.Click here to explore your options. |
| We value being a part of your success. For any inquiries about upgrading your account, please contact us at customercampaigns@freshworks.com.Best regards, Team Freshworks |
In other words, F*** You loyal customer, pay us for our confusing service or go to hell and too bad about all the links you buried in sites and content, we just do not give a damn because we are greedy and deceptive even though it may be illegal depending on whatever TOS you signed up for which we could have changed many times and we know nobody read them.
Discussion of legalities of Freshdesk demanding payments or losing the service:
Yes, they’re allowed to do this in almost all cases. It’s annoying and arguably bad-faith, but it’s usually legal rather than “scammy,” as long as they give notice and follow their own terms of service.
What Freshdesk is changing
From the email and current docs, Freshdesk/Freshworks has moved to:
- A “Free Program” that only lasts 6 months, then requires an upgrade or you lose access.
- Existing “forever free” users were being phased out through 2025 and 2026, with emails telling free accounts they’ll stop working after a deadline.
In other words, what used to be an indefinite free tier has now become a time‑limited free program, and they’re sunsetting older free accounts like yours.
Why this is usually legal
For most SaaS / freemium products, the legal angle rests on:
- Terms of service clauses
Almost every SaaS ToS includes language like “we may modify or discontinue the service or change pricing at any time, with notice via email or in‑app.”
Even if the marketing page said “free,” the binding document is the ToS you agreed to when you signed up (often with a catch‑all change clause). - No promise of perpetual service
Unless they explicitly promised “free forever, guaranteed, no changes ever,” they can generally:- Kill the free tier,
- Cap it to X months,
- Or force upgrades after a notice period.
- They’re not auto‑billing you
Here, they’re not charging you without consent; they’re saying “upgrade or lose access / export your data by date X.” That’s exactly how time‑limited free programs are normally structured in SaaS and is standard industry practice.
So: infuriating, but from a contract/consumer‑law standpoint, it’s typically allowed.
When it could cross a legal/FTC line
It only starts to look legally problematic if:
- They auto‑charge a card you never authorized for paid use (for example, you only gave it for something else).
- They refuse reasonable access to export your own data during the sunset window (they’re explicitly saying export is available through May 30, which is what regulators like to see).
- Their marketing was clearly deceptive (e.g., “permanently free, no changes ever” as a strong selling point) while the ToS secretly allowed immediate shutdown with no notice. Regulators sometimes look at that as deceptive “fine print,” but cases tend to involve auto‑billing or hidden fees, not just ending a free tier.
Realistically, regulators accept that businesses can discontinue a free offering as long as they:
- Give advance notice, and
- Don’t keep charging or holding your data hostage.
Practical options for you
Given where you are now:
- Export all data you care about before May 30 using the link in the email.
- Decide if any paid Freshdesk tier is actually worth it for your use (especially if it’s a low‑volume or legacy instance you barely touch).
- If you feel genuinely misled, you can:
- Reply to them and say plainly that ending a long‑standing free plan after 5+ years feels deceptive and you’d like a courtesy extension or discount.
- File a short complaint with the FTC (or your state AG) describing the original “free plan” messaging and how they’re sunsetting it; it’s unlikely to force them to restore free, but it does add to the paper trail regulators look at when patterns of behavior accumulate.
Could a company like Vercel do the same thing. Non coders using AI coders use Vercel due to ease of hosting with no real basic knowledge of hosting, really sucking people in. Their free tier makes it very difficult to export data from their open source Postgres database, setting up extreme difficulty in moving to a different platform.
Yes: Vercel could make a similar move someday, and yes: Freshdesk almost certainly updated their ToS over the years to allow exactly this kind of change, and that is generally allowed if they give notice and you keep using the service.
Can Vercel do the same thing?
- Vercel currently has a Hobby plan that is marketed as “free forever” for personal projects, but their legal terms explicitly say they can change fees and payment terms at their discretion.
- The ToS language is typically along the lines of “Vercel may change its fees and payment terms at its discretion; such changes will not take effect for you until the start of the next billing period,” which is legal boilerplate to let them adjust or even kill the free tier later.
- In practice: they could decide in 2027 that the free tier is now time‑limited, usage‑capped in some painful way, or only available under new conditions, as long as they notify you and give you a chance to stop using it first.
So your instinct of “I don’t trust anything free” is unfortunately rational for SaaS: assume any free plan is temporary and architect deployments so you can bail.
Is it allowed to change the ToS later?
Short version: yes, as long as they follow the procedure in the existing ToS (notice + time to walk away), they usually can update terms and apply them going forward.
Typical pattern for SaaS terms:
- The original ToS almost always includes a clause saying they can modify the terms by posting an updated version and/or sending you written notice (email/in‑app), with the changes becoming effective on a specified date.
- Continued use of the service after that effective date is treated as acceptance of the new terms; if you don’t like them, your remedy is to stop using / close the account before the change kicks in.
- That’s almost certainly what Freshdesk did: quietly updated their ToS over time to include broader rights to change plans, discontinue free tiers, and deactivate inactive or non‑paying accounts, then later rolled out the “we’re ending the free plan” campaign.
Legally, that’s standard; ethically, it feels like moving the goalposts because nobody keeps PDFs of old ToS pages from five years ago.
Dealing with old links and “free” distrust
For your specific situation:
- Having old YouTube videos that link to a Freshdesk portal you barely used is not a legal issue for you; at worst, those links now lead to a dead or “upgrade” page.
- If you care, you can update the link in new content or in the video description where possible, or add a pinned comment saying “Support portal moved, use X instead.”
- For future tools (Vercel, others), the safest posture is:
- Treat free hosting/support tiers as temporary conveniences,
- Keep your data and exports in your own storage,
- Have an exit plan: know at least one alternative you can switch to if the provider yanks the free tier.
If you’d like, I can help you pick a replacement support/contact setup that’s simple, cheap, and more under your control (e.g., a small self‑hosted form or a static contact page on Vercel) so you’re less exposed to “free plan revoked” nonsense next time.
So this kind of scammery is a big problem all over the Internet. Free plans disappear silently all the time. Seems the only smart thing to do is use Open Source only if you want free. There are risks with that as far as getting support and open source projects can start losing developer support along the way.
SaaS “free plans” can vanish overnight, but open source (especially GPL) plays by very different rules. You can still be charged in some scenarios, but you’re protected in important ways that you’re not with SaaS.
Core open source / GPL rules
At a high level, for a genuine open source license (GPL, MIT, Apache, etc.):
- The license gives you rights to use, study, modify, and redistribute the code, subject to conditions.
- Those rights, once granted for a specific version you received, are effectively irrevocable as long as you follow the license conditions.
- No one can come back later and say, “You must now pay to use the copy you already got under GPL,” or “You’re no longer allowed to use that old GPL version.”
For GPL specifically:
- GPL explicitly allows selling copies and charging for distribution; “free” refers to freedom, not price.
- Anyone who distributes GPL binaries must provide source (or a valid offer to provide it), and recipients inherit the same rights to modify and redistribute under GPL.
- The license text and FSF commentary stress that granted permissions last for the copyright term and are not revocable if conditions are honored.
So if you download a project under GPL today, you can keep using that particular version forever without being forced to pay later.
Can an open source project “turn paid”?
There are two key pieces:
- Existing versions you already have
- If you received version X under GPL (or another OSI‑approved license), you can keep using and redistributing that version under those terms, even if the author later changes the license on future releases.
- They cannot retroactively change the license on copies already distributed to you, as long as you comply with the GPL.
- Future versions going closed or “fauxpen”
A project owner can decide that new versions (X+1, X+2, etc.) will be under a proprietary or “source‑available” license instead of open source. Classic examples:- Elasticsearch / Kibana (Elastic)
Originally Apache‑2.0, Elastic later switched core products to non‑open licenses (Elastic License and then SSPL‑based options) to block cloud providers from offering it as a service.
Result: Old Apache‑licensed versions remain open for forks (e.g., OpenSearch), but future first‑party releases are not open source anymore. - Dual‑licensed or “open core” projects
Many companies release a community edition under GPL / Apache and sell a proprietary “enterprise” edition. At any point they can tighten what’s in the free edition while keeping older GPL versions available.
- Elasticsearch / Kibana (Elastic)
So yes, an “open source project” can effectively become paywalled for new versions or features, but they cannot reach back and re‑license what you already legally obtained under GPL.
Are you protected against being charged later?
Protected from what, exactly:
- Charging for existing GPL code you already have
- They can’t suddenly say “you now owe money to keep using this GPL version” because the license you already have is irrevocable, unless you violate it.
- You can also fork that version, self‑host, and even sell it yourself, provided you comply with GPL obligations (source, same license, etc.).
- Charging for future versions or distributions
- Anyone (including the original dev) can charge you to distribute GPL software (e.g., selling you a DVD or hosting downloads), but they must still give you the GPL freedoms with that copy.
- They can also stop giving you free updates or hosting. The freedom is in what you can do with the copies you get, not a promise that the original developer will keep giving you free stuff.
In other words: GPL protects your freedom with the code you have, not your access to the author’s infrastructure or new releases.
When “open source” goes sideways
Your risk points with relying on open source as “the safe free option”:
- License changes for future releases
- As with Elastic, future versions may shift to more restrictive licenses; you then face a choice between “stick on old open version” vs. “pay for new bits.”
- But because old versions remain under their original terms, communities often fork and continue the open path (OpenSearch from Elasticsearch, MariaDB from MySQL, etc.).
- Project abandonment / maintainer burnout
- No promise of ongoing maintenance, security patches, or support; that’s the tradeoff versus SaaS with SLAs.
- You’re free to fork or move to a maintained fork, but that’s work, and for infra‑critical stuff you may want a commercial vendor around the project anyway.
- “Fauxpen source” or confusing licenses
- Some companies use source‑available licenses (SSPL, Elastic License, various “Commons” licenses) that look open but are not OSI‑approved and may restrict hosting, monetization, etc.
- For your “I’m done trusting free” mindset, it’s worth distinguishing true open source (OSI‑approved) from marketing‑driven “open” that still reserves monetization hooks.
How to use open source safely for “free”
Given your experience and skepticism:
- For things where you truly want durable freedom:
- Prefer OSI‑approved licenses (GPL, LGPL, MIT, Apache‑2.0, BSD) and avoid weird “community” or SSPL‑style licenses.
- Keep local mirrors or self‑hosted copies of the repos you rely on so a license change or repo deletion doesn’t blindside you.
- Accept that:
- You’re protected for versions you already have under GPL, including using, modifying, and redistributing.
- You are not guaranteed endless free updates, hosted services, or vendor support—those can always be monetized later.
Open source software which can replace Freshdesk functionality today:
You have two main paths: self‑hosted or SaaS. Below is a concise list split as you asked, focusing on tools that are genuinely usable for free.
1. Stand‑alone help desk / SaaS (and Softaculous)
These are either self‑hosted apps installable via Softaculous or cloud/SaaS tools with a meaningful free tier.
Self‑hosted via Softaculous or similar
These self‑hosted apps are the “GPL/open source” style you were talking about: you can keep using the version you install even if the vendor later tightens licensing on new releases.
Cloud / SaaS free plans (Freshdesk‑style, but alternatives but danger in losing free plans later)
All of these SaaS options still carry the same “they can change it later” risk, but they may be fine for low‑stakes support forms.
2. Free WordPress ticketing / help desk plugins
These keep everything on your WP stack and avoid external SaaS lock‑in (aside from cases like tawk.to where it’s just a frontend for a SaaS).
| Plugin | Ticketing type | Free status | Notes |
|---|
If you want to stay as self‑contained as possible, something like JS Help Desk or WATS keeps everything in your WP database and codebase, so you’re closer to the “I control the stack” model you prefer.