Get started with game servers
A game server runs Minecraft: Java Edition, Terraria or Valheim for your players, on your workspace's private network with a public address to share. The console shows who is playing, sends commands to the server, browses its files and backs up its world.
Before you start
- A workspace role of Owner, Admin or Developer.
- Room in the workspace's quota for the size you pick. The Free plan's quota fits a Terraria server on Small; Minecraft and Valheim need Game 4 GB or larger.
1. Create the server
Open Game servers, choose New game server and pick a game. Then fill in:
- Server name, or World name for Terraria: 3 to 31 lowercase letters, digits and underscores, starting with a letter, such as
survival. - Password, under Configure credentials, for Minecraft and Valheim. Leave it blank to have a strong one generated. For Valheim it is the password players type to join.
- Network access: keep Public, so players can reach it.
- Plan: the size. Quota usage shows what it takes from the workspace's quota.
- For Minecraft, tick I accept the Minecraft EULA.
Select Create instance. The Provisioning tab follows each step until the server is Ready. A new Valheim server generates its world on its first start, which can take several minutes.
2. Invite players
Give players the Public address from the Connection card on the server's Overview, such as survival-7a1b.play.sahabti.app:40021. The port is the server's own, not the game's usual one, so players must include it:
- Minecraft: Multiplayer → Add Server, and the address with its port.
- Terraria: Multiplayer → Join via IP, then the hostname and the port.
- Valheim: Join Game → Add server, the address with its port, then the password.
3. Run it
- Game panel shows who is online and gives you the Server console, such as
whitelist add <player>on Minecraft. - Files browses the game's folder while the server runs: download, upload and delete files.
- Backups: Back up now archives the world and its settings, and a restore creates a new server from it.
- Network: limit who may connect with Edit allowed sources on the game's built-in rule.
With PromptOps
In a workspace with PromptOps on, ask in the chat. It asks before it creates or changes anything:
- "Create a Minecraft server called survival on Game 4 GB."
- "Back up survival before I install the update."
- "Restart survival."
- "Only let 203.0.113.0/24 join survival."
With the API or MCP
Create an API token with the instance actions, and save the server as server.json, with the game as engine and the size as plan:
{
"orgId": "<workspace id>",
"engine": "minecraft",
"name": "survival",
"plan": "game-4"
}
curl -X POST https://api.sahabti.com/v1/servers \
-H "x-api-key: $SAHABTI_TOKEN" \
-H "Content-Type: application/json" \
-d @server.json
Over MCP, create_instance takes the same fields and create_snapshot takes a backup. The server console is POST /v1/servers/{id}/console, in the API only.
What it costs
On Free and on a plan, a game server takes its size from the workspace's quota. On pay as you go, game servers are metered by the hour. See Plans and pay as you go and the pricing page.
First checks
- The server shows Ready, and you can join it with the Public address and its port.
- On Minecraft and Valheim, Game panel counts you among the players online.
- Backups lists a backup once you take one.
Next steps
- Game servers: sizes, the console commands, files, updates and what is not offered yet
- Backups: back up and restore a server's world
- Instance network: who may connect to your server