Engine Support

Any engine. No SDK.

Gameye doesn't care what engine your game uses. If your dedicated server compiles to Linux and fits in a Docker container, it runs on Gameye. No plugin, no SDK, no engine coupling.

Last modified

Why Gameye is engine-agnostic

Most game server platforms require an SDK in your server binary — lifecycle calls that tell the platform when your server is ready, when players connect, and when to shut down. Gameye doesn't. Gameye orchestrates at the container level, not the engine level.

Your server starts. It listens on a port. Players connect. Gameye handles everything else externally: session allocation, region placement, scaling, failover, and termination. No code runs inside your game server binary. No library to import. No API to call from your server process.

The only requirement: a Linux build of your dedicated server, packaged as a Docker image.


Supported engines and frameworks

Every engine and networking framework listed below has been run on Gameye in production or confirmed compatible. The list is not exhaustive — if it compiles to Linux, it works.

Unreal Engine

Dedicated page

UE4 and UE5 dedicated servers. Linux headless build, Dockerised, deployed via Session API. No UE plugin required. Chivalry 2 ran its 250,000-player launch on Gameye.

Unity

Dedicated page

Unity Dedicated Server build target. No Multiplay SDK, no Unity Gaming Services dependency. Works with Unity Matchmaker, Relay, and Lobby. Clone Drone in the Danger Zone runs on Gameye.

Godot

Godot 4 dedicated server exports to Linux. Package as a Docker image with your PCK file and deploy. No Godot-specific plugin or integration code needed.

Mirror Networking

Mirror dedicated servers compile to a standalone Linux binary via Unity. Containerise and deploy — Gameye orchestrates the process. No Mirror-specific SDK.

Fish-Networking

Fish-Net dedicated servers export as Linux standalones. Same Docker workflow — build, push, call the API. No Fish-Networking-specific integration layer.

PurrNet

PurrNet multiplayer servers build to Linux headless. Containerise and deploy on Gameye with the standard Docker + API workflow. No additional SDK.

Photon Fusion

Integration guide

Gameye is an officially documented hosting provider in Photon's own docs. Wrap your Fusion Dedicated Server in Docker and deploy via the Session API.

Photon Bolt

Photon Bolt supports server-authoritative dedicated servers. Clone Drone in the Danger Zone runs on Bolt with Gameye — Linux binary, Docker container, no Photon-specific hosting SDK. 60%+ cost reduction after switching.

Nakama (Heroic Labs)

Integration guide

Gameye has a native Nakama Fleet Manager integration. Nakama handles matchmaking; Gameye handles server allocation. Full session lifecycle support out of the box.

Custom C++ / C

If your studio builds its own engine in C or C++, the dedicated server compiles to a Linux ELF binary. Containerise it and deploy. Gameye doesn't inspect or modify your binary.

Rust

Rust game servers compile to a single static binary. Minimal Docker images (scratch or Alpine base), fast container starts. Ideal for Gameye's container model.

Go

Go game servers compile to a single binary with zero runtime dependencies. Docker images are tiny. Same workflow — build, push, deploy via API.


What your server needs

1. Linux build

Your dedicated server must compile to a Linux binary. Most engines support this via a headless or dedicated server build target. Windows containers are not supported.

2. Docker container

Package your Linux binary in a Dockerfile. Expose your game port. Push to Docker Hub. Gameye pulls the image and starts containers on demand. See the Dockerfile guide.

3. Port listening

Your server listens on its configured port (typically UDP 7777). In bridge mode, use EXPOSE in your Dockerfile. In host mode, read the port from the Gameye-injected environment variable GAMEYE_PORT_{protocol}_{containerPort}.

That's it. No Gameye SDK. No lifecycle callbacks. No engine plugin. Your server starts, listens, accepts players.


Frequently asked questions

Does Gameye support Godot dedicated servers?

Yes. Build your Godot dedicated server as a Linux binary, package it in a Docker container, and deploy via the Gameye API. No Godot-specific SDK, plugin, or integration code is needed.

Does Gameye support Mirror Networking?

Yes. Mirror dedicated servers compile to a Linux binary via Unity's Dedicated Server build target. Package in Docker and deploy on Gameye. No Mirror-specific SDK required.

Does Gameye work with custom game engines?

Yes. Any game server that compiles to a Linux binary and can be packaged as a Docker container works on Gameye. Custom C++, Rust, Go, or any other language.

Why doesn't Gameye need an engine SDK?

Gameye orchestrates at the container level, not the engine level. Your server starts, listens on a port, and accepts players. Gameye handles session allocation, placement, scaling, and lifecycle externally via its REST API. No code runs inside your binary.

What does my server need to run on Gameye?

A Linux build and a Dockerfile. Your server reads its port from Gameye-injected environment variables (host mode) or uses EXPOSE (bridge mode). That's the full integration surface.

Does Gameye support Photon Fusion?

Yes. Gameye is an officially documented hosting provider in Photon's own technical docs. See the Photon Fusion integration guide.


Missing an engine? Let us know and we'll confirm compatibility.

Get started with Gameye

Sandbox access in 24 hours.
Bring any engine.

Push your Docker image, call the API, run your first session — regardless of what engine you built it with.

Request your Gameye API key →