Data region
Every organization keeps its event data in one region. The choice decides where the events your properties send are stored and where every report, alert and query runs. You make it once, when your organization is new, and Monita enforces it from the first beacon onward.
Choosing the region
Section titled “Choosing the region”-
Sign in as an admin or owner. The first time an admin opens a new organization, Monita asks where to keep its data. Members see the same prompt but cannot answer it; they can keep browsing while an admin decides.
-
Pick a region.
- United States: your data is stored and processed in the US.
- European Union: your data is stored and processed in the EU.
-
Confirm. The choice applies immediately to every property in the organization, including properties created before the choice. Create your first property after this step so all of its traffic lands in the region you chose.
The current region is shown under Settings → Organization.
What the region covers
Section titled “What the region covers”- Event data — every beacon your properties send, and everything derived from it: issues, alerts, signal volume, journeys, compliance reports and the data dictionary.
- Queries — the app, the API and the MCP server all read from the organization’s region. There is no cross-region query.
Account records such as your organization name, team roster and property configuration are not event data and are not covered by the region setting.
Changing the region later
Section titled “Changing the region later”The region is locked once the organization has received events. Existing data does not move on its own, and a change would leave earlier events behind in the old region. To change region after that point, email support@getmonita.io and Monita will migrate the organization’s data as a managed change.
If you chose a region before any events arrived, or the only traffic so far was a test, the change is immediate: pick the new region again from the prompt or ask support to reset it.
Organization admins can set the region programmatically with PUT /v1/org/region and a body of { "region": "US" } or { "region": "EU" }. The call returns 409 region_locked once events exist. GET /v1/org reports the current region and whether it has been chosen yet (regionChosen).