> ## Documentation Index
> Fetch the complete documentation index at: https://docs.superblocks.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Deploy to multiple environments

By default, agents handle requests for [all data tags](/development-lifecycle/build/data-tags). To configure agents to execute workloads for a specific data tag, deploy separate agents to each of your environments or VPCs, and set the agent tags variable to a comma separated list of key-value pairs. Some examples include:

```text theme={null}
# Execute APIs for the production data tag
"profile:production"

# Execute APIs for both the development and staging data tags
"profile:development,profile:staging" 

# Execute APIs for all data tags (default)
"profile:*" 
```

<Info>
  The agent tag format uses the `profile:` prefix for backwards compatibility. The `profile:` prefix is equivalent to targeting data tags — each `profile:<KEY>` value maps to the data tag with the matching key.
</Info>

To configure agent tags, set the following variable depending on your deployment method.

<Tabs>
  <Tab title="Terraform">
    ```
    superblocks_agent_tags = "profile:<DATA_TAG_KEY>"`
    ```
  </Tab>

  <Tab title="Helm">
    ```yaml theme={null}
    superblocks:
      #(...)
      agentTags: "profile:<DATA_TAG_KEY>"
    ```
  </Tab>

  <Tab title="Docker">
    When running the agent with Docker Compose, set `SUPERBLOCKS_AGENT_TAGS` along with other required environment variables.

    ```
    curl -s https://raw.githubusercontent.com/superblocksteam/agent/main/compose.yaml | \
      SUPERBLOCKS_AGENT_TAGS="profile:<DATA_TAG_KEY>" \
      docker compose -p superblocks -f - up
    ```
  </Tab>
</Tabs>