> For the complete documentation index, see [llms.txt](https://hatchbox.gitbook.io/hatchbox/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hatchbox.gitbook.io/hatchbox/clusters.md). # Clusters ## Can I deploy multiple apps to a single server? Yes you can. You'll just need to create a single-server cluster. Once you're done, you can deploy as many apps as you want to it. You'll need to add domains to each app so that NGINX knows which app to serve when a request comes in. If you don't add domains, NGINX will just serve up the first app it finds for every request. Just keep in mind that the RAM of your server will probably be the limiting factor of how many apps you can run. ## How do multi-server clusters work? When you create a multi-server cluster, you choose how many servers you want and what size each of them should be. Then, you can tag each server with the roles it should have. For example, you can tag one server as your load balancer, another server as a web server and the cron server, and then one server for your databases and background workers. You can add a new server to the cluster at any time and move roles around as needed. We don't let you migrate your database servers to prevent downtime from migrating data. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://hatchbox.gitbook.io/hatchbox/clusters.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.