Podcast Appearances
There's ones that are more directly tied to the user identities.
So we've got some customers that have a staging tailnet and a testing tailnet.
User identity is a first class thing.
I believe those tracks of development will converge at some point.
But there's already some really incredible stuff you can do with multi-tailnets, for instance.
And that's one of the reasons I think things like Aperture and TSNet are so fascinating in that I could create a separate tailnet
and I can make sure that nothing can escape from that, and I can go off and do its thing, and I can run coding agents in YOLO mode.
I can have them connect to MCP servers, and I have permissions that can fly around inside of the network, and it's all nice and contained.
And you can use Tailscale for that kind of thing.
And those are the kinds of areas where I'm really excited for people to start experimenting with and bringing up ideas of just like, oh, if Tailscale did this for me, or if it let me export this kind of thing, or if it could transport this kind of policy, or if it could connect to these different things, then I could achieve X. And I want to hear more of those ideas so that we can start building more stuff and more features at the edge so that people can start using Tailscale more as a platform.
Did I say that earlier?
Yeah, I'm not.
Basically, yeah.
I mean, a lot of the stuff you can do with multi-tailnets, you can do with just modifying the policy file in a single tailnet.
If your rules are aggressive enough, for instance.
But there's definitely, there's a lot of people that were like, no, I don't want to mess around with a complex policy file.
It's too risky.
Or I'm dealing with multiple customers and my customers demand complete guarantees and isolation between them.
I don't want to be managing
Something where I accidentally add a star somewhere that all the customers can see each other, for instance.