NimbusNexus

Region requests

By default new accounts get access to one region (whichever they picked at signup). Adding access to additional regions requires a region request — a short form explaining the workload that needs the new region. Most production accounts are approved within a business day; the gating exists for capacity planning and to flag unusual patterns (a brand-new account asking for capacity in five regions on day one is worth a brief conversation).

This endpoint also handles quota uplifts — a request to raise the VM count, vCPU, or storage limit in a region you already have access to. Same gating reason: large requests need capacity planning. See Quotas for the quota model itself.

The API surface here exists so programmatic deployment can fire-and-forget the request; the approval still happens manually on our side (this is one of the few corners of the API that isn't fully self-service by design).

What's next

  • Regions — the list of available regions.
  • Quotas — the per-project limits a region-request can also adjust.
  • Account overview — the account context for region access.

No endpoints to show

The OpenAPI spec doesn't currently expose any endpoints under theregion-requeststag. This is usually a manifest typo; check that the tag matches what the backend serves at /openapi/external.json.