Regional Policies

What is a Regional Policy?

A Regional Policy controls which Stacuity packet gateway your endpoints' traffic is routed through, on a per-country and per-operator basis. When a device attaches to a serving network, that serving network needs to know which Stacuity packet gateway to send the traffic to. The Regional Policy makes that determination based on which serving network the device is currently connected to.

Routing traffic to the geographically closest gateway reduces latency and avoids unnecessary international routing.

Regional Policies are assigned at the Endpoint Group level and apply to all endpoints in that group.

When to Use a Regional Policy

Control packet gateway routing: Direct endpoints in different regions to the closest Stacuity gateway. For example, route European deployments to the European gateway and North American deployments to the North American gateway.

Data residency and compliance: For deployments with regulatory requirements such as GDPR, a Regional Policy ensures endpoints only route data through gateways in approved geographic regions.

Vantiq Motors Example
Vantiq Charge operates EV charging stations across the EU. Under GDPR, charging session data must remain within EU infrastructure. Vantiq creates a Regional Policy with the Default gateway set to Europe, ensuring all sessions route to the European packet gateway regardless of which country the station is in.

How Regional Policies Work

Set a default primary (and optionally secondary) regional gateway - for example, Europe - and then override it for specific countries (or networks), such as the USA or Australia, by assigning it at a country or network level. If a secondary regional gateway is set, you can also select a distribution mode — either failover or load balancing between the two.

The Default row at the top sets the gateway used for all countries which are set to "inherit", specific networks can then "inherit" or override the country level setting. In most deployments, set a sensible default (e.g. Europe) and then override specific countries or operators where needed.

Where to Find Regional Policies

Navigate to Configuration → Regional Policies.

The list shows each policy's name. From this screen you can create, edit, and delete Regional Policies.

Create a Regional Policy

Steps

1. Go to Configuration → Regional Policies.
2. Click Add.
3. Fill in the fields and click Create.
4. After creation, open the Rules tab to configure per-country gateway assignments.

Fields

Rules are only available after the policy has been created.

Configuring Rules

After creating the policy, open the Rules tab. For each row, select a Regional Gateway from the dropdown:

• Default row: sets the gateway used for any country or operator not explicitly configured
• Country rows: set a specific gateway for all traffic from that country, this will override the default setting, or leave as Inherit to use the default setting for that country
• Operator rows: override the country-level setting for a specific operator, or leave as Inherit to use the country-level setting.

Regional Gateway Primary (Primary Region)

The Primary Region is the preferred location used to process and route your traffic during normal operation. This is typically selected based on factors such as geographic proximity, performance, and organisational requirements to provide the best user experience.

Regional Gateway Secondary (Secondary Region)

The Secondary Region feature provides greater control over service resilience by allowing you to define a backup region for your traffic.

If your primary region becomes unavailable, traffic can automatically be redirected to the configured secondary region, helping to maintain service continuity and minimise disruption.

Distribution Mode

Failover

Traffic is directed to the Primary Region during normal operation. If the Primary Region becomes unavailable, traffic automatically switches to the configured Secondary Region. This provides a simple and effective disaster recovery mechanism.

Load Balance

Traffic is distributed between the Primary and Secondary Regions. This can help spread traffic across multiple locations and improve resilience. Load balancing is most effective when the selected regions are geographically close to one another, such as two locations within Europe.

Assigning to an Endpoint Group

Assign the policy via Inventory → Endpoint Groups → Edit → Regional Policy.

Edit a Regional Policy

1. Go to Configuration → Regional Policies.
2. Click the edit icon next to the policy.
3. Update the Name or Moniker on the Details tab, or switch to the Rules tab to adjust gateway assignments.
4. Click Update.

Delete a Regional Policy

1. Go to Configuration → Regional Policies.
2. Click the delete icon.
3. Confirm deletion.