# 3.3 Set-up a server-hosted environment

This section outlines the process to setup and deploy OpenCRVS on a remote server environment for Staging (developer testing), Quality Assurance or live Production use.\
\
First you need to provision 1, 3 or 5 Ubuntu servers, with an additional, optional backup server that have internet connectivity, in a secure location with cooling and uninterrupted power supply.  

{% hint style="danger" %}
**OpenCRVS in production must be deployed in a minimum of a** [**Tier 2**](https://en.wikipedia.org/wiki/Data_center#Data_center_levels_and_tiers) **data centre with the strongest possible internet connection.**
{% endhint %}

#### Decide on the size of your deployment

OpenCRVS supports deployments to 1 server, but this is only recommended for a testing (staging), development or a quality assurance environment.

Alternatively, OpenCRVS supports deployments to 3 servers in a load balanced cluster.  This approach also provisions Mongo replica sets for managing a production database at a normal scale.

Finally, OpenCRVS supports deployments to 5 servers in a load balanced cluster.  This approach also provisions Mongo replica sets for managing a production database at a large scale.

If you wish to enable an automated backup from production onto another server, you will need an additional backup server.

This section instructs you how to provision your servers and deploy your OpenCRVS instance.


---

# 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://documentation.opencrvs.org/v1.3/setup/3.-installation/3.3-set-up-a-server-hosted-environment.md?ask=<question>
```

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.