this post was submitted on 20 Feb 2026
73 points (100.0% liked)

Selfhosted

61425 readers
577 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

This should be excellent for selfhosters that have all their services in one VM. I haven't tried this myself, but I think this means you can:

  • you can create memorable links instead of memorizing port numbers: jellyfin.foo-bar.ts.net
  • share one service from a machine instead of all of them in a more intuitive way

If you’re new to Tailscale Services, it lets you publish internal resources like databases, APIs, and web servers as named services in your tailnet, using stable MagicDNS names. Rather than connecting to individual machines, teams connect to logical services that automatically route traffic to healthy, available backends across your infrastructure. This decoupling makes migrations, scaling, and high availability far easier, without reconfiguring clients, rewriting access policies, or standing up load balancers. Our documentation has details on use cases, requirements, and implementation.

you are viewing a single comment's thread
view the rest of the comments
[–] avidamoeba@lemmy.ca 5 points 5 months ago* (last edited 5 months ago)

That's one way to look at it. I used to look at paid VC-funded services like that. I no longer do as I've observed services I paid good money for get more expensive much faster than inflation and decrease in quality and features at the same time. It's one reason I self-host many services I used to pay third parties for. I now look to alternatives from the get go and derisk existing dependencies. To be clear - profitability isn't merely the only problem. The ownership and its profit growth strategy (and expectations) are. Those are not the same in a decades old ISP and a VC-funded startup.

Merely being profitable today isn't a good predictor for stable prices and function over the long run for VC-funded services. I'm not planning to do major surgery to my setup every few years as yet another service shits the bed. The workstation/server where my self-hosted services run has last been reinstalled in 2014. Most of my config-as-code was written in 2019. I support a few families with this and I aim at maximum stability with minimal maintenance. So I use open source whenever I can and I often pay for development. I only integrated Tailscale in my setup because the clients are open source and because there's an open source server option.

I'm not saying to people - don't use Tailscale. In fact I often recommend it to new self-hosters. But I do that because there's a way out. So here I'm reminding people who care about a way out to check if this feature is escapable. :D