You’ve probably been using Gmail to send emails from your custom domain for years. It just works. You set up an alias, configure SMTP, and go about your day. No fuss, no extra fees. The email arrives from your address, through your domain, powered by the free Google infrastructure you’ve come to rely on.
Now Google is taking that away. In January 2027, the ability to send from third-party email addresses in the free version of Gmail will disappear. The official reason? “Disproportionate maintenance.”
Let’s pause right there. Because that’s not a technical explanation. It’s a lie dressed up as a practicality.
Here’s the part they don’t want you to notice: the exact same “send-as” functionality remains fully intact for Google Workspace customers. You know—the people who pay. So the feature isn’t too hard to maintain. It’s just not profitable enough to give away for free. One commenter on the announcement put it bluntly: “They claim disproportionate maintenance and yet state ‘and Google Workspace “Send as” functionality is not affected.’ Beyond retarded.”
That’s not a bug report. That’s a user reading the fine print and realizing they’re being played.
This isn’t just about email forwarding. It’s about the slow, quiet enclosure of the open web. The decentralized internet isn’t dying from a single regulation or a dramatic shutdown. It’s being starved to death by dominant platforms that decide, one feature at a time, that the open protocols they once supported are no longer worth the cost of maintaining for users who don’t pay.
Google isn’t just killing a feature—it’s closing the door on the decentralized internet, one email alias at a time.
Think about what this means for the non-profit student association running a self-hosted mail server. For the small business owner who uses a custom domain with free Gmail because they can’t afford $6 per user per month. For the freelancer who built their entire workflow around a simple alias. They now face a choice: pay Google, overhaul their setup, or abandon Gmail entirely.
Everyone who uses a custom domain with free Gmail is now a hostage. Google holds the key, and the ransom is a monthly subscription.
This is the pattern. First, it was free Google Apps accounts being forced to migrate to Workspace. Then it was the gradual removal of features from the free tier. Now it’s “send-as” from third-party addresses. Each step is framed as a technical necessity, but the pattern is unmistakable: free users are being squeezed out of the ecosystem, and the open web is losing a vital connection point.
I saw this firsthand when I helped a friend migrate his small business off free Gmail after they lost the ability to use custom domains. He wasn’t angry—he was resigned. “It’s their platform,” he said. “What can you do?” That resignation is the real danger. It’s the acceptance of a world where the only way to have a functional email setup is to pay a monopoly.
The twist here is that Google isn’t even the bad guy in the traditional sense. They’re just acting rationally—as a monopoly does. The real tragedy is that we’ve built our digital lives on platforms that can change the rules at any time, and we have no recourse. When the platform that controls your inbox decides you’re not profitable enough, you don’t get a vote.
So what do you do? Three options: pay Google Workspace, find an alternative email provider that respects open standards, or accept that your digital autonomy is slowly being eroded. There’s no fourth option where you get to keep the free, open internet you thought you had.
But here’s the thing: the death of the open web isn’t inevitable. It’s happening because we let it happen. Every time we accept a “maintenance” excuse without questioning why the same feature is still available for paying customers, we give away a little more of our freedom. The next time you see a feature being quietly removed from a free service, ask yourself: is this really about maintenance, or is it about enclosing the digital commons?
Because the answer will tell you everything about where we’re headed.
FAQ
Q: Is Google really killing the feature, or is it just a maintenance issue?
A: It's not a maintenance issue. The exact same 'send-as' functionality remains fully available for Google Workspace paying customers. The 'disproportionate maintenance' claim is a pretext to push free users into a paid subscription.
Q: What practical steps should I take if I use a custom domain with free Gmail?
A: You have three options: migrate to Google Workspace (paid), switch to a different email provider that supports custom domains (like ProtonMail, Fastmail, or Zoho), or reconfigure your setup to use a standalone email client that doesn't rely on Gmail's send-as feature. Act before January 2027.
Q: Isn't it reasonable for Google to charge for features that cost money to maintain?
A: That's a fair argument, but it ignores the context: Google built a massive free user base on the promise of open access, then slowly removed features to monetize them. The pattern is not about cost recovery—it's about platform lock-in. The real cost is the loss of digital autonomy for users who can't or won't pay.