Hathora Migration: Gameye vs GameFabric for Studios Moving On

Hathora shuts down May 5, 2026. Compare Gameye vs GameFabric — matchmaker integrations, SDK requirements, pricing, and infrastructure.

Roberto Sasso
CTO at Gameye

By Roberto Sasso, CTO at Gameye · · Updated

Hathora’s game server hosting platform shuts down May 5, 2026. Hathora’s recommended migration path is GameFabric by Nitrado. Gameye is the other main option. Both are container-based platforms, but they differ in matchmaker integration depth, SDK requirements, pricing model, and infrastructure approach.

This post compares the two so you can make an informed decision based on your stack.


The matchmaker question

Your game server platform sits downstream of your matchmaker. That handoff — from “match ready” to “server running” — is the most latency-sensitive moment in your player experience. It’s also the integration most likely to break when you change platforms.

MatchmakerGameyeGameFabric
Pragma EngineOfficial ServerProviderPluginNo documented integration
NakamaNative Fleet Manager integrationNo documented integration
AWS FlexMatchDocumented integrationDocumented integration
Custom / homebrewREST API — any matchmakerHTTP allocator API

If your game uses Pragma or Nakama, Gameye has native integrations that handle the allocation handoff without custom code. GameFabric’s path for these matchmakers requires building a custom connector. Both platforms support FlexMatch and custom matchmakers.

The Pragma case

Pragma Engine lists its supported game server platforms in its own documentation: Amazon GameLift, Multiplay, and Gameye. Gameye ships as an official ServerProviderPlugin — migrating means updating your Capacity Provider config, not rebuilding matchmaking architecture.

The Nakama case

Gameye implements Nakama’s Go runtime Fleet Manager interface natively. If you’re on a Hathora + Nakama stack, Gameye is a drop-in replacement for the server allocation layer.


SDK requirements

Gameye requires no SDK in your game server binary. Your server runs as a Docker container — it starts, listens on its port, and accepts connections. Gameye manages session lifecycle server-side.

GameFabric is built on Agones, which requires sdk.Ready(), sdk.Allocate(), and sdk.Shutdown() lifecycle calls in your game server binary. This is code in scope for every future build.

Hathora also required its SDK for server lifecycle. If you move to Gameye, you remove the Hathora SDK and don’t replace it. If you move to GameFabric, you replace it with the Agones SDK.


Direct comparison

GameyeGameFabric
Game server SDKNone requiredAgones SDK in every build
Pragma EngineOfficial pluginNo documented integration
NakamaNative Fleet ManagerNo documented integration
FlexMatchDocumentedDocumented
Infrastructure21 providers, 200+ datacentersNitrado network, 67+ locations
Container start time0.5 secondsNot published
Pricing$0.07/vCPU/hr, no egressNot published — sales consultation
Uptime SLA99.99%Not publicly stated
DDoS protectionGame-aware profiles across all providersSteelShield (proprietary)
ObservabilityReal-time log streaming, Admin Panel, 3 months retentionGrafana + eBPF profiling
FailoverAutomatic cross-providerSingle network (Nitrado)
OnboardingSandbox in 24 hoursDemo + consultation required
Sessions at scale120M+ sessions, 1M peak CCU80+ games on platform

Infrastructure and pricing

Gameye runs across 21 infrastructure providers and 200+ datacenters on bare metal and cloud. GameFabric runs on Nitrado’s own network across 67+ locations — a vertically integrated approach that simplifies their operations. Both models have trade-offs: Gameye offers more provider flexibility and cross-provider failover; GameFabric offers a single, integrated network.

Gameye publishes pricing at $0.07/vCPU/hr with no egress fees. GameFabric’s pricing page states “Individual Pricing — Tailored to Your Unique Needs” and requires a sales consultation. Studios evaluating both can model Gameye costs immediately.

GameFabric offers Grafana dashboards with eBPF-based profiling — genuine kernel-level performance visibility that’s a strength of their stack. Gameye provides real-time log streaming during active sessions with 3 months retention in the Admin Panel.


When to choose each platform

Choose Gameye if you need:

Consider GameFabric if you have:


The migration window

Hathora shuts down May 5, 2026. Both Gameye and GameFabric are container-based — your Docker images transfer. The difference is what else changes: with Gameye, you remove the Hathora SDK and don’t replace it. With GameFabric, you replace it with the Agones SDK.

If you’re on Pragma or Nakama, Gameye has the native integration. If you’re on FlexMatch, both platforms support it. If you’re using a custom matchmaker, both platforms offer an HTTP/REST allocation endpoint.

Sandbox access in 24 hours. No sales call required. Request your Gameye API key.


Related: Gameye vs GameFabric — full comparison · Gameye vs Hathora · Hathora migration guide — all options · FlexMatch + Gameye integration guide


Frequently asked questions

When does Hathora shut down? Hathora’s game server hosting platform shuts down May 5, 2026. The team is joining Fireworks AI. Studios need a migration plan before the deadline.

Does Gameye require an SDK like Hathora did? No. Hathora required its SDK for server lifecycle management. Gameye requires no SDK in your game server binary — remove the Hathora SDK and don’t replace it.

Which matchmakers does Gameye support that GameFabric doesn’t? Gameye has native integrations with Pragma Engine (official ServerProviderPlugin) and Nakama (Fleet Manager interface). GameFabric has no documented integration with either. Both platforms support FlexMatch and custom matchmakers via REST.

Does Gameye charge egress fees? No. Gameye includes all bandwidth in its per-vCPU-hour pricing. Hathora charged per-GB egress on top of compute. GameFabric’s egress model depends on the underlying Kubernetes provider.