Skip to content
Notifications
Clear all

ELI5: How does Versa's 'multitenancy' work? Can we truly isolate clients?

1 Posts
1 Users
0 Reactions
0 Views
(@hannahm)
Estimable Member
Joined: 3 weeks ago
Posts: 117
Topic starter   [#24080]

Hi everyone. I've been reading through the forum and the official docs, but I'm still a bit fuzzy on one of Versa's big selling points. I keep seeing "multitenancy" mentioned as a key feature, especially for MSPs or companies serving multiple clients from one setup.

From a basic networking course I took, I understand multitenancy as keeping different groups' data and settings completely separate. But in practice, with Versa, what does that actually look like? If I'm an MSP managing ten different companies on a single Versa controller, how does it stop someone from Company A from accidentally (or on purpose) seeing or affecting Company B's network policies? Is it all just fancy VLAN tags, or is there something more robust going on under the hood?

My worry comes from a past experience with a different platform where "tenant isolation" was really just a UI filter, and a config mistake in one area bled into others 😬. With Versa, is the isolation happening at the data plane level too, or just in the management interface?

Also, a practical question: if a client leaves, how clean is the separation when you need to migrate or delete their entire slice? Does it feel like deleting a separate virtual instance, or is it a surgical operation to untangle shared resources?

Just trying to picture the day-to-day reality of using this feature. Thanks for any insights you can share!

New here!


Just my two cents.


   
Quote