Platform

What is Gameye?

Gameye is the orchestration layer between your matchmaker and your infrastructure. Your matchmaker decides when a match is ready. Gameye starts a server in 0.5 seconds. Players connect.

Last modified

Where does Gameye fit in your game stack?

Game pipeline diagram showing Game Clients connecting through Matchmaker (Pragma, Nakama, FlexMatch, Custom) to Gameye, which orchestrates across infrastructure providers (OVHCloud, GCore, Servers.com, AWS, GCP, Azure) to connect players

Gameye is the middle layer. Everything above it (your matchmaker, your game logic) and below it (the hardware, the network) stays the same. You're adding an orchestration layer, not replacing your stack.


What does Gameye replace?

The infrastructure work your team would otherwise own:

Provisioning cloud or bare metal servers
Configuring firewalls and networks
Writing Terraform or Ansible
Managing Docker runtimes on remote machines
Building custom autoscaling logic
On-call for infrastructure failures at 3 AM

Gameye replaces all of this with one API call: POST /session.

Before: complex web of infrastructure concerns including Kubernetes, firewalls, monitoring, alerting, and support. After: one API call — POST /session — and a single server container

What doesn't Gameye touch?

Gameye stays in its lane. Your game code is yours.

Your game server binary — no SDK, no plugin, no code changes
Your matchmaker — Gameye works with whatever you already use
Your networking model — Netcode, Mirror, Photon, custom UDP
Your client connection flow — players connect directly to the server
Your game engine — any engine works

How does it work?

1

Containerise your game server

Build a Linux dedicated server. Wrap it in a Dockerfile. Push to Docker Hub. Any engine works.

2

Configure in the Admin Panel

Set your image name, ports, networking mode, and deployment regions. Test-launch a container to verify.

3

Call the API

Your matchmaker calls POST /session with a region and your image name. Gameye returns the host IP and port in 0.5 seconds.

4

Players connect

Match starts. Gameye handles scaling, failover, DDoS protection, and teardown. You handle gameplay.


Who uses Gameye?

250,000
concurrent players at launch

Chivalry 2 by Torn Banner Studios. Zero downtime. Gameye scaled automatically.

60%+
server cost reduction

Clone Drone in the Danger Zone by Doborog Games. Switched to Gameye, eliminated egress fees.

Long-session
persistent game support

Orion Drift by Another Axiom. Runs long-session games on Gameye using the reserved rate.


Gameye by the numbers

120M+
sessions orchestrated
0.5s
container start time
21
infrastructure providers
200+
datacenters worldwide
99.99%
uptime SLA
$0.07
/vCPU/hr, zero egress

Platform data and methodology


Frequently asked questions

Do I need a Gameye SDK in my game server?

No. Gameye requires no SDK, plugin, or code changes in your game server binary. Your server runs as a Docker container — it starts, listens on a port, and accepts connections. Gameye manages everything externally via its REST API.

What game engines does Gameye support?

Gameye is engine-agnostic. Any server that compiles to Linux and fits in a Docker container works: Unreal Engine, Unity, Godot, Mirror, Photon Fusion, custom C++, Rust, Go. Full engine support list.

How much does Gameye cost?

$0.07/vCPU/hr on demand, $0.02/vCPU/hr reserved. No egress fees. Billing is per second with no minimum session length. Full pricing.

Which matchmakers work with Gameye?

Gameye is matchmaker-agnostic. Native integrations exist for Pragma Engine, Nakama, FlexMatch, PlayFab, and Photon Fusion. Any backend that can make an HTTP request also works. All integrations.

How is Gameye different from AWS GameLift or Edgegap?

Gameye requires no SDK (GameLift and Agones-based platforms require one). Gameye includes egress (GameLift charges per-GB). Gameye runs across 21 providers (GameLift is AWS-only). Full comparisons.


Key terms


Go deeper

Get started

Try Gameye free.
120 minutes, no credit card.

Sign up with Google, push your Docker image, and run your first session — before your next standup.

Sign up free