Cloud server locations

Put the workload where it works best.

Vloxt exposes eligible locations from the active server catalogue. Choose a server shape first, compare its locations, then confirm current stock during ordering.

See available locations

How should I choose a server location?

Choose the location that best balances latency, data-placement needs, and current availability. The closest location is often a good starting point, but connected databases, storage, and users may make another location more practical.

Latency

Choose a location close to the people or systems that exchange the most data with your server.

Availability

A location appears only when it is enabled for the selected server shape. Stock is checked during ordering.

Data placement

Consider where your users, backups, and connected services are located before choosing.

Map the request path before choosing the map point

A nearby region can still produce a slow application when its database or other conversational dependency is far away. Test the whole path from representative networks.

UsersRequest

Latency-sensitive

ApplicationCompute

Frequent round trips

DatabaseData

Independent copy

RecoveryRestore

Place the most conversational systems close together. Keep a recovery copy reachable through an independent access path.

Eligibility is a separate decision

A technically suitable region must also support the chosen server configuration and meet the workload’s data-placement requirements. Current catalogue data—not this model—decides which combinations can proceed.

Near usersNear dataEligible planRegion ALow delaySame pathVerify nowRegion BHigher delaySame pathVerify nowRegion CLow delayRemote dataDifferent family

This is a decision model, not current stock. The catalogue is the authority for enabled plan and location combinations.

Availability is checked twice

Ordering performs a current stock check before an invoice is created. Capacity is checked again immediately before provisioning because availability can change between payment and deployment. If the selected configuration is no longer available, automated provisioning stops and the order enters a recoverable state.

Location availability varies by server family

Shared CPU, dedicated CPU, cloud GPU, and bare-metal systems do not necessarily share the same location coverage. The server catalogue displays only the locations currently mapped and enabled for each plan.