As an image, we describe the collection of files needed to run your game server. After uploading and pushing your files, our services are creating a Docker image to easily deploy your payload to machines all over the world.
A payload is a uniquely identifiable instance of a game server session currently running or previously running as a containerized service.
Our APIs payload endpoint allows spawning, updating, shutdown, reserving and unreserving payloads.
In your allocation, you configure a
free payload capacity. This is the desired amount of free resources to spawn payloads instantly.
In your allocation, you configure a desired amount of
unreserved payloads. These payloads are already running and ready for users to connect.
An allocation is a set of data and rules that describe how hardware resources and payloads should be managed by our scaler:
Basic information (free text name, regions, …)
Payload definition (which payload to use, how to start it up)
Payload quota (needed resources for one running payload like CPU, RAM, storage or network connectivity)
Scaling rules (how we should scale, so there are enough spare resources for you, but not too many lying around unused)
Our scaler is the heart of the orchestration service. With an allocation you set up, it scales to bare-metal, bare-metal on demand and common cloud providers (AWS, Azure, GCP). We call this feature Hybrid Cloud.
Hybrid Cloud gives your games the best value for your money. Depending on your current load different types of machine sources are used.
Bare-metal machines are concrete machines bound to one customer. They are highly optimized to run games. Hardware can be tailored to your needs.
These machines can be booked for at least one month.
zeuz has a pool of machines in every region, that is available to retort high loads. You can configure access to these machines by setting the max amount of bare-metal machines in your allocations scaling rules.
Machines used as bare-metal on demand are paid per hour or part thereof.
In peak times, when your bare-metal contingent and bare-metal on demand exceeds its capacity, we manage scaling into the cloud using your existing cloud setup with AWS, Azure or GCP.
Optimized for games
Customers per machine
Bare-metal on demand
Depends on Cloud provider (often minute-based)
Decided by provider. Mostly more than 1
Our matchmaking service is able to communicate with the scaler to automatically adjust allocations temporarily based on your real needs in the near future. Therefore using the combination of the orchestration and matchmaking is more than the sum of its parts.
You can easily set up zeuz matchmaking to talk to the orchestration
Updated 4 days ago