3. Paste in other payloads and see if they look fine, go to step **2** if

necessary.

After iterating on the config, paste it back into the project config located at

For example:

{

"publicKeys": [

{

"publicKey": "___PUBLIC_KEY___",

"isEnabled": true

}

],

"config": {

"allowedDomains": ["*"],

"piiConfig": {

"rules": {

"device_id": {

"type": "pattern",

"pattern": "d/[a-f0-9]{12}",

"redaction": {

"method": "hash"

}

}

},

"applications": {

"freeform": ["device_id"]

}

}

}

}

[advanced data scrubbing]: https://docs.sentry.io/product/data-management-settings/scrubbing/advanced-datascrubbing/

[relay]: https://github.com/getsentry/relay

[piinguin]: https://getsentry.github.io/piinguin

- The `mode` setting, which configures the major mode in which Relay operates. For more information on available Relay modes, refer to [Relay Modes](../modes/).

<Alert level="warning">

Currently, only `proxy` and `static` mode are available to all organizations. Relay in `managed` mode is available only on the [Business and Enterprise plans](https://sentry.io/pricing/).

</Alert>

- The `upstream` setting configures the server to which Relay will forward the

events (by default the main `sentry.io` URL).

- Improve event response time in regions with low bandwidth or limited connectivity

- Act as an opaque proxy for organizations that restrict all HTTP communication to a custom domain name

<Alert>

Relay in `managed` mode is available only on the [Business and Enterprise plans](https://sentry.io/pricing/).

</Alert>

Relay is designed to support organizations that have specific enterprise security requirements for data scrubbing of personally identifiable information (PII), response time, and enterprise domain management.

Relay can operate in one of several major modes, and it is critical to understand the modes prior if you are configuring the Relay server rather than using the default settings.

The mode is stored in the configuration file, which contains the `relay.mode` field. This field specifies the mode in which Relay will run: `managed`, `static`, or `proxy`. The Relay mode controls the way Relay obtains project settings for events.

<Alert>

Relay in `managed` mode is available only on the [Business and Enterprise plans](https://sentry.io/pricing/).

</Alert>

The mode is stored in the configuration file, which contains the `relay.mode` field. This field specifies the mode in which Relay will run: `managed` or `proxy`. The Relay mode controls whether or not Relay obtains project settings for events.

In Sentry, event processing is configured according to both project and organization settings. Some settings, such as privacy controls, are set at the organization level, then inherited by all projects in that organization; other settings are specified per project. For Relay, events are processed according to the inherited project settings to which the event is sent.

mode: managed

To activate static mode, set this configuration:

| key | type | value | description |

| -------------------------- | ------- | --------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

| relay.mode | String | default value: `managed` possible values: `managed, static, proxy, capture` optional: `false` | Controls how Relay obtains the project configuration for events. For detailed explanation of these modes, see [Relay Modes](/product/relay/modes/). `Environment variable: "RELAY_MODE."` |

| relay.mode | String | default value: `managed` possible values: `managed, proxy` optional: `false` | Controls how Relay obtains the project configuration for events. For detailed explanation of these modes, see [Relay Modes](/product/relay/modes/). `Environment variable: "RELAY_MODE."` |

| relay.upstream | String | default value: `https://sentry.io` optional: `false` | Fully qualified URL of the upstream Relay or Sentry instance. `Environment variable: "RELAY_UPSTREAM_URL".` <Alert level="warning" title="Important"> Relay doesn't check for cycles. Don't set this option to an endpoint that will cause events to be cycled back here. </Alert> |

| relay.host | String | default value: `0.0.0.0 in Docker, otherwise 127.0.0.1` optional: `false` | The host to which Relay should bind (network interface). `Environment variable: "RELAY_HOST".` |

| relay.port | Integer | default value: `3000` optional: `false` | The port to which Relay should bind for the unencrypted Relay HTTP server. `Environment variable: "RELAY_PORT".` |

from: '/product/security/relay/',

to: '/product/relay/',

},

{

from: '/meta/relay/projects/',

to: '/product/relay/projects/',

},

{

from: '/meta/relay/getting-started/',

to: '/product/relay/getting-started/',

},

{

from: '/meta/relay/pii-and-data-scrubbing/',

to: '/product/relay/pii-and-data-scrubbing/',

},

{

from: '/meta/relay/options/',

to: '/product/relay/options/',