Zentitle Single Tenant vs Multi-Tenant
Zentitle infrastructure is offered in options suitable for your needs
What are Zentitle’s single-tenant and multi-tenant options?
Multi-tenant is Zentitle’s default: all customers run on a shared, auto-scaled cluster. Single-tenant spins up a dedicated instance reserved for one vendor, with its own data isolation and a choice of AWS availability zone.
Why a vendor might prefer single-tenant
Some vendors need data residency guarantees (e.g., GDPR in Frankfurt), complete data segregation, or business-continuity provisions that let them take over the instance under extreme circumstances. Single-tenant addresses those without giving up platform scalability.
How the trade-offs compare in practice
Both options share the TurboScale architecture, so performance is not a dividing line.
- Multi-tenant: shared infrastructure, managed entirely by Nalpeiron, lower cost
- Single-tenant: dedicated instance, chosen AWS AZ (e.g., Frankfurt), data-segregated
- Single-tenant contract includes instance-takeover provisions for continuity
- Both scale dynamically with TurboScale as customers grow
Who this video is for?
Infosec, compliance and procurement teams who need to understand the deployment options before approving Zentitle.
Video transcript
Auto-generated from the video and lightly edited for readability.
We offer our Zentitle infrastructure in one of a couple of different models. One is a multi tenant, that is our standard way of going to market.
And their multiple customers, all of the multi tenant customers are serviced through our common core managed infrastructure.
We also provide the option of spinning up a single tenant instance reserved specifically for you and your customers that can be managed on a dedicated basis. So what are some of the trade offs? Well, with multi tenant, you've got that common approach, you've got a large number of customers, large number of end users, all working together to, leverage that common infrastructure And with turbo scale, you can have confidence that that will scale up accordingly regardless of which individual vendors, their customers, etcetera, are causing demand. So even in that multi tenant environment, you still have great confidence that the system is gonna scale. That being said, if you'd like the independence of being on a single tenant instance, we can accommodate that as well.
We're using AWS for managing our infrastructure.
But within that single tenant, You have the ability to request a certain availability zone in AZ that you can choose for whatever reasons you may say, Hey, we want, to have an availability zone, based in Frankfurt, for example, so we can accommodate that. And that might perhaps give, lower latency, better performance to your European customers, or you may have, a request around GDPR or data protection issues where you'd like to manage that separately.
It also gives you the ability to have all your data managed independently from the rest of our customers. So some people would prefer that their data be segregated from their rest of our customers. And of course, it gives you that independence as well. So for example, if you have any concerns about ongoing sort of viability, for Nalpeiron as an organization, then we have a standard part of our single tenant contract the ability to take over that instance if, you know, some very unusual, you know, the thing happens to tune up here in And of course, even within that single tenant environment, you continue to have the benefit of our turbo scale technology.
To allow your single tenant instance to scale dynamically as you bring on more customers, more products, more end users, and so forth.
Decouple your
monetization today
Join the enterprises scaling their revenue without rebuilding their stack every year.
Unleash the monetization potential of your software / SaaS / Hardware