> For the complete documentation index, see [llms.txt](https://docs.nalpeiron.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nalpeiron.com/the-platform/single-tenant-hosting.md). # Single tenant hosting Compare Nalpeiron's multi-tenant and single-tenant hosting models to decide which trade-offs — location, security, performance, and risk — best fit your organization. {% embed url="" %} We offer the Nalpeiron Growth Platform in two different models. The first is multi-tenant, our standard way of going to market, where multiple customers are serviced through our common core managed infrastructure. We also offer a single-tenant instance, reserved only for you and your customers, which can be managed on a dedicated basis. ### What are the trade-offs? With multi-tenancy, you have a common approach: a large number of customers and end users working together to leverage shared infrastructure. With TurboScale, you can be confident that the system will scale up accordingly, regardless of which individual vendors or customers are causing demand. You can trust that the system will scale effectively even in this multi-tenant environment. If you'd prefer the independence of a single-tenant instance, we can accommodate that as well. We're using AWS to manage our infrastructure, and within that single-tenant environment, you can request a specific availability zone (AZ) of your choice. For example, you might want an availability zone based in Frankfurt to provide lower latency and better performance for your European customers, or you may have GDPR data protection requirements that you'd like to manage separately. Single-tenant hosting lets you manage all your data independently of our other customers. Some organizations prefer their data to be segregated this way. It also provides additional independence—for example, if you have any concerns about Nalpeiron's ongoing viability, we include in our standard single-tenant contract the ability for you to take over that instance if any unusual circumstances were to affect our organization. Of course, even within that single-tenant environment, you continue to benefit from our TurboScale technology, which dynamically scales your instance as you add more customers, products, and end users. ### The Benefits of Single-Tenant Instances #### GDPR and location choices • With options on hosting location, you can handle any regional issues as required. #### Enhanced Security and Privacy • Complete control over the security measures implemented on your infrastructure. Also, it eliminates the concern of sharing resources with other tenants, ensuring that your sensitive data remains isolated and protected. #### Improved Performance and Scalability • Optimize the performance of your applications and systems with no competition for resources from other tenants. Your applications can run at their maximum potential. #### Reduced Risk • With the single-tenant option, you have control of your destiny, independent of a supplier like Nalpeiron, as everything is running in a hyperscaler under your control. #### Conclusion • For larger clients with large volumes of users or high revenue values, a single-tenant option provides many benefits, from reduced risks to total infrastructure flexibility. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.nalpeiron.com/the-platform/single-tenant-hosting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.