The entire point of self-hosting was to stop paying monthly subscriptions by running software on hardware you own, manage, and maintain yourself. That promise is collapsing as some of the most popular self-hosted applications now demand recurring monthly fees for features that execute entirely on customer-supplied infrastructure, turning the very tools people chose to escape subscription culture into another line item on the monthly budget.
Plex is the most visible example of how aggressively the shift is happening across the self-hosted landscape. The media server remains free for local streaming within your own network, but the moment you want to watch your own media remotely, Plex demands payment. Remote playback requires either a Plex Pass at $6.99 per month ($69.99 annually) or a separate Remote Watch Pass that covers only remote access. For users who previously bought the lifetime pass as a one-time escape from subscriptions, that door is now effectively closed. Plex tripled the lifetime price to $749.99 in July 2026, making the monthly subscription the realistic option for most new users.
Emby follows the same trajectory by charging $4.99 per month for hardware-accelerated transcoding, downloads, DVR functionality, and backup features. All of these capabilities run on the user’s own CPU, GPU, and storage. The software is not providing cloud compute or bandwidth for these features. It is simply unlocking functionality that executes on hardware the customer already paid for. Emby does still offer a $119 lifetime license, but the monthly option signals where the business model is heading across the entire self-hosted ecosystem.
The pattern now reaches well beyond media servers into categories where self-hosting once meant total financial independence from recurring payments. Bitwarden lets users deploy its password manager on their own servers, but the integrated authenticator, encrypted file attachments, emergency access controls, and security reports all sit behind a $19.80 annual paywall. Roon takes it further by requiring an active subscription just to operate Roon Server at all, tying the license to the account rather than to the machine that physically runs the software.
What makes these subscriptions particularly frustrating is the cost structure they impose on top of expenses users already absorb entirely on their own. Self-hosting requires purchasing server hardware, paying electricity bills, managing storage drives, configuring network infrastructure, maintaining security updates, and troubleshooting failures without a support team. Users accept all of that operational burden precisely because it eliminates dependency on monthly payments. Layering a subscription fee on top of that investment fundamentally contradicts the value proposition that drew people to self-hosting.
Not every project handles monetization this way, and the exceptions highlight how unnecessary the subscription approach really is for locally executed features. Home Assistant keeps its core application fully functional without any payment and only charges $6.50 per month for features that genuinely require developer-side infrastructure, specifically cloud remote access, cloud backups, and voice assistant integration. That distinction matters because those features create real recurring costs for the developer’s own servers. Immich sells one-time product keys at $25 for individuals and $100 for servers while keeping every feature accessible to unpaid users. Jellyfin provides media streaming, transcoding, remote access, and user management entirely for free with no subscription tier at all.
The self-hosting community now faces an uncomfortable question about whether the trend is reversible or whether it represents a permanent shift in how open-source and self-hosted software gets funded. Developers undeniably need revenue to maintain code, patch vulnerabilities, write documentation, and support growing user bases. But monthly subscriptions for features that never touch the developer’s infrastructure treat locally hosted software as a cloud service without providing any of the cloud’s convenience. One-time licenses, optional premium tiers, enterprise pricing, and donation-supported models all generate revenue without asking users to pay monthly rent on capabilities running inside their own homes.
