If You're on Hathora, Your Matchmaker Should Choose Your Next Platform

The Integration Gap That Changes Everything

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 tells the server platform to spin up a game. That handoff is the most latency-sensitive moment in your entire player experience. It's also the integration that breaks when you change platforms.

For Pragma Engine, Nakama, and Idem.gg studios, the choice is clear: Gameye has documented, production-tested integrations for all three; GameFabric has none. FlexMatch is the one area where GameFabric has published documentation — Gameye supports it too, but it is not publicly documented. Contact us for setup details.

If your game uses Pragma, Nakama, or Idem.gg today, Gameye is a drop-in. GameFabric requires a rebuild from scratch.

The Pragma Case: An Official Plugin, Not a Workaround

Pragma Engine is the backend platform of choice for studios that want production-grade matchmaking, party formation, social systems, and live ops without building it all from scratch. If you're on Hathora with Pragma today, your stack works like this:

1. Players queue for a match
2. Pragma handles party formation and matchmaking logic
3. Pragma's Gameye Capacity Provider plugin instructs Gameye to spin up a dedicated server
4. Pragma sends the server IP and port to the players' clients
5. Match starts

The Gameye integration lives inside Pragma's own codebase as an official ServerProviderPlugin — it's not a third-party connector or a community hack. It shipped as part of Pragma Engine 2025.2. No equivalent GameFabric plugin exists in Pragma's codebase.

The Nakama Case

Nakama is a popular open-source game backend for studios who want real-time multiplayer, social features, leaderboards, and matchmaking under one roof. Gameye's native Nakama Fleet Manager integration means the full loop runs without custom glue code on your side. GameFabric has no Nakama integration — migrating means writing and maintaining that connection yourself.

A Note on FlexMatch

FlexMatch (AWS) is the one matchmaker where GameFabric has the stronger public documentation. Gameye supports FlexMatch, but the integration is not publicly documented — reach out to our team and we'll walk you through the setup. If FlexMatch is your primary matchmaker and public documentation is a hard requirement today, that's a fair point in GameFabric's favour. For Pragma, Nakama, and Idem.gg studios, the decision is straightforward.

The Idem.gg Case: A Third Party Already Chose

Idem.gg is a skill-based matchmaker that publishes a dedicated integration page for each game server platform it supports. Those platforms are: Gameye, Edgegap, i3D.net, and GPortal. GameFabric is not listed.

This is a third party — not Gameye's marketing team — that evaluated the ecosystem and built a native integration with Gameye. The full integration docs live at docs.idem.gg/gameye/, covering API token setup, regional server launch, and player connection handoff. If your studio uses Idem.gg for skill-based matchmaking, Gameye is the only platform on this page with a documented path forward.

Gameye at a Glance

Gameye vs. GameFabric: Direct Comparison

For a broader look at how Gameye compares to other platforms on the market, see the Gameye vs. Hathora full comparison.

Total Cost of Ownership: What "Managed K8s" Still Requires From Your Team

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.

The Agones SDK requirement is the most material cost. Your game server binary must implement three lifecycle calls — sdk.Ready() on startup, sdk.Allocate() when players connect, sdk.Shutdown() on teardown — for the orchestrator to manage it correctly. A missed or mistimed call produces sessions the orchestrator believes are broken, or servers that never deallocate. Getting this right requires dedicated testing, and maintaining it means the Agones lifecycle is in scope for every future game server build.

The scaling model difference compounds over time. ArmadaSets pre-provision a standing fleet to avoid cold starts — those servers sit idle between matches, accruing compute cost. Gameye bills per second on active sessions only. For games with variable concurrency or pronounced off-peak troughs, the gap in effective compute spend can be significant before accounting for any other factor.

The sum — SDK integration, fleet tuning, custom matchmaker connectors, and idle capacity overhead — represents a real engineering and operational investment that doesn't appear in a vCPU/hour comparison. It's the cost that outlasts the migration.

Use Gameye If... / Use GameFabric If...

Frequently Asked Questions