RIP ElfVPN
ElfVPN was a shared VPN which allowed the torrent clients (Deluge, qBittorrent, rutorrent) to be evaluated / used without having to bolt-on a BYO VPN subscription.
Shortly after we ramped up our test users from r/seedboxes, the VPS which ran ElfVPN was terminated by the provider for DMCA abuse.
After some consideration (details below), I've decided not to replace it, and instead withdrawn the ElfVPN products from the store.
TL;DR - From now on, in order to use the torrent clients, you will need to BYO VPN...
What will happen to existing subscriptions?
Because the product has been withdrawn from the store, it won't be included on your next (daily) subscription renewal. Please subscribe to one of the BYOVPN torrent clients instead.
Don't see your VPN provider? We can add it!
If you don't see your particular VPN provider, create an #elf-help ticket, and we should be able to add it for you. Typically any OpenVPN or Wireguard VPNs will work, but OpenVPN is priced higher due to its higher CPU requirements.
What if I don't want to BYO VPN?
There are other options besides torrenting. We have NZB apps (NZBget and SABnzbd), as well as RDTClient for Premiumize/Debrid support.
But why?
Here are the reasons:
Limit drive-bys
While I want new users to try out the ElfHosted services, what I don't want, is to provide "free torrenting" to users who have no intention of sticking around, or just want to use up their $10 free ElfBuckz, and move on. Requiring a VPN in order to use torrent apps hopefully filters out some of this behaviour, since you'd need to have already invested in a VPN in order to use them (which aligns with our target torrent users).
BYO FTW
Stick with the BYO philosophy
I'm liking the BYO philosophy (especially for storage) because it reduces the amount of responsibilty I feel for continuity of access to media. Seedplicity basically ran for 2 months after the shutdown announcement, simply to allow users time to offload their media. ElfHosted is built-in-public rapid prototype, and I hope it'll be sustainable long-term, but I want users to be able to pick up and leave with their data (and VPN config!) without any dependency on me.
(This might end up being a standalone blog post)
Reduces cost and liability
Finally, running a VPN-terminating VPS obviously comes with a cost, which I can now avoid. I'm also wary of any perceived responsibilty for the actions of torrent users, and I felt that permitting the torrenting traffic through a VPN I own and manage would indicate implicit approval.
As soon as we loaded up on users, the throughput rate of ElfVPN suffered. Running BYOVPN will result in a much improved user experience.
Other changes
Improvementz
It turns out our nodes (Intel i9-9900K) support QuickSync, so some #elf-a-testers are testing hardware transcoding in the streamers (Jellyfin, Emby, Plex). If you want to help test, hit me up to temporarily switch you to the alpha channel! 
- Feedback on the biometric / passkey logins has been positive, but there was a conflict between the original email verification flow, and the OwnID enrollment flow. I've removed the old 'verify your email' plugin, and enforced the OwnID login flow, since this ensures a user has a valid email anyway.
- Refactored the process which removes a user's "24h" orders, which wasn't working well. 24h app termination should now work correctly, and I'm working on the related storage cleanup flow. Effectively, after your app expires / fails to resubscribe, we'll hang onto the app data for
x days, and then delete it - Removed the troublesome Longhorn, which was not scaling well and contributing to node load.
Upcoming
Summary
Thanks for building with us - stay tuned!