Environments

Many customers have multiple environments within their data platform, such as production, pre-production, and test. Entropy Data supports managing multiple environments in different ways.

1. One Organization per Environment: Organizations are the tenants in the Entropy Data, highly isolated from each other. This is useful if you want to have strict separation between environments, and make sure that data products, teams, and users cannot request access to data outside of that environment. If your organization is named ACME Inc., and you have the environments prod, preprod, and test, we recommend to create three organizations: acme, acme-preprod, and acme-test. Users can be members of all three organizations, and switch between these organizations.
2. Single Organization for All Environments: This is useful if you want to allow requesting access across different environments, and if you want to see all data products and their output ports within a single organization. If your organization is named ACME Inc., and you have the environments prod, preprod, and test, we recommend to create a single organization with your company name, e.g., acme and use the environment field at the output port to distinguish between environments with the values prod, preprod, and test.
3. One Instance per Environment (Self-Hosted Only): If you have strict network isolation, you can consider to deploy a Entropy Data instance per environment. We recommend to use the same organization name (acme) for all three instances, and differentiate through the URLs, e.g., https://prod.example.com/acme, https://preprod.example.com/acme, and https://test.example.com/acme.

Test Deployment

If you want to test new releases of the Entropy Data before rolling it out in your enterprise, consider an additional deployment that is available for the data platform team. That test deployment acts as a playground for testing new features, and can be used to validate new configurations before applying them to the production deployment.

We do not offer a test deployment for the managed SaaS offering.