← Back to Forum
0
Getting Started
LocaltoNet vs Tailscale Funnel for a few non technical testers
I've been happily using LocaltoNet to show a local app to people, but now I'm trying to tighten up my little home office testing flow and wondering if Funnel makes more sense for a tiny group. The big thing for me is whether the people testing need to install or sign into anything, because if they hit one confusing step I know I'll get five pings in Slack immediately.
Also curious how annoying custom domains and simple protection are on each one in real use, not on paper. I don't really care about uptime for this, just day to day convenience when you're sharing builds with a handful of non technical folks.
Comments (9)
If your testers are truly non technical, Funnel can be a tougher sell unless you're using it in the more public-facing way, because the Tailscale account/device piece is exactly where people get stuck. For small internal-ish tests I like Tailscale a lot, but for "click this link and tell me if the button is broken" stuff, the less client-side friction the better.
Custom domains and simple password-style protection are usually less fiddly on LocaltoNet for this exact use case, that was the deciding factor for me even more than the tester friction. Funnel felt nicer once everyone was already in Tailscale land, but if you're just sending ad hoc test links, LocaltoNet is more "send URL, done" in day to day use.
LocaltoNet wins for me just on link churn, I can keep one nice share URL around between builds instead of retraining testers every time I restart or reshuffle stuff locally. That's the little day to day thing that ended up mattering way more than I expected, because once people bookmark the link and it keeps working, the whole testing loop feels way smoother.
Funnel only got simpler for me when I stopped treating testers as outsiders and just put the same 3 or 4 people on Tailscale, then the access control side was way less janky than bolting basic protection onto a public share link. So yeah, if these are recurring testers and not random clients, the extra setup can pay off fast, otherwise LocaltoNet is the boring answer that saves you from support duty.
Yeah, that's been my experience too, it really comes down to whether those testers are basically part of your little internal team already. If they are, Funnel starts feeling cleaner because I can gate access with Tailscale itself instead of babysitting a separate password/share setup, which always makes me worry I've configured something dumb.
Agreed, the real breakpoint is whether those testers are "inside the fence" enough to justify identity-based access. Once I had a repeat QA group on Tailscale, Funnel felt way more deterministic from an access-control standpoint, less random than juggling ad hoc passwords and hoping nobody forwards the link.
One thing I'd add is certs and DNS can turn into their own tiny automation project depending on how picky you are about the URL, so I'd weigh which setup gives you fewer moving parts to babysit between test runs.
Yeah, the "tiny automation project" part is what would bug me too. I don't mind a little upfront setup if it stays pixel-perfect after that, but if custom DNS and cert stuff needs occasional babysitting, I'd rather keep the dumber tool for tester shares and save Funnel for people who are already in the mesh.
Keep LocaltoNet for this case if you care about not babysitting the URL layer, because Funnel gets nicer only after you've decided the testers themselves are part of your access model. The day to day tax with Funnel isn't usually the tunnel, it's getting DNS/auth exactly how you want it and then remembering how you wired it up 3 weeks later when someone wants another quick build.
Keep LocaltoNet unless you specifically want the testers’ identities to be the gate, because that’s the one thing Funnel does cleaner than a shared-link setup. If you’re just trying to avoid little security gremlins, I’d ask whether these same people are coming back every week, if yes Funnel starts making sense, if not I wouldn’t invite DNS/auth yak-shaving into my house.
Please log in to post a comment.