NewFleet Autoscale · Invite Only

Manage multiple game servers from one tab.

Fleet is multi-server management on your panel's home page, for official servers and community networks alike. Studios roll a patch out region by region. Communities run every server they own as one, with server groups, bulk actions and one live console.

Use what's already familiar to you, from the makers of Pterodactyl.

Hosting your game's official servers? Physgun for Studios
On Physgun servers
Free
Before every action
Preview
Ways to roll out
4
We host
Every game

Server groups that build themselves.

Make a server group per game mode, per region or per tournament, mixing games and locations, and give each one a color. Smart groups fill themselves by rule, so a new Rust server can join your Rust group on its own, and a server that gets busy shows up in "Busy Right Now" while it is.

  • Mix games and locations in one group
  • Smart rules on game, location, kind or name
  • Live rules on state, players, CPU, memory or disk
  • One server can be in several groups

Bulk actions on every server. Each one previewed.

Select a server group, a filter or every server you have, then act on all of them: restart multiple servers at once, back them all up, change a startup variable everywhere, or add a subuser to every server. Before anything runs, you see what will happen on each server and how many players get disconnected.

  • StartBring every selected server up.
  • StopShut them all down.
  • RestartRestart them, now.
  • KillForce-stop the ones that are stuck.
  • Restart When EmptyWaits until nobody's online, then restarts.
  • Run CommandOne console command, on every server.
  • BackupBack them all up in one go.
  • Change SettingEdit startup variables, with an optional restart after.
  • Update GameUpdate every server with its game's updater, or reinstall games that don't have one.
  • Push FileOne file to the same path on every server. Overwrite, skip, or back up what's there.
  • Add SubuserInvite someone by email with a preset, or update their access. It only grants what you hold.
  • Remove SubuserTake someone off every selected server.

Don't want to kick anyone? Restart When Empty waits for each server's last player to leave, then restarts it.

Roll out in waves, not all at once.

Patch staging and playtest first, then roll out one region at a time. Pick how a change spreads, cap how many servers go at once on each node, and let Halt on Failure stop a bad change before it reaches everyone. Watch every server live, retry what failed, and look back at every run.

  • All at onceEverything together, when speed matters.
  • In wavesA few at a time, so a bad change stops early.
  • One at a timeEach server finishes before the next starts.
  • By locationOne location per wave, in the order you choose.

Halt on Failure

  • After each wave, Fleet waits a settle time you pick.
  • It halts the run if a server failed, crashed or didn't come back up, or if players dropped more than you allow.
  • The rest are held and an alert goes to your alert destinations. Resume or cancel.

Trigger it from CI

An account API key can preview and start a Fleet run in one call, aimed at a group or smart group, then poll it. Ship a build, and your pipeline rolls it out to your official servers.

Invite OnlyFor studios' official servers

Fleet Autoscale. Scale on player load.

When players climb past a threshold, Fleet brings up more servers from a standby pool. When they drop, it winds the extra ones down once they're empty.

  • Brings up more servers from a standby pool when players climb past a threshold.
  • Winds the extra servers down once players drop and they're empty.
  • Built on Fleet's player-count rules, run history and alerts.

Send a command to every server. One live console.

Stream the console of every server you select, live, in one view, and dispatch one command to all of them at once. Perfect for the announcement before a restart, or a save across a Minecraft or Rust network.

  • Each server in its own color
  • One command, sent to all of them
  • A command palette that suggests as you type
  • Saved commands, ready to reuse

Restart multiple servers on a schedule.

Schedule any fleet action to repeat, see every schedule on one timeline, and check each run in its history.

  • Any fleet actionUpdate Game, Push File, Change Setting, Restart When Empty: any action, repeating, on a visual timeline. Run Once Now when you need it.
  • Full rollout optionsWaves, By Location, First servers and Halt on Failure. Badly overdue runs are skipped, never fired late.
  • Spread the loadSpread a schedule so your servers don't all restart in the same minute.
  • Maintenance windowsPlanned work? Pause schedules and alerts for a group, or your whole fleet, until it ends.

Monitor every server at once. Hear about it first.

Fleet-wide charts track player activity, CPU, memory and disk across every server, region by region, live for the last hour or back through your history. After a release, crashes and player drops land where your team already is.

Alerts for what matters

  • Server offline
  • Crashes
  • CPU, memory or disk over a threshold for a window
  • Player count drops

Sent to destinations like Discord webhooks, with every alert kept in its history. Each server also gets a metric card with its copyable connect address and a link straight to it.

Teams and startup variables, across every server.

Game server team management, done once: give staff, moderators and QA access to the servers they need, and lock startup variables so every server runs the same config.

Teams

Create a team, add your staff by email with a role (Read-Only, Operator, Full Access or Custom), and share groups with the whole team. Every member gets subuser access on those servers, kept in sync as members, roles and servers change. Access from several places combines, and members see the team and their own role. Or share one group with one person.

Locked fleet settings

Set startup variables once on a group. Locked ones are enforced on every server in it; unlocked ones are defaults a server can override. New servers in the group pick them up automatically.

Drive it with AI

Connect Claude or ChatGPT to your panel and run Fleet in plain language. Every action still shows its preview before it runs.

Compare every server. Catch the drift.

Pick a group or a selection and see every server's settings in one table. Server drift shows itself, and one click puts it right.

  • Game, image, version and every startup variable, side by side
  • Cells that differ from the group's settings or from the majority stand out
  • Make These Match fills in Change Setting; Lock in Group keeps it that way
  • Check File compares one file's hash across up to 25 servers
  • Values you can't read stay hidden, and secrets show only a fingerprint

