November 23rd, 2024

How Tailscale's infra team stays small

Tailscale's three-engineer infrastructure team uses its product to simplify network management and security, employing ACLs for access control and an in-house tool for efficient secret management, allowing focus on complex challenges.

Read original articleLink Icon
How Tailscale's infra team stays small

Tailscale's infrastructure team, consisting of just three engineers, effectively manages its operations by utilizing its own product, which simplifies many security concerns. The team relies on Tailscale to create a programmable network layer that connects resources across various cloud providers without the complexities typically associated with network architecture. This approach allows them to avoid common networking issues, such as managing public and private endpoints, and enables seamless communication between services regardless of their hosting location. Additionally, Tailscale's configuration allows for straightforward access control management through ACLs, reducing the need for intricate security setups. The team also developed an in-house secret management tool, setec, which integrates with Tailscale, allowing for efficient management of access to sensitive information. This setup alleviates the burden of handling secrets and TLS certificates, as Tailscale automates key distribution and certificate management. Despite the small team size, Tailscale's infrastructure team remains busy tackling other challenges, indicating that their reliance on their product has significantly streamlined their operations.

- Tailscale's infrastructure team operates with only three engineers by using their own product.

- The team simplifies network management and security concerns through Tailscale's programmable network layer.

- Access control is managed via ACLs, reducing complexity in network architecture.

- An in-house secret management tool, setec, integrates with Tailscale for efficient access management.

- The team focuses on more complex problems, having alleviated common infrastructure challenges.

Link Icon 3 comments
By @notTooFarGone - 4 months
I love that they point out the massive added benefit of using your own products.

Dealing with software you kind of always see if the software is actually used by developers.

Too many times I'm pained with request that take for ever, asset management tools that just don't click or just mondboggling APIs that need 3 other APIs to function properly.

I think using your own products and iteration over internal feedback early and often is the way to a brilliant product and such cost efficiencies are a nice byproduct.

By @maayank - 4 months
> Establishing AWS identity outside of AWS is a headache, and often comes with a chicken-and-egg problem of needing to possess a secret to show you are allowed to get a secret.

> For most stuff here, we can rely on the fact that every connection over Tailscale is encrypted and authenticated to an identity

Mm, okay, but you still have the chicken and egg problem of distributing the creds to join your tailnet.

Isn’t it not that different than distributing aws creds to access secrets manager?

By @egnehots - 4 months
yeah, I wonder if there's room for a different networking abstraction that could address most of complex orgs networking issues, I, for sure, don't think that we should still think about cidr range limitations when making networks, for ex.

that said, I'm not sure the tailscale approach scales well in typical modern corporate environments, where you've got a small army of junior devops often overlooking security or cost implications (don't forget about egress costs!).

the traditional, meticulous approach of segmenting networks into VPCs, subnets, etc., with careful planning of auth, firewall rules and routes, helps limit the blast radius of mistakes.

tailscale's networking & security model feels simple and flat, which is great for usability, but it lacks the comforting "defense in depth" that will be asked in most big corps.