Skip to main content

2 - Create your Game Profile

Arbitrium is awesome to deploy your game server, where it's needed and when it's needed. To deploy a game server in our system, you need to create your first application/game server on the dashboard. You can do so by clicking on the “Applications” section of the navigation sidebar.

At this point, you will need a docker repository to deploy your game. You can find more information here. Get in touch with your Edgegap team to get help on how to containerize your game, and we have tools we can provide to help you on your way.

Click on the “Create New” button and create your game profile.


You will be prompted to fill a creation form. On this page, you will create a new application and the first version of it.

First, choose a name for your application. This name must be unique among all your applications. You also need to upload an image for your application. That’s all for the application information.

Then, you will need to fill up the version information. Versions are used so you can deploy multiple versions of the same app with different specifications.

You must specify a name, docker repository, Docker image, Docker tag, CPU Count, Memory and GPU. All other fields are optional and not required to make your application deployable. Note that the version name must be unique too among all versions of the application.

If your Docker repository is private, you will need to fill in the Private registry username and Private registry token. Optionally, you can enter environment variables and ports that might be required by your Docker containerized game. You can also integrate telemetry to your game server to have accurate data about every game played on this server.

You can define a max duration for your game. It means that if a deployment reaches the max duration, the system will terminate it automatically. Please note that if nothing is entered, the duration of a game server is infinite.

You can activate the caching system. We will ensure that your application is always cached on every location available. This will improve the deployment time of your application. You can specify a caching time between 0 and 23. By default, we will make sure that your app is cached, but if you make some live updates on your version, we will cache the new version between these 2 hours or at any time if not specified.

You can inject context into your deployment for that specific version. Refer to this for more details.

Once completed, click “Submit. “ That’s it!

You can see a JSON snippet of the request that we are sending to our backend. You can use it to create applications and application versions with an API request.

If you wish to test the API, follow the following example API Getting started.