A complete guide to data residency and region selection.

Data Residency and Region Selection

PetRock.cloud operates rocks and stores associated data across four geographic regions. This article describes each region, how to choose one, and what data residency does and does not control.

Available regions

Region ID Location Tier availability
us-east-stone-1 Northern Virginia, USA All tiers
us-west-stone-2 Oregon, USA Cobble and above
eu-west-stone-1 Frankfurt, Germany Cobble and above
ap-stone-1 Singapore Boulder and above

The Pebble tier is restricted to us-east-stone-1 to keep costs down. Higher tiers may select any region.

What data residency controls

When you provision a rock in a region, the following data is stored in that region:

  • Rock metadata (name, tags, configuration)
  • Audit log entries scoped to that rock
  • Webhook delivery records for events emitted by that rock (none, in practice)
  • Backups of the above

What data residency does not control:

  • Authentication infrastructure, which is multi-region by design
  • Aggregated billing data, stored in the workspace's billing region
  • Anonymized usage telemetry (active rock counts, dashboard load latency)
  • Status page and public marketing content

Selecting a region

At provisioning

  1. From the dashboard, click Provision Rock.
  2. In the Region dropdown, select the desired region.
  3. Complete provisioning as normal.

The region cannot be changed without migration after provisioning.

Migrating a rock to a different region

  1. Open the rock detail page.
  2. Go to Settings → Region.
  3. Click Migrate Region.
  4. Select the destination region.
  5. Confirm.

Migration takes 5-10 minutes. During migration, the rock's status displays as Migrating. The rock remains addressable via the API throughout, though API calls may experience elevated latency.

Note: Migration does not require any rock-side preparation, since the rock is not actively performing work. The migration moves only metadata and management plane state.

Choosing a region

Considerations when selecting a region:

  • Compliance requirements: GDPR, HIPAA, or local data protection laws may dictate a specific region.
  • Latency to dashboard users: The region affects API and dashboard latency, not rock latency. The rock's response time is constant across regions.
  • Cost: Pricing varies slightly by region. See Settings → Billing → Regional Pricing for current rates.
  • Tier availability: Some regions require a higher tier.

Region-locked workspaces

Workspaces with Region Lock enabled (under Settings → Workspace) restrict all rock provisioning to a single region. New rocks outside the locked region will fail with 403 Region Restricted.

Region Lock is required for workspaces with EU Data Residency enabled. See GDPR and European Rocks.

Cross-region backup

Each region maintains backups within that same region's storage. No cross-region replication of customer data occurs by default. Customers requiring cross-region disaster recovery should contact sales for an enterprise arrangement.

Region status

Per-region status is published at status.petrock.cloud. Each region has independent status indicators for:

  • API availability
  • Dashboard availability
  • Webhook delivery
  • Provisioning success rate

Rock activity is not displayed on the status page since there is no rock activity to monitor.