We offer a free evaluation environment where you can test your game sessions on Gameye. This environment is limited in capacity but is available in regions worldwide.
Everything you need to know about our company, platform, and setup.
We offer a free evaluation environment where you can test your game sessions on Gameye. This environment is limited in capacity but is available in regions worldwide.
Get in touch with us and tell us about your game and someone from our crew will get right back to you. We’ll walk you through the integration and give you support through our Discord.
Our approach doesn’t require an SDK. We use a container-based approach which means we can orchestrate any process as long as it runs on Linux. So we can run any server process whether it’s off the shelf or completely custom built.
We have an API endpoint which gives access to logs from a game server process run on Gameye. These are available for four hours after the container has finished.
We give our customers 24/7/365 support, plus we offer direct interaction with our support and integration team via Discord and Slack.
We’re 100% agnostic. So we work with any matchmaker. Even one you created yourself.
No. Gameye is infrastructure-agnostic. You can run Gameye on bare metal, virtual machines, cloud, or edge — or any hybrid combination. We also support bursting into cloud and edge capacity for effectively infinite scale, so you’re never locked into a single hosting model or provider and can always choose the setup that best fits your performance, cost, and operational needs.
Gameye uses capacity-based pricing — you pay for the compute resources you reserve, not for bandwidth or data transfer. There are no egress fees, no per-GB charges, and no surprise bills when your player base grows. Pricing is structured around vCPU and memory capacity across your chosen regions. Contact us for a quote tailored to your game’s session profile and expected concurrency.
No. All data transfer is included in Gameye’s capacity-based pricing. This is a fundamental difference from cloud providers like AWS GameLift, where egress fees ($0.09+/GB) can account for 40–60% of your total infrastructure bill for multiplayer games. With Gameye, your costs stay predictable as your player base grows.
Gameye starts new containers in 0.5 seconds on average. This compares to minutes for AWS GameLift fleet scaling and ‘under 2 minutes’ for Hathora node provisioning. The difference matters most during launch spikes, free weekends, and viral moments when thousands of players need matches simultaneously.
Game server orchestration is the automated management of dedicated game server instances — starting servers when players need matches, placing them in the right region, monitoring their health, and reclaiming them when sessions end. An orchestration platform like Gameye handles all of this through a single API, so your game client or matchmaker can request a server and receive a connection address in under a second, without any manual infrastructure management.
Gameye operates in major population centers across North America, Europe, Asia-Pacific, and South America. All regions run on premium bare metal infrastructure (Gcore, OVHCloud) with game-grade DDoS protection. Contact us for the current full region list — we regularly add capacity based on customer demand.
Yes. DDoS protection is built into every Gameye location — not bolted on as an extra fee. We run on infrastructure providers (Gcore and OVHCloud) who have spent years building game-specific DDoS mitigation. This is different from AWS Shield, which is designed for web applications and costs $3,000/month minimum on top of your compute bill.
Gameye is 100% matchmaker-agnostic. It works with any matchmaker — Nakama, AccelByte, GameSparks, PlayFab, open-source solutions, or a custom matchmaker you built yourself. Your matchmaker calls the Gameye API to request a server session, receives the connection details, and passes them to players. No vendor lock-in, no required middleware.
Most studios complete integration in days, not weeks. If your game server is already containerized (Docker), you can be running sessions on Gameye with minimal code changes — typically just replacing existing orchestration API calls with Gameye’s REST API. Our integration team provides hands-on support through Discord and Slack throughout the process.
Yes. Gameye works with any game engine. Because we use a container-based approach, we orchestrate the server process itself — not an engine-specific SDK. Whether your dedicated server is built in Unreal Engine, Unity, Godot, or a custom engine, if it runs on Linux it runs on Gameye. No engine-side integration or plugin required.
Yes. Gameye works with any containerized game server. If you’re on GameLift, your server binary gets packaged into a Docker container and deployed to Gameye. For Agones, your existing container images work with minimal changes — you swap SDK calls for Gameye’s API. Studios typically run both platforms in parallel during migration, shifting traffic region by region. Our team supports the full migration process.
Yes. Gameye integrates with your existing setup — you can run it in parallel with AWS, your own servers, or another orchestration platform. Many studios start by directing traffic for a single region or game mode to Gameye while keeping existing infrastructure running, then migrate progressively once they’ve validated performance and costs.
Notable titles include Chivalry 2 (Torn Banner Studios), which launched with 250,000 concurrent players in the first 30 minutes with zero downtime; Clone Drone in the Danger Zone (Doborog Games), which reduced server costs by over 60% after switching; and games from Tripwire Interactive, Remedy Entertainment, and Oddshot Games. Gameye has orchestrated over 120 million game sessions since 2019.
Gameye maintains 99.99% uptime across its platform. We’ve run over 120 million game sessions since 2019, including high-profile launches with hundreds of thousands of simultaneous players. Multi-provider infrastructure means if one provider has issues, sessions automatically fail over — games stay online without manual intervention.
Yes. Gameye supports any network protocol your game server uses — UDP, TCP, WebSockets, or custom protocols. Our bare metal infrastructure is optimized for the low-latency, high-throughput traffic patterns of real-time multiplayer games, and DDoS protection covers UDP floods which are the most common attack vector for game servers.
Gameye was founded in 2017 and is headquartered in Rotterdam, Netherlands. We’ve been running production game infrastructure since 2019 and have supported over 120 million game sessions. As an independent, games-focused company, our entire roadmap and engineering are dedicated to multiplayer game infrastructure — no side businesses, no pivots.
No. Game servers must run in Linux Docker containers. Windows-based containers are not currently supported. Most game engines — Unreal Engine, Unity, Godot — can produce Linux dedicated server builds alongside their Windows builds. If your server only targets Windows today, you’ll need to add a Linux build target before integrating with Gameye. There are no language or runtime restrictions beyond the Linux requirement: C#, C++, Go, Rust, Java, and any other language that runs in a Linux container is supported.
Gameye supports Docker Hub (the most common option) and Amazon ECR. Other registries are supported on request — contact us if you’re using a different registry. Gameye integrates directly with your registry and preloads images onto its infrastructure automatically. You push once to your registry and Gameye handles distribution globally — you never push images directly to Gameye. Each application supports up to 5 image tags simultaneously; when a new tag is pushed beyond the cap, the least recently used tag is replaced.
Gameye force-terminates the container the moment the TTL (Time to Live) expires. Billing stops at termination. The shutdown is immediate — there is no graceful shutdown signal before the TTL fires. If you need to preserve state such as match results or save files, use the artifacts API to retrieve files before the TTL is reached, or write to external storage from within the session. For development and testing, setting a short TTL (e.g. 600 seconds) prevents containers from running indefinitely if you forget to clean up.
Gameye is optimised for session-based multiplayer games — one match, fixed duration. Long-lived sessions work on the platform. Session-based autoscaling (scaling container inventory based on active player counts within running sessions) is shipping in March 2026. For most games with matches under a few hours, Gameye works without issue. Contact us if you’re unsure whether your use case is a good fit.
