Atlas server hosting for your own pirate world
Run your own ATLAS ocean for a crew or a whole community. An ATLAS world is a grid of linked servers, one per cell, joined by a Redis database, so ships sail from one cell to the next without a loading screen.
- Official ATLAS dedicated server for Windows and Linux
- Grids of linked servers built with ServerGridEditor
- Redis keeps players, ships and claims in sync
- Steam Workshop mods for unofficial worlds
- WorldServerGridEditor exports ServerGrid.json; each cell starts as its own ShooterGameServer with ServerX and ServerY.
- A grid of servers, one per cell
- DatabaseEvery grid needs Redis. A Windows build comes with the server tools; set your own Redis password.
- Redis
- PlayersThe official example starts a cell with MaxPlayers=100 and ReservedPlayerSlots=30.
- MaxPlayers per cell
- PortsThe official example uses Port=5761 and QueryPort=57561; SeamlessIP must be the public address.
- Game and query port per cell
- Mods
- Steam Workshop
- Server
- Steam app 1006030, Windows and Linux
Building blocks
- ServerGridEditor
- Redis
- ServerGrid.json
- Home servers
- Steam Workshop
- SeamlessIP
Game facts from Grapeshot Games’ ServerGridEditor wiki, the ATLAS Steam store page and SteamCMD data, checked in October 2026.
- DDoS protection
- 20 game server locations
Atlas plans are being prepared
Tell us how many grid cells you want and how many players will sail, and our team will reply with the options. Or open a ticket and we will let you know when the plans are online.
How big should an Atlas grid be?
Each grid cell is a full server process, so plan per cell. Small crews often start with a 1×1 or 2×2 grid.
Find your size
| Feature |
Single cell
1×1 grid, up to 20 players
|
Recommended Small grid
2×2 grid, up to 50 players
|
Large grid
3×3 or bigger
|
|---|---|---|---|
| Memory (RAM)Each cell is its own ShooterGameServer, plus memory for Redis. | 8 GB | 24 GB | 6 GB per cell+ |
| CPU coresEvery cell simulates its own part of the ocean, so give each cell its own fast core. | 2 | 6 | 1–2 per cell |
| Disk spaceOne server install of about 35 GB serves all cells; each cell adds its own saves. | 50 GB | 60 GB | 80 GB+ |
| Grid cellsServerGridEditor sets the grid size; the wiki advises keeping a cell’s gridSize at or below 1,400,000 units. | 1 | 4 | 9+ |
| Typical use | A crew on one island cell | A small community ocean | A large world with many home servers |
-
Single cell
1×1 grid, up to 20 players
- Memory (RAM)Each cell is its own ShooterGameServer, plus memory for Redis.
- 8 GB
- CPU coresEvery cell simulates its own part of the ocean, so give each cell its own fast core.
- 2
- Disk spaceOne server install of about 35 GB serves all cells; each cell adds its own saves.
- 50 GB
- Grid cellsServerGridEditor sets the grid size; the wiki advises keeping a cell’s gridSize at or below 1,400,000 units.
- 1
- Typical use
- A crew on one island cell
-
Recommended
Small grid
2×2 grid, up to 50 players
- Memory (RAM)Each cell is its own ShooterGameServer, plus memory for Redis.
- 24 GB
- CPU coresEvery cell simulates its own part of the ocean, so give each cell its own fast core.
- 6
- Disk spaceOne server install of about 35 GB serves all cells; each cell adds its own saves.
- 60 GB
- Grid cellsServerGridEditor sets the grid size; the wiki advises keeping a cell’s gridSize at or below 1,400,000 units.
- 4
- Typical use
- A small community ocean
-
Large grid
3×3 or bigger
- Memory (RAM)Each cell is its own ShooterGameServer, plus memory for Redis.
- 6 GB per cell+
- CPU coresEvery cell simulates its own part of the ocean, so give each cell its own fast core.
- 1–2 per cell
- Disk spaceOne server install of about 35 GB serves all cells; each cell adds its own saves.
- 80 GB+
- Grid cellsServerGridEditor sets the grid size; the wiki advises keeping a cell’s gridSize at or below 1,400,000 units.
- 9+
- Typical use
- A large world with many home servers
Grapeshot publishes no hardware figures. These starting points are derived from the 35 GB server install and the one-process-per-cell design; busy cells need more.
Grids, Redis and mods
An ATLAS world has more moving parts than most game servers. Here is what each one does.
ServerGridEditor
Grapeshot’s editor draws your ocean, islands and grid, then exports ServerGrid.json and ServerGrid.ServerOnly.json for the servers.
Redis
All cells share one Redis database through DatabaseConnections. Use a custom Redis password.
One server per cell
Start each cell with its coordinates, for example Ocean?ServerX=1?ServerY=0, plus its own ports and AltSaveDirectoryName.
Seamless travel
Set SeamlessIP to the public address so players and ships can cross from cell to cell.
Home servers
Mark the cells where new players may start, or use -ForceAllHomeServer to let every cell be a home server.
Workshop mods
ATLAS supports the Steam Workshop, and unofficial ATLAS mods can be of any size and configuration.
Set up your Atlas world
Four steps from an empty chart to your first voyage.
-
Design the grid
Draw the ocean in ServerGridEditor, pick the number of cells and size the server with the table above.
-
Pick a location
Choose the one closest to your crew from our 20 game server locations.
-
Start Redis and the cells
Run Redis with a password, then start one server per cell with its coordinates, ports and SeamlessIP.
-
Set sail
Find your world among the unofficial servers and pick a home server to start on.
Other game servers you might like
ARK: Survival Ascended
Crossplay worlds with CurseForge mods, clusters and your own rates.
Learn moreFrequently asked questions
Can I still host ATLAS?
Yes. ATLAS is still sold on Steam, and the ATLAS Dedicated Server (Steam app 1006030) is available for Windows and Linux. Its public branch was last updated in May 2023, so plan with the current version and do not expect frequent server updates.
Why does an ATLAS server need Redis?
Every cell of the grid is its own server. Redis is the shared database that keeps players, ships and claims consistent across cells. Grapeshot’s tools include a Windows Redis build, and newer Redis versions run on Linux.
How do I build my map?
With ServerGridEditor, an example editor from Grapeshot Games. It exports ServerGrid.json and ServerGrid.ServerOnly.json; give your world a unique WorldAtlasId and keep gridSize at or below 1,400,000 units.
How many players can a cell hold?
You set it per cell with MaxPlayers. Grapeshot’s example starts a cell with MaxPlayers=100 and ReservedPlayerSlots=30; actual limits depend on the hardware of each cell.
Which ports does each cell need?
Each cell gets its own game port and query port, as in the official example Port=5761 and QueryPort=57561. Set SeamlessIP to the public address, not an internal one.
What is a home server?
A cell where new players can create their character and start. Choose them in ServerGridEditor, or start the cells with -ForceAllHomeServer to make every cell a home server.
Can I use mods?
Yes. ATLAS supports the Steam Workshop, and the store page notes that unofficial ATLAS mods can be of any size and configuration.
Do I need a big grid for a small crew?
No. A single cell or a small 2×2 grid is enough for a crew, and you can add cells later. For playing with up to eight friends without a server, the game also offers non-dedicated sessions.
Ready to chart your own ocean?
Tell us your grid size and players, and we will help you plan the right Atlas world.