# ENTERPRISE installations ENTERPRISE instances are available for customers to require any of the following: * High volume * Siloed cloud infrastructure * Multi-tenancy * [App development access](/middle-docs/app-development.md) ## Siloed stack With a Middle installation, ENTERPRISE customers get their own [cloud computer stack](/middle-docs/introduction/middles-infrastructure.md) to power their Middle functions and store their data. An ENTERPRISE instance of Middle keeps your data separate from other Middle customers and reserves computing power for the owner of the instance and their accounts. ## Predictable pricing You pay for your instance's cloud infrastructure. This encourages you to max out your instance's power, while maintaining low latency. When you need a bigger instance, you can always upgrade. ## Take ownership over your apps ENTERPRISE customers have open-sourced access to [Middle's pre-built apps](https://apps.middle.app/search). Middle has a integration development team that builds and maintains its library of connectors. However, if you develop in Python, you can customize existing apps and build your own. Your app developments live in your instance and cannot be accessed by other customers. ENTERPRISE app access comes with app performance metrics, app invocation history, and instance-wide API keys. ## Multi-tenancy Middle installations allow you to have as many accounts as you need. If you have multiple clients or brands in Middle, each one can get its own Middle account within your installation. This allows you to have multiple buckets in which data and workflows can be separated and managed accordingly. [User access](/middle-docs/user-access.md) can be granted to these individuals accounts or instance wide. ## No noisy neighbors Shared multi-tenant architecture can suffer from the noisy neighbor problem, a situation where one large tenant hogs resources that should be available for others. Siloed ENTERPRISE architecture ensures that all resources available for that instance are dedicated for that customer's own use. ## Targeted deployments Middle can roll out deployments to some ENTERPRISE customers, but not others. In this way, Middle tests platform updates on a small number of deployed production environments, and only if the update proves to be successful do deployments move ahead to other customers. Furthermore, we can respect ENTERPRISE customers' wishes to not receive updates at a particular time, such as a time when their system is under significant load with an important process running. ## Data deletion upon cancellation Middle customers can feel confident that if they ever were to discontinue using the product, all data would be irrevocably deleted with ease. Middle simply deletes the stack, and all associated resources such as the database, go away forever. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.middle.app/middle-docs/introduction/enterprise-installations.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.