Podcast Appearances
And so multi-tailnet is definitely, it facilitates that significantly.
A lot of it's just peace of mind.
Like, oh no, I have this particular tailnet, it's used exclusively for this.
It can't move laterally to a different tailnet.
They're completely isolated from each other.
So it gives a lot of people just peace of mind.
And frankly, it's like a divide and conquer kind of problem.
It's like, well, why have one big complex tail net when I can have two simple ones?
With the API-only tailnets, you get an OAuth client back.
And then with that OAuth client, you can do things like add nodes, create auth keys, provision stuff within that particular tailnet.
It is still tied with what you might call the primary tailnet.
It is associated with that.
But for all intents and purposes, it's a separate network.
One of the bigger issues that a lot of, especially larger companies that I've seen coming up more recently, is they have a traditional network, traditional VPN.
It's like one monolithic thing.
And they're trying to bring up MCP servers and they're trying to bring up MCP clients.
And they've got these notions of like, they basically are thinking like, oh, I've got now agents that are trying to operate inside of the network the same way humans used to, right?
Except, well, I don't need to go on about the dangers of sort of letting an agent run amok on an internal corporate network.
But it's becoming obviously more and more an issue for especially bigger organizations that have traditionally dealt with security from a very centralized, monolithic perspective.
So I think there's definitely been this push of just like, okay, well, how do we start segmenting or isolating or subdividing our network?