Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.rafftechnologies.com/llms.txt

Use this file to discover all available pages before exploring further.

Updated May 8, 2026 A region is a geographic location where Raff operates compute, storage, and networking. The region you pick at VM creation determines where the VM physically lives, which IP ranges it can be assigned, and which VPCs it can join.

Available regions

RegionStatusNotes
us-eastAvailableThe single region today
Pass region: "us-east" (or pick “US East” in the dashboard) on every create call. The List Regions endpoint returns the current set programmatically.

What region scope means

A region is a hard boundary — resources from different regions cannot share networking or be moved between regions in place.
ScopeBehavior
VM locationThe VM’s CPU, RAM, and disk physically live in the chosen region’s datacenter
VPC scopeA VPC and every VM in it must share a region. You can’t have one VPC spanning two regions
Public IPsIPv4 / IPv6 addresses come from region-specific pools. A reserved IP can only attach to VMs in the same region it was reserved in
VolumesA volume can only attach to VMs in its own region
Object StorageBuckets are region-scoped; same-region traffic between VMs and Object Storage is free
Snapshots and backupsStored in the same region as the source VM

Picking a region

With one region today, the choice is straightforward — us-east. When this matters more in the future:
  • Latency — pick the region closest to your users. Round-trip time to a region is the floor of how fast your service can respond
  • Data residency — if you have customer-data-locality requirements, the region determines where the data is stored
  • Cross-region traffic — same-region traffic between Raff resources is free; cross-region (when other regions exist) goes over the public internet and counts against egress

Migrating a VM to a different region

You can’t change a running VM’s region. The migration path:
  1. Snapshot the source VM (or save its OS disk as a Custom Image)
  2. Create a new VM in the target region from that image
  3. Restore data from any volume snapshots or backups, or copy data via SCP/SFTP/rsync
  4. Update DNS / load balancer / clients to point at the new VM
  5. Delete the source VM when the cutover is done — unused subscription time credits back to your balance
Keep the old VM running until the new one is verified — there’s no auto-failover between regions.

Plans & sizing

Per-plan specs and pricing.

VPC

Region-scoped private networking.

Public IPs

Region-scoped IPv4 / IPv6.
Last modified on May 8, 2026