As the engine owner, click Upgrade class on Replica nodes, choose a target class, pick as many nodes of that class as your engine has, and click Start migration.
- Open the engine, choose Replica nodes and click Upgrade class.
- Under Target class · currently …, pick a class. Only more powerful classes are offered, each with its vCPU, RAM, disk and a "From … /node/mo" price.
- Under Pick … nodes, select exactly as many nodes as the engine has now; the counter reads, for example, "2 of 4 picked". The catalog is fixed to the target class and your engine's privacy mode.
- Check This upgrade: Nodes, Monthly now, New monthly and Due now.
- Click Start migration. You're taken back to Replica nodes.
Good to know
- Only the engine owner can start, stop or resume a migration. Everyone on the engine sees its progress.
- Every node is replaced, one at a time, and each new node has to catch up before the next one starts.
- A banner on Replica nodes shows "Changing class from … to …", how many new nodes are live, and The roll, in order. Waiting nodes show as Queued; replaced ones stay listed as Reserved and stay billed to the end of the period already paid for, with no refund.
- Nothing is charged up front: the engine's balance pays for each new node day by day from the day it joins. On the free tier the migration costs nothing.
- Stop migration ends it early. The swaps that already ran stand, and the engine is priced for the set it has then.
- If the migration pauses, the banner says why (for example, the balance no longer covers the next node, or the joining node is stuck catching up). Fix the cause, then click Resume.
- While a migration runs, you can't add, remove or replace nodes. It can't start while a recently added node is still catching up.
- The engine keeps its node count and can't move to a smaller class. Use Add nodes to grow it.
- On the top class, Dense, clicking Upgrade class only shows "This engine is already on the most powerful class."