Multi-server management, for studios and communities.

Whether it's your game's official servers or every server your community runs, it's the same tab doing two different jobs.

Game studios

Your game's official servers, in every region, patched without drama.

See What Studios Do
  • Patch staging and playtest first, then roll the update out region by region with By Location, seeing the players affected first.
  • Halt on Failure stops the rollout if a server fails or players drop, and holds the rest until you resume.
  • Trigger the rollout from your build pipeline with an account API key, and poll the run.
  • Ship a hotfix with Restart When Empty: each server restarts once its last player leaves.
  • Push a config or ban list to the same path on every official server.
  • Watch players by location, and get alerts on crashes and player drops after a release.
  • Put QA, community managers and moderators in teams with Read-Only or Operator roles.
  • Lock startup variables, and use Compare to catch any official server that drifted.
  • Open a maintenance window around a planned patch, pausing schedules and alerts.
  • Scale official servers on player load with Fleet Autoscale.Invite Only
Physgun for Studios

Communities and networks

Every game mode you run, every server in it, handled as one.

See What Communities Do
  • Server groups per game mode, plus smart groups that pick servers up by rule, like every server with players over a count.
  • Schedule any action: restarts spread across the night, or a weekly Update Game across the network.
  • Restart When Empty after a plugin update, with no one dropped mid-game.
  • Push a plugin or config to the same path on every server.
  • Send one command to every server from the live console, with a command palette and saved commands.
  • Add your staff to a team once with a role, and share the groups they run. Access stays in sync.
  • Add or remove a subuser across every server in one bulk action.
  • Lock startup variables, and use Compare to spot the server that drifted.
  • Send alerts on crashes and player drops to your staff Discord.
  • Open a maintenance window for a wipe or map change, and use the players heatmap to find a quiet hour.
Pick Your Game

Questions, answered

Managing multiple game servers with Fleet: bulk actions, commands, staff access, startup variables and what it costs.

Physgun

Open the Fleet tab on your panel's home page. Put your servers in server groups (or let smart groups fill themselves by rule), select a group, a filter or every server, and run a bulk action on all of them. Each one previews what happens on every server before it runs.

Yes. Restart, Start, Stop and Kill work across every selected server: all at once, in waves, one at a time, or By Location (one location per wave), with a limit per node and Halt on Failure to stop a bad change early. Restart When Empty waits until nobody's online, and a schedule can spread restarts so your servers don't all go down in the same minute.

Yes. Run Command sends one console command to every selected server, and the live fleet console streams all their consoles in one view, each in its own color, with a command palette and saved commands.

Make a team, add your staff by email with a role (Read-Only, Operator, Full Access or Custom), and share server groups with the team. Every member gets subuser access on every server in those groups, kept in sync as members, roles and servers change, and access from several places combines. You can also share one group with one person, or use the Add Subuser and Remove Subuser bulk actions across any selection.

Yes. Set startup variables once on a group. Locked ones are enforced on every server in the group, unlocked ones are defaults a server can override, and servers that join the group get them automatically. Change Setting also edits a startup variable across servers, with an optional restart after.

Yes. Create a team, add staff by email with a role (Read-Only, Operator, Full Access or Custom), and share Fleet groups with the whole team. Members get subuser access on the groups' servers, kept in sync as members, roles and servers change, and they see the team and their own role.

Turn on Halt on Failure for a wave or one-at-a-time rollout. After each wave Fleet waits a settle time (1 to 15 minutes) and halts if a server failed, crashed or didn't come back up, or, if you set it, players dropped more than a percentage. The remaining servers are held, an alert goes to your alert destinations, and you resume or cancel.

Yes. An account API key can preview and start a Fleet run in one call, aimed at a group or smart group, and poll the run; responses include a link to the run in the panel. Studios use it to roll a build out from their pipeline, for example a GitHub Actions step.

Yes. A schedule can run any Fleet action, Update Game included, with the same rollout options: waves, By Location, First servers and Halt on Failure. Run Once Now runs it straight away, and occurrences that are badly overdue are skipped rather than fired late.

Yes. Group your official servers by region, roll a patch out By Location (staging and playtest first, then one region per wave) with a preview of the players affected and Halt on Failure on, trigger it from CI with an API key, push a config or ban list to every server, open maintenance windows around planned patches, get alerts on crashes and player drops, and give QA, community managers and moderators Read-Only or Operator roles in a team. See Physgun for Studios for hosting your official servers.

With Fleet Autoscale, which is invite only. When players climb past a threshold, Fleet brings up more servers from a standby pool, and when they drop, it winds the extra ones down once they're empty. To request access, email sales@physgun.com.

Yes. Fleet works across every game we host, Minecraft included, so a network of servers can share groups, bulk actions, schedules and one live console, mixed with any other games you run.

Nothing extra. Fleet is included with your Physgun servers, in the Fleet tab on your panel's home page. It works across every game we host, and VMs show up too, for power actions.

Every bulk action opens with a preview of what happens on each server and how many players get disconnected. Roll it out in waves, one at a time or By Location, with a limit per node, and turn on Halt on Failure: after each wave Fleet waits a settle time, and halts the run if a server failed, crashed or didn't come back up, or players dropped more than you allow. The rest are held until you resume or cancel.

Yes. Connect Claude or ChatGPT to your panel and drive Fleet in plain language, like asking it to roll a patch out to your official servers. Every action still shows its preview before it runs.
Still stuck?

Bring the whole fleet.

Fleet comes with your Physgun servers at no extra cost, for every game we host. VMs join in too, for power actions.

Read the launch post