# Setting Up Multiple Instances of Sisense

> If you want to support multiple instances of Sisense, for example, a dev and a production environment, or if you offer Sisense dashboards to multiple customers and want a specific Sisense instance for each customer, you can set up multiple deployments.

*Source: https://docs.sisense.com/main/SisenseLinux/setting-up-multiple-instances-of-sisense.htm*

---

Last updated: June 10, 2026

|  |  |
| --- | --- |
| [Tier](https://www.sisense.com/pricing/#pricing) | [Deployment](https://docs.sisense.com/main/SisenseLinux/introduction-to-sisense-cloud-managed-services.md#ComparisonofManagedCloudandSelfHosted) |
| Enterprise | Cloud     On-Prem |

If you want to support multiple instances of Sisense (for example, a dev/staging and a production environment), you can set up
multiple deployments.

**Note:**

- This is currently an experimental feature.
- You cannot install multiple namespaces in single node deployments.
- Having different versions on the same cluster is currently not fully supported and may cause issues.

  

**To set up another Sisense instance:**

1. Open the configuration file used when you installed Sisense, for example:

   `vim cloud_config.yaml`

   The command should contain the name of the configuration file you used, not necessarily cloud\_config.yaml.
2. Modify the values of the following parameters:

   **update** - Set to **true**.
     
   **gateway\_port** - Enter a new value for each deployment. The value should be between
   30000-32000. You cannot have two deployments with the same **gateway\_port** value.
     
   **namespace\_name** - Enter a unique namespace name distinct from any other namespace names you
   have.

   Note:

   Multi-namespace deployment using HTTPS is also supported. To use HTTPS: instead of `gateway_port`, enter `is_ssl: true`, and provide your `ssl_key_path`, `ssl_cer_path` and `application_dns_name`.

   For example:

   [Copy](javascript:void(0);)

   ```
   application_dns_name: "your-name.example.com"  
   is_ssl: true  
   ssl_key_path: /path/to/key  
   ssl_cer_path: /path/to/cert
   ```
3. Run your configuration script to create a new Sisense instance.