I've been using Tailscale in a professional context for about eight months now, primarily to manage secure access for a small dev team across AWS and GCP projects. While the core functionality is excellent, I’ve increasingly found the admin console's information architecture somewhat non-intuitive.
My main point of friction is navigating between the high-level overview and granular policy details. For instance:
* The separation between **Access Controls** (ACLs) and **Policies** (which seem to encompass SSH and tag-based access) feels disjointed. I often find myself clicking through multiple sections to trace why a specific node or user has a particular level of access.
* The **Devices** list is clear, but linking device-specific settings (like tags) to the broader policy framework that governs them isn't always a linear path.
* As someone who deals with cost allocation, I wish the **Billing** and **User/Role** management sections were more directly integrated. Understanding which team's usage maps to which cost center requires cross-referencing several views.
I appreciate the power Tailscale provides, and I suspect this complexity stems from trying to serve both simple personal networks and complex organizational ones within a single interface. However, the mental model for org-wide settings—like authentication providers, device approval flows, and subnet routers—doesn't follow a consistent hierarchy.
Has anyone else experienced this, or developed workflows or documentation to navigate it more efficiently? I'm particularly interested in perspectives from others who manage multi-cloud environments. Perhaps I'm just not approaching it from the intended angle 🤔.
—A
Every dollar counts.
You've put your finger on a key friction point. That disjointed feeling between ACLs, Policies, and Devices creates real overhead. I've spent non trivial time myself auditing access, clicking back and forth to reconstruct the effective policy for a single device, which directly impacts security reviews.
Your mention of cost allocation is particularly resonant. In a cloud context, every resource needs a clear owner for chargeback. If you can't easily map a Tailscale tag or user group to a cost center, that creates a blind spot. You're forced to maintain a separate mapping document, which inevitably falls out of sync. I'd be curious if you've quantified the time spent on that cross referencing, as that's a direct administrative cost often overlooked.
The console feels like it evolved feature by feature without a unified information model for the administrator. For a tool built on simplicity, the management experience becomes ironically complex at scale.
CostCutter