Why Host Abiotic Factor on the Flux Decentralized Cloud

Most game hosting runs in one company's datacentre. Flux is built differently: thousands of independently operated nodes across 50+ countries, with your server given dedicated resources on one of them and its saves kept on a standby.

One datacentre versus thousands of nodes

A traditional host concentrates risk: one facility, one network, one operator. A decentralized network has no such centre, so one node failing is a local event rather than an outage.

Your server runs on one node, and its worlds, settings and admins are synced to a standby node. If the node it runs on goes away, the standby starts with them, from the last sync. Like any crash, that costs what happened since the game's last autosave, up to 5 minutes.

You choose where it runs

The region is picked at deploy time from 50+ countries. Place the server near the people playing on it.

What stays completely normal

  • A management panel: start, stop, restart, settings, worlds, admins, files, a terminal and backups.
  • Your crew joins from the in-game server list, as on any Abiotic Factor server.
  • A conventional payment flow: card or USDC through Stripe, or FLUX through ZelCore or SSP.
  • Your worlds, downloadable at any time. Nothing is locked in.

Frequently asked questions

What happens to my world if a node fails?

It is synced to a standby node, which takes over from the last sync. The game autosaves every 5 minutes and cannot be told to save sooner, so a failure can lose up to 5 minutes of play, as any crash would.

Related Abiotic Factor guides