min read

Scalr Organizational Hierarchy - Best Practices


This is some text inside of a div block.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

The #1 question we get asked is “What are the best practices for using Scalr accounts, environments, and workspaces?”

This picture shows the logical organizational model in Scalr:

Working from the bottom up the recommended use of each “scope” is as follows:


  • A workspace is used to deploy and manage logical sub-divisions of your infrastructure, such as networking, database, K8 clusters, application instances etc.
  • Workspace state can be shared to enable the use of shared infrastructure.
  • This is where a Terraform run is performed and a state file (and its history) are stored.
  • Variables (Terraform and shell) are assigned values to be passed into a run including provider credentials, possibly set at higher scopes.