KeepWorlds

About us

Built in-house.
Automated end to end.

Launching a server, monitoring it, backing it up and keeping it up to date all run on software we wrote ourselves: the same fixed procedure every time, every step recorded and open to review. People step in where judgement is needed.

On record
Operator
Sichuan Tianfu New Area Chengdu Wan'an Kongdaolingjing Information Technology Services Studio

How we build and run it

Every layer of the platform is our own work: the backend that drives it, the agent installed on each server, the Console and this site. Orders, machines, saves and billing all move through one system, with the database as the single source of truth, rather than people copying data between third-party panels.

The goal in operations is to keep people out of the routine path: anything that can be written down as steps is done by software and leaves a record you can trace, and only the calls that need judgement go to a person. Every incident gets a post-mortem, and what it teaches us goes back into the code and the procedure instead of into somebody's memory.

One backend, end to end

Ordering, launching, renewing, restoring and refunding are states in a single chain, not a handful of tools stitched together.

Launches run themselves

Creating the dedicated machine, writing the config, starting the server and wiring up monitoring all happen automatically once payment clears.

Monitoring and auto-recovery

Frame rate and player counts are recorded every minute, and a crashed game process restarts itself in about 10 seconds. If a launch, update or restore fails, our team is alerted right away and follows up by hand.

Backups and Version guard

Saves are backed up on a schedule, restored in one click, and downloadable any time. New upstream builds are detected and flagged, and the save is backed up before any update.

How we write our guides

The guides on this site are written by the team that builds and runs KeepWorlds, out of what comes up running servers and helping the people who play on them.

Measured on servers we run

Frame rates, memory and file sizes quoted in a guide come from servers we operate, with the game version or date given. Where we have no data, the guide says so rather than guessing.

We sell hosting, and say so

Our guides mention our own service where it fits. The advice doesn't depend on buying it, and the self-hosting steps are complete without it.

Corrections

If something is wrong or out of date, email us and we'll fix it. A guide's Updated date moves only when its substance changes, not when a title is reworded.

What we provide, and what we don't

We don't operate, publish or sell games

We neither operate nor publish games, and we don't sell games or any in-game currency or items.

Bring your own copy

You need your own copy of the game.

What you pay is a technical service fee

What you pay is a technical service fee for the hosting and operation described in our Terms: deployment, startup, monitoring, and backups, all run automatically by our software, with game updates detected automatically and applied in one click.

Trademarks and copyright

Game names, trademarks, and artwork belong to their respective owners. We are neither affiliated with nor endorsed by them, and use their names only to identify the games we host.

Contact us

Questions before you order, trouble with a server, or a project to discuss: it all starts here. Creators, see the Creator program.