Instance migration

Resize an instance

Instance size (compute tier) can be changed at any time. The change is saved immediately but shown as “pending” until you click Apply Changes to deploy the new configuration. 4xlarge and above are only available on Business and Enterprise plans.

Instance sizes

Size	vCPU	RAM	Compute units
nano	0.25	0.5 GB	0.5
small	0.25	1 GB	1
medium	0.25	2 GB	2
large	0.50	4 GB	4
xlarge	1.00	8 GB	8
2xlarge	2.00	16 GB	16
4xlarge	4.00	30 GB	32
8xlarge	8.00	60 GB	64
16xlarge	16.00	120 GB	128

Choose a size that fits your dataset in memory, not your query load — the entire snapshot must fit in RAM. A good starting point: take your MySQL database size and multiply by 1.5× for index and overhead headroom.

How to resize

1. Open the database in the dashboard and go to Settings

2. Select the new Instance size from the dropdown

3. Click Save

4. Click Rebuild to apply the change — the current instance stays running until the new one is ready, then traffic is swapped over

The rebuild takes 3–5 minutes. The old instance continues serving queries until the new one is live.

Note

Compute unit consumption changes immediately on the next billing period after the rebuild completes. Downsizing releases units back to your plan balance; upsizing consumes additional units (overage applies if you exceed your plan limit).

---

Move an instance to a different region

Instances cannot be migrated between regions in-place. The process is: provision a new instance in the target region, verify it, then terminate the old one.

Caution

Multi-region deployment is available on Team plan and above. Verify your plan before attempting to provision in a non-default region.

Available regions

Region	Location
eu-west-1	Ireland (EU) — default for all accounts
us-east-1	Virginia (US)

Migration steps

1. Provision a new instance in the target region

   Open the database in the dashboard, click Add Instance, and select the target region from the Region dropdown. Complete provisioning — this takes 3–5 minutes.

2. Verify the new instance

   Once the new instance is running, run a test query against it:

   curl https://<new-instance-id>.reflexdb.cloud/query \
     -H "Authorization: Bearer <api-key>" \
     -d '<any_table> { id }'

   Confirm the response matches your expectations.

3. Update your clients

   Update your application’s ReflexDB endpoint URL to point to the new instance ID. If you use multiple API keys, create new keys on the new instance before removing the old ones.

4. Terminate the old instance

   Once all traffic is routing to the new instance, open the old database entry in the dashboard and click Terminate. This removes the running instance and all associated infrastructure.

API keys after migration

API keys are scoped to a specific instance. After provisioning the new instance:

1. Create new API keys on the new instance (Database → API Keys → New Key)
2. Update your application with the new keys
3. Revoke the old keys once traffic has fully switched over

Changing the default region on a connection

To make future instances in this connection default to the new region:

1. Open the connection in the dashboard (Connections)
2. Edit the Default region field
3. Save — new instances will use this region by default

Existing instances are not affected by changing the connection’s default region.