Private Fleets
Reserve standby capacity on monthly basis for persistent 24/7 always online servers. Choose your preference between Virtual Machines (Performance) or Bare Metal (Overdrive) specifications.
Private Fleets are an optional addition to Edgegap Cloud (default), a popular hosting option enabling Persistence with 24/7 always online servers and favorable pricing for games with predictable traffic.
🌟 Upgrade to Pay as You Go tier to unlock private fleets hosting with standby capacity!
Alternatively, see Match-Bound orchestration to utilize fractional vCPU pricing.
Smart Fleets (legacy) and Sessions (legacy) will be deprecated and replaced by Private Fleets and Server Browser on March 1st 2026. Reach out over Discord to learn more and get help with migration.
✔️ Introduction
Private Fleets let you pick specific host locations and reserve dedicated standby compute capacity within our globally available cloud infrastructure, suitable for:
persistent 24/7 servers featuring open worlds with user-generated content placed by players,
MMO games prioritizing social experiences with high amount of concurrent users per server,
released games with mostly predictable daily traffic patterns and stable player communities.
☁️ Hardware
Pick one of our generic host specifications:
Best Suited For
match-based games, or with predictable traffic
CPU-intensive games (AI), or above 1:2 CPU/RAM ratio
CPU Specifications
16 vCPU 2.0 - 3.7 GHz frequency
16 vCPU 3.7 - 5.1 GHz frequency
RAM Specifications
32 GB
64 GB
Free Egress Included
5 TB per Host
5 TB per Host
Price, pre-paid monthly
(commitment based)
$250.00 per Host
$290.00 per Host
Your first month reservation price and free egress quota are pro-rated. This means you are charged only for the portion of time until the end of current month.
Reservations automatically renew on the first day of every month at 00:00 UTC until deleted. Your card will be automatically charged the monthly amount for renewed hosts at this time.
A fleet with active hosts may not swap specifications. Create a new fleet or delete active hosts first.
Small amount of resources on each host is reserved for Operating System, Monitoring, and Orchestration.
Modifying Schedule and Deleting Hosts
You may modify or delete this schedule at any time prior to the scheduled time, at no charge. You may designate any number of reserved (active) private hosts for deletion at the end of the current billing period, prior to the renewal date. Deleted hosts will not be charged for subsequent renewals. Any deployments running on private hosts scheduled for deletion will be gracefully shut down at the time of deletion without additional warnings.
Delayed Start or Insufficient Provider Capacity
In the event of delayed private host start or insufficient provider capacity, your payment amount and invoice for the scheduled or renewal periods will be adjusted accordingly.
📍 Locations
Choose a centroid by dropping a pin and preview your primary/fallback locations for new hosts.
Select a fallback strategy to control suitable locations for each centroid:
Proximity (default) - 700 km centroid radius, for more latency-sensitive designs,
Redundancy - 1,400 km centroid radius, allowing further locations as fallbacks.
Location availability depends on chosen hardware specification. Overdrive availability is limited.
📢 API provisioning under development, let us know about your Continuous Integration needs!
🔄 Host Lifecycle
Private Fleet hosts follow a simple three step lifecycle sequence.
📢 Scheduling new host additions is under development, let us know about your release process!
1. Pending
New hosts have been requested, we're starting them in order of distance from centroid.
2. Active
Host is active and responsive, ready to 1. Start a Deployment.
3. Scheduled for Deletion
While stile active, this host will be deleted at the end of the current billing period (month). This action can be reverted (cancelled) at any time until deletion takes place.
Deployments running on private hosts will be gracefully stopped once the host is deleted.
Prevent frustration due to rollbacks and gameplay disruption by notifying players and rerouting new deployments to other private fleet hosts, once a private host scheduled for deletion is nearing shutdown.
⚡ Deployment
Deployments for Private Fleet work exactly the same as regular cloud deployments, except you must specify a prioritized list of host IDs to deploy to.
Deployment will be started on the first private host in your list with sufficient resources.
If no private host has available capacity, deployment will Overflow to Cloud.
Overflow to Cloud
If your selected private fleet hosts don't have sufficient capacity at the time of deployment, your request will automatically use Server Score strategy and deploy to Edgegap Cloud.
To account for this possibility and prepare:
Read Resource Specifications injected variables to identify overflow case within deployment.
Cloud hosts may provide lower CPU frequency than private host Overdrive ☁️ Hardware, restrict player capacity or other CPU-intensive features in server to prevent bottlenecking.
Substitute missing private host beacon with one of the low latency cloud Ping Beacons.
Prepare for your deployment gracefully shutting down after 24 hours (max cloud lifetime).
Manage Persistence and Recovery Objectives to prevent data loss.
🔎 Discoverability
Find deployments running on private fleets and establish player sessions using Server Browser, or Filter Deployments to integrate a custom backend / third party solutions.
📢 Matchmaking integration under development, let us know about your needs!
Ping Beacons
Enable beacons for your fleet to automatically deploy and maintain highly-available Ping Beacons on each of your private hosts. Hosting beacons on the same machine as your deployments will provide the most precise ping measurement.
Last updated
Was this helpful?