01 / PERSISTENT WORLDS
A world of your own.
For a survival server and the community that calls it home.
Keep it running.
See how it works- Persistent world lifecycle
- Snapshots and restore workflows
- Player records and staff permissions
Software for the worlds you build
Your world.
Your network.
Build worlds. Run the network. Manage your Hytale servers, players, and worlds from one place, on infrastructure you own.
BUILT FOR HYTALEOne world or a whole network.
World orchestrationPlayer managementConnected by designYour game servers
01 / THE TOOLKIT
One place to run
the whole network.
Servers, player tools, and connections.
Built to work together from the start.
A home for every world.
From a persistent survival world to a fleet of short-lived matches. Bring your game-server hosts, define your templates, and shape the capacity your network needs.
- Machines, templates, and fleet lifecycle
- Persistent worlds and snapshot workflows
- Match allocation and ready capacity
WORKSPACE RIFT CORE
Fleet overview
Network resourcesSample workspace
| Fleet | Workload | Desired state |
|---|---|---|
| survival-main | Persistent world | Running |
| skywars-eu | Match fleet | Ready buffer |
| lobby-eu | Shared lobby | Running |
Recent operations Example activity
Template publishedskywars@1.0.0
Ready for deploymentSnapshot verifiedsurvival-main
Restore point availableIllustrative preview. No live server is connected.
Keep your game hosts.
Choose where game-server workloads run. Riftworks operates the platform around them.
Know what changed.
Versioned templates and recorded operations, from release to recovery.
Connect your game.
Bring your game logic into the network with the bridge and SDK.
02 / BUILD ON YOUR TERMS
Start with a world.
Make room for more.
Bring the hosts that run your game.
Riftworks operates everything around them.
02 / MINIGAME NETWORKS
Room for the next match.
For lobbies, queues, and games that start when players are ready.
Build your network.
See how it works- Templates and match fleets
- Ready capacity and allocation
- Proxy integration and backend switching
03 / GROWING OPERATIONS
Your team, connected.
For operators coordinating regions, releases, and a wider team.
Run it together.
See how it works- Environment-scoped access
- Versioned releases and operations
- Shared network visibility
Planned release scope. Platform pricing will be announced before launch. Only your game-server hosting is billed separately.
A few things
to know.
Clear boundaries. Better foundations.
Is Riftworks a game server host?
Riftworks operates the platform around your network: control plane, proxy networking, player management, orchestration, operations, and more. You bring only the hosts that run the actual game-server workloads, and your provider bills that compute separately.
Can I run a single persistent world?
Yes, that is a target use case in Rift Core. Persistent worlds have their own lifecycle and snapshot workflows; matchmaking is not required.
Does backend switching keep players connected?
The planned custom hotswap retains the client connection to its owning proxy. A world transition may include a loading interval. It does not promise zero pause, arbitrary plugin-state continuity, or survival of a proxy-process failure.
Is the platform available today?
This site introduces the proposed product scope. Production availability, supported Hytale builds, and pricing will be published after the corresponding release gates are validated.