There are two types of execution modes in Scalr, remote and local. The remote execution mode means the Terraform or OpenTofu (OTF) run will execute in a container that is running on the Scalr infrastructure or a self-hosted agent. When using the remote mode, you gain all of the benefits of Scalr. Local execution mode means that the run will execute local to where the Terraform or OTF commands have been executed, but the state is still stored in Scalr. Users are not charged for local runs in Scalr. ### Use Cases for Local Execution We typically see the execution mode being updated to local during early development cycles. During this time, there is more trial and error when developing the Terraform or OTF code and some of the integrations that Scalr provides may not be as critical. Once the development is finished and the code is ready for production, we usually see the execution mode switched back to remote to gain the full benefits of using a remote backend. The other common use case we see for this is when an organization just needs a little more structure and wants to have a central place for storing state. You might already have a pipeline outside of Scalr and want to have the ability to organize workspaces, restrict who can access state through RBAC, and have centralized state storage. All of this, plus a private module registry is possible when using local execution. ### Add the Remote Backend To take advantage of Scalr for state storage, you will need to set the remote backend in your code: ```hcl terraform { backend "remote" { hostname = ".scalr.io" organization = "" workspaces { name = "" } } } ``` You will also need to ensure you have Scalr credentials local to where the run is being executed. These can be set by running `terraform login .scalr.io` ### Ways to Set a Workspace to Local Execution Mode The workspace attribute `execution-mode` can be updated in Scalr through the Scalr CLI, provider, or API. The ability to update it through the UI is coming soon. #### Scalr CLI The Scalr [CLI](https://docs.scalr.io/docs/overview-2) can be used for quick operational changes that don't require coding around the API or using the Scalr provider. See the command below to update an existing workspace's execution-mode. ```hcl ##First set environment variables: export SCALR_HOSTNAME=.scalr.io export SCALR_TOKEN= export SCALR_ACCOUNT= ##Make the CLI call to update the workspace: scalr update-workspace -environment-id= -workspace= -name= -execution-mode=local ``` #### Scalr Provider The Scalr provider can also be used to update the workspace settings. We highly recommend managing all Scalr objects through the Scalr Terraform or OTF provider to easily scale your operations. The workspace `resource` must be used and you simply add the `execution_mode` attribute: ```hcl resource "scalr_workspace" "cli-driven" { name = "" environment_id = "" execution_mode = "local" } ``` #### Scalr API To do this in the Scalr API, you'll want to call the [create workspace](https://docs.scalr.io/reference/create_workspace) or [update workspace](https://docs.scalr.io/reference/update_workspace) endpoints, depending on the situation. The example below is updating an existing workspace: ```hcl curl --request PATCH \ --url https://.scalr.io/api/iacp/v3/workspaces/ \ --header 'Prefer: profile=preview' \ --header 'accept: application/vnd.api+json' \ --header 'authorization: Bearer ' \ --header 'content-type: application/vnd.api+json' \ --data ' { "data": { "attributes": { "execution-mode": "local", "name": "my-workspace" }, "type": "workspaces" } } ' ``` ### Pros and Cons of Local Execution Mode The main pro of using local execution mode is that you are not charged for it in Scalr. As mentioned before, this is helpful during early development cycles when you might be going through a lot of trial and error and don't need the advantages of a remote backend like Scalr. That being said, there are a few cons to setting the workspace to local. First, you are not using the Scalr pipeline, so you will not see the run reported anywhere in Scalr. This also means that you will not see the cost estimation or be able to utilize the Open Policy Agent integration. Lastly, the biggest con is that you are not able to use the provider configurations that are stored in Scalr for authentication to an external provider. This is one of the more critical security features in Scalr as the credentials are automatically passed to the runs without the users having to supply them. But, as mentioned, this might be for development environments where some of the security protocols are relaxed. ### Wrapping Up The `execution-mode` attribute of a workspace gives organizations flexibility on choosing how they want to use Scalr. With this set, you have the ability to use Scalr for free until you decide you want to take advantage of the full feature set, which includes integrations, reporting, and more. [Sign Up](https://scalr.io/v2/signup/) and get started!

Ryan Fee

Articles by Ryan Fee

How to Use a MCP Server with Terraform: 6 Prompts for Infrastructure Teams

Selecting a Terraform Cloud Alternative (March 2026)

Terraform Modules Explained

Stop Troubleshooting Terraform: How Scalr AI Empowers Platform Teams

Terraform Drift Detection and Management: A Comprehensive Guide

Using Checkov with Terraform - Integrations, Features, Examples

What is a Terraform TACO?

What is Terraform?

Terraform Registry: Public vs Private Module Registries Explained

New Feature: Private Module Registry Namespaces

Terraform Outputs: How to with Examples

Terraform Providers: Complete Configuration and Management Guide

Terraform State Files Best Practices

Using the AWS S3 Backend Block in Terraform

Using the AzureRM Backend Block in Terraform

Using the GCS Backend Block in Terraform

Understanding the Terraform ignore_changes Lifecycle Block

Everything you need to know about using Terraform or OpenTofu with Slack

Scalr's MCP Server: The AI Assistant That Does the Heavy Lifting

Introducing Scalr Metrics

November 2025 Release Notes

Scalr Feature - Storage Profiles

New Scalr Feature: Control Tower

Scalr Product Updates - August 2025

Announcing a Simpler, More Transparent Pricing Model

What are Terraform Lock Files

Scalr Product Updates - July 2025

Dynamic Backend Blocks with OpenTofu

Scalr Product Updates - June 2025

How to Share Terraform State

A Guide to Terraform Audit Logs

Product Update: Scalr Federated Environments

Product Updates April 2025: Flexible Storage Options, Federation, and GitOps Workflows

Product Updates May 2025: Scalr OIDC, Improved GitOps Flows, and PR Comment Approval

About the Learning Center

Maintaining Terraform Module Health with Dependabot and Scalr

A beginner's guide to the terraform init command

HCP Terraform Cloud Pricing Review - 2025

Terraform Random Provider

Using Terraform Workspace Prefixes in a Remote Backend

Scalr VSCode Extension for Terraform & OpenTofu

The Terraform & OpenTofu Terralith

How to Use Snyk with Terraform: Securing Your Infrastructure as Code

New Feature: Terraform & OpenTofu Ephemeral Workspaces

Integrating Terraform Events w/ AWS EventBridge

Use local execution mode for free with Scalr

Terraform and OpenTofu Pull Request Comments The Right Way

Understanding Terraform & OpenTofu Workspaces

How to use the Azure DevOps Terraform Provider

How to use the Bitbucket Terraform Provider

How to use Terraform or OpenTofu to Manage Datadog

Why Terraform Concurrency Matters

API Driven Workflows for Terraform and OpenTofu

Understanding OpenTofu Remote Backends

Scaling Terraform Modules

How to use Terraform to manage Okta

Terraform at Scale

OpenTofu Runs are Free in Scalr

Scalr Offers Free Terraform Agents

Scalr offers a free private module registry

OpenTofu Alpha release

10 OpenTofu Commands

Get started with OpenTofu by installing from source

Key similarities of Scalr and Terraform Cloud that make Scalr the alternative

Increased productivity with Account Level Workspaces

Terraform Import Block - New Terraform Feature

Terraform No Code Provisioning made easy on Scalr

How to easily migrate from Terraform Cloud to Scalr

Terraform Operations at Scale

Terraform Modules - Define, Enforce, Report

Don't Build a Service Catalog

3 ways to use Terraform Module and Provider Reports

Monitor Terraform Runs in Datadog

New Feature: Terraform Reports in Scalr

Using Scalr Hooks with Bridgecrew Yor

How To Manage Scalr RBAC At Scale Using The Scalr Provider

Introducing Native Support for Terraform Variable Files in Scalr

How To Structure Terraform Deployments At Scale