> 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/enterprise-security/security-and-platform-details/turboscale.md). # Turboscale Discover how Turboscale, Nalpeiron's auto-scaling architecture built on Kubernetes and Docker, handles billions of transactions and scales every layer of the stack on demand. {% embed url="" %} Turboscale is Nalpeiron's term for our highly scalable architecture, which can handle billions of transactions automatically. This is a proprietary development we developed to allow every part of our infrastructure to grow and shrink on demand. After 20+ years handling huge volumes of variable traffic, we invested millions in building modern infrastructure that allows for incredible flexibility in traffic volumes at any time. We have learned that traffic can change a great deal over a day or a month, and this allows us to keep our uptime promise no matter how many millions of end users are connected to our platform. Unlike our competitors, who can't easily handle large traffic volumes, we can handle an almost unlimited flow of traffic and data at any time, 24/7/365. ### Turboscale explained One of the key trends we've seen—and in fact pioneered—is the move toward cloud-based software licensing. In our environment, we focus on multi-tenant clusters as our primary go-to-market solution, though we now also offer a single-tenant edition. In both environments, we've built scalability into every aspect of the architecture. What does this mean? At our core, our architecture is built around Docker containers managed through Kubernetes that automatically scale. As demand increases, we spin up additional Docker workers to handle specific workload aspects. With Kubernetes management, you get a seamless experience. We also have an auto-scaling database for both performance and storage. As additional capacity is needed, it automatically scales and spins up workers to handle database queries. Similarly, our API handlers use Docker containers that scale up and down as needed, ensuring low-latency access and excellent performance regardless of traffic volume on the multi-tenant cluster. The user interface—including the dashboard and end-user portal—is built around these same APIs. Whether you have tens of customers or tens of millions, every part of our stack will scale through this turbo-scale approach. ### Turboscale architecture **Zentitle will automatically scale to demand across the stack.** * Initially, HPA (Horizontal Pod Autoscaling) adds new instances (pods) of individual applications (e.g., Licensing API and Core Service). * As the whole cluster reaches capacity, new Kubernetes nodes are being provisioned automatically. * The reverse is true as demand reduces. * Database server capacity is automatically scaled, as well. **HPA (Horizontal Pod Autoscaling)** ![](https://docs.nalpeiron.com/~gitbook/image?url=https%3A%2F%2F2412542193-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F1tBhTGn5igyI6ECLHjpC%252Fuploads%252F4EraekZ9UyDhpGnjpS5n%252Fhpa.png%3Falt%3Dmedia%26token%3D266e20a2-7733-4dae-ad30-b415d417b85e\&width=768\&dpr=4\&quality=100\&sign=3c514909\&sv=2) • Observe services for CPU/Memory pressure and modify instances as needed • Horizontal scaling means deploying more Pods to respond to increased load. This is different from vertical scaling, which for Kubernetes would mean assigning more resources (e.g., memory or CPU) to the Pods that are already running for the workload. {% hint style="success" %} ### Article interesting? Test drive the Nalpeiron Growth Platform. Get a FREE Trial of The Nalpeiron Growth Platform {% endhint %} --- # 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/enterprise-security/security-and-platform-details/turboscale.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.