Platform Comparison
Gameye vs. GameFabric
Native matchmaker integrations vs. engineering overhead. Here's what the decision actually comes down to.
Purpose-built game server orchestration. Native integrations with Pragma Engine, Nakama, PlayFab, and FlexMatch. $0.07/vCPU/hr, no egress fees, 99.99% SLA. Provider-agnostic. Sandbox in 24 hours.
Kubernetes-based game server hosting built on Agones, running on Nitrado's global network (67+ locations). No documented integration with Pragma Engine or Nakama. Documented FlexMatch integration. Pricing on request.
The matchmaker question decides the platform
Your game server platform doesn't run in isolation. It sits downstream of your matchmaker — the system that decides when a match is ready and requests a server. That handoff is where platform choice becomes concrete. This comparison focuses on Pragma Engine, Nakama, and Idem.gg, where the distinction is sharpest.
| Matchmaker | Gameye | GameFabric |
|---|---|---|
| Pragma Engine | ✓ Official ServerProviderPlugin (2025.2) | ✗ No plugin in Pragma codebase |
| Nakama | ✓ Native Fleet Manager integration | ✗ No documented integration |
| AWS FlexMatch | ⚠ Available — contact for details | ✓ Documented integration |
| Idem.gg (skill-based) | ✓ Native integration (docs.idem.gg/gameye/) | ✗ Not a listed provider |
| Custom / homebrew | ✓ Platform-agnostic | ⚠ HTTP allocator, custom integration |
The Pragma case is the clearest. Gameye ships as an official ServerProviderPlugin inside Pragma Engine 2025.2. Migrating to Gameye means updating a Capacity Provider config — not rebuilding your matchmaking architecture. No equivalent GameFabric plugin exists in Pragma's codebase.
Idem.gg, a skill-based matchmaker with a native Gameye integration, has published a dedicated integration page at docs.idem.gg/gameye/. GameFabric is not listed as a supported server provider in Idem's documentation. If your studio is evaluating or already using Idem.gg for skill-based matchmaking, Gameye is the only platform with a documented path.
A note on FlexMatch
FlexMatch is the one area where GameFabric has the stronger public documentation. Gameye supports FlexMatch but the integration is not publicly documented — reach out and we'll walk you through setup. If FlexMatch is your primary matchmaker and public documentation is a hard requirement today, that's a legitimate point in GameFabric's favour.
Total cost of ownership: the application layer overhead
GameFabric manages the Kubernetes cluster — studios don't operate nodes or handle cluster upgrades. But managed infrastructure doesn't mean zero engineering overhead. The cost is at the application layer, and it's ongoing.
| Engineering cost | Gameye | GameFabric |
|---|---|---|
| Game server SDK | None required in game server binary | Agones SDK — must implement sdk.Ready(), sdk.Allocate(), sdk.Shutdown() in every build |
| Fleet configuration | Managed by Gameye | ArmadaSets and FleetAutoscalers — studio-defined scaling rules, ongoing tuning required |
| Matchmaker integration | Pragma and Nakama native. FlexMatch available — contact for setup details | Pragma and Nakama undocumented. FlexMatch documented |
| Scaling cost model | Per-second billing on active sessions — zero idle capacity cost | ArmadaSets pre-provision capacity — idle servers accrue cost between sessions |
| Image and registry | Docker Hub + webhook | Separate registry service, webhook configuration, per-environment image tag management |
| Time to first session | Sandbox in 24 hours | Demo + consultation + ArmadaSet config + SDK integration |
The Agones SDK requirement is the most material ongoing cost. Your game server binary must call sdk.Ready() on startup, sdk.Allocate() when players connect, and sdk.Shutdown() on teardown. A missed or mistimed call produces sessions the orchestrator believes are broken, or servers that never deallocate. This is code in scope for every future game server build.
The scaling model compounds over time. ArmadaSets pre-provision a standing fleet to avoid cold starts — those servers sit idle between sessions, accruing compute cost. Gameye bills per second on active sessions only. For games with variable concurrency or off-peak troughs, the gap in effective compute spend is real before accounting for any other factor.
Direct comparison
| Criteria | Gameye | Nitrado GameFabric |
|---|---|---|
| Pragma Engine | ✓ Official ServerProviderPlugin | ✗ No plugin in Pragma codebase |
| Nakama | ✓ Native | ✗ No documented integration |
| AWS FlexMatch | ⚠ Available — contact for details | ✓ Documented integration |
| Game server SDK required | No | Yes — Agones SDK in every build |
| Fleet management | Managed by Gameye | Studio-configured ArmadaSets |
| Infrastructure | Provider-agnostic — cloud, bare metal, or your own accounts | Runs on Nitrado's global network (67+ locations) |
| Container start time | 0.5 seconds | Not published |
| Pricing | $0.07/vCPU/hr, publicly stated, no egress fees | Custom quotes — contact required |
| Uptime SLA | 99.99% — publicly stated | Not publicly stated |
| Scaling billing | Per second, active sessions only | Pre-provisioned fleet — idle capacity billed |
| Onboarding | Sandbox in 24 hours | Demo + consultation required |
| Sessions at scale | 120M+ sessions, 1M peak CCU | 80+ games on platform |
When to choose each platform
- Pragma Engine — official ServerProviderPlugin, update a config not a rebuild
- Nakama — native Fleet Manager integration, no custom code
- Idem.gg — dedicated integration, no equivalent GameFabric path
- No Agones SDK changes to your game server binary
- Per-second billing with no idle fleet overhead
- Publicly stated pricing you can model before a sales call
- Provider-agnostic infrastructure — not tied to one network
- A sandbox running in 24 hours
- No existing Pragma or Nakama matchmaker to preserve
- FlexMatch as your primary matchmaker — GameFabric has the public docs
- An existing Agones or Kubernetes-based workflow
- Existing infrastructure within Nitrado's network
Frequently asked questions
Does GameFabric support Pragma Engine?
No documented integration exists. Gameye ships as an official ServerProviderPlugin inside Pragma Engine 2025.2. Updating your Capacity Provider config is all that's required. No equivalent GameFabric plugin exists in Pragma's codebase.
Does GameFabric support Nakama or PlayFab?
No documented integration has been found in GameFabric's documentation or in Nakama's and PlayFab's documentation. Gameye provides native integrations with both out of the box.
Does GameFabric support Idem.gg?
No. Idem.gg publishes a dedicated Gameye integration page at docs.idem.gg/gameye/ covering API token setup, regional server launch, and player connection flow. GameFabric is not listed as a supported provider in Idem's documentation. If your studio uses Idem.gg for skill-based matchmaking, Gameye is the only platform with a documented integration path.
Does GameFabric support FlexMatch?
Both platforms use an AWS Lambda to bridge FlexMatch — but Gameye publishes a pre-built Gameye FlexMatch Bridge to the AWS Serverless Application Repository (SAR). Studios open the AWS console, find the app, enter their API token and image name, and click Deploy. No code written, no CLI required. GameFabric's documented pattern requires studios to author the Lambda themselves — subscribing to SNS MatchmakingSucceeded events, calling the allocator, re-emitting enriched events. That code is your team's to write and maintain indefinitely.
What engineering overhead does GameFabric require?
GameFabric is built on Agones, so your game server binary must implement three lifecycle calls: sdk.Ready(), sdk.Allocate(), and sdk.Shutdown(). You also configure and tune your own ArmadaSets (fleet scaling rules) and pre-provision idle capacity to avoid cold starts. Gameye manages session lifecycle server-side — no SDK integration is required in your game server binary.
How does GameFabric pricing compare to Gameye?
Gameye publishes pricing publicly: $0.07/vCPU/hr with no egress fees and a publicly stated 99.99% SLA. GameFabric does not publish pricing — a sales consultation is required before you can model costs. GameFabric's uptime SLA is also not publicly stated.
Is GameFabric a fully managed platform?
GameFabric manages the Kubernetes cluster infrastructure — studios don't operate nodes or handle cluster upgrades. However, the application layer still requires significant engineering: Agones SDK integration in your game server binary, ArmadaSet configuration and fleet tuning, and custom matchmaker connectors where no native integration exists.
Get started with Gameye
Sandbox access in 24 hours.
No sales call required.
Run your first sessions, validate performance, and confirm your matchmaker integration — before you commit to anything.
Request your Gameye API key →Want to model costs first? Use the pricing calculator →