Blog
Matchmaking Without the Black Box: Pairiquium vs FlexMatch, Unity Matchmaker, Open Match and Nakama
An honest comparison of Pairiquium with Amazon GameLift FlexMatch, Unity Matchmaker, Open Match and Nakama: what each does well, what it costs and when to pick something else.
Published Last checked
I'm a senior software engineer, and I remember what it was like before I was. Cloud infrastructure felt like a black box with a bill attached. You never quite knew what you were paying for until the invoice arrived, and "just spin up a backend" was advice from people who already knew how.
Indie game developers are in that position today. You want players to find each other. You don't want to learn queue design, WebSocket gateways and autoscaling to make it happen, and you definitely don't want a surprise bill. That's why I built Pairiquium.
This post explains what Pairiquium is good at, and just as importantly, when you should pick something else.
What Pairiquium is
Pairiquium is a hosted matchmaking backend. You keep your own game servers. We run the queues, form the matches and tell your backend who is playing together.
The integration is deliberately small:
- Your backend asks Pairiquium for a short-lived ticket for a player. Your API key stays on your server and never ships in a game build.
- The game client uses the ticket to open a WebSocket and starts a search.
- When a match forms, the client is told it has a match, and your backend receives a signed webhook with the full player list.
With the Unity SDK you only hook the moments your game cares about: start matching, match found, cancel search (and more). The web API covers everything the SDK does (the SDK uses it underneath), so any engine can integrate. The SDK is also open source, so it is built to be tweaked, verified and adapted if you need or want to.
Where Pairiquium is strong
Fast to a first working match. Mint a ticket, connect, search, handle the webhook. You are integrating, not designing infrastructure.
Matching you control per game mode. Each mode picks one algorithm:
- Skill (MMR). You store ratings; you pass the player's MMR when you create the ticket, so there's no rating system to adopt or migrate to. You set a base tolerance and an expansion multiplier. The allowed MMR gap grows continuously the longer a player waits, so a strict ranked mode and a quick casual mode are just two settings apart. For example, over a 0–3000 range with a base of 5% and a multiplier of 2, the allowed gap is 150 points at the start, 300 after 10 seconds and 450 after 20.
- Latency (ping). We measure ping live and you set the maximum allowed difference, which is good for modes where network quality matters most.
- First-come. No closeness check. The fastest queue there is.
Match shapes are flexible: 1v1, 5v5, four teams of two, asymmetric 1-vs-3, co-op or free-for-all. Teams are balanced by snake-draft on rating. Parties are optional per mode, with a size limit, and you choose whether a party must stay on one team or may be split.
A webhook you can trust. Match notifications are signed (HMAC-SHA256 with a timestamp, to block replays), delivered at-least-once, and carry a stable ID so you can de-duplicate. Each game mode has its own signing secret, and if one ever leaks you can roll it immediately. Matches that arrive during a roll are retried, not lost. The payload includes each player's team, search duration and the MMR or ping that drove their search, plus a party ID where relevant.
Region handling that stays out of the way. By default we pick the region with the lowest latency to the player. If you want players to choose, pass a region when you create the ticket.
Pricing you can predict. You pay a flat monthly price for an allowance of matched players. Only players placed in a match count. Queue time, matching cycles, cancelled searches, dropped connections and match count are free. The dashboard shows usage against your allowance and the matching metrics, and we keep adding to them.
Nothing idling on your bill. Pairiquium is event-driven and serverless, so there is no backend sitting around waiting for players, and no idle cost to pass on to you. It is designed to grow with demand rather than needing capacity planned in advance.
Platform-agnostic by default. Matches are cross-platform unless you decide otherwise. To lock a mode to one platform, use a separate game mode.
What to know before you start
Pairiquium is new, and I'd rather you hear the limits from me:
- No customers yet. Pairiquium is a start-up and nobody is running it in production, so there are no case studies to point at. I haven't published latency or uptime figures because I'd rather give you real numbers from real games than guesses. If you're one of the first, you'll shape what it becomes.
- Fixed allowances. Plans currently run from 750 to 15,000 matched players a month (Hobby is free but waitlisted), and when you reach your cap, new searches are rejected until the next cycle. Players already queued or matched are unaffected. Top-ups and optional overage are planned, not live. That means no surprise bill, but also a hard ceiling today.
- Skill range is the only widening dial. Skill-based searches widen over time. Ping uses a fixed maximum difference, and first-come has no settings.
- Party skill limits aren't implemented yet. A party currently matches on the average MMR of its members.
- Unity SDK scope. The SDK is open source (Apache 2.0) and supports Unity 2021.3 LTS or newer on Windows and Linux desktop. It doesn't support WebGL. Other platforms use the web API. Unreal and Godot SDKs are planned.
- Config changes can take up to 5 minutes to apply to a running game mode.
- No game server hosting. We tell your servers who should play together; allocating the server is up to you. Hosting is planned.
- Prices are in GBP only for now.
When another provider is the better choice
Pairiquium is built for a specific job, and a few needs sit outside it. If one of these describes your game, another provider is the better fit:
- Deeply custom matching rules. Pairiquium's three algorithms and configurable ranges cover many competitive and casual modes, but they are not a rules language, and there is no backfill into running matches yet. If your design needs more, Amazon GameLift FlexMatch uses rulesets you write yourself, Unity Matchmaker offers a rule-based engine with rules relaxation and backfill, and Open Match lets you write your own matching function in code. The extra control comes with extra setup and tuning on your side, which is worth it when your game genuinely needs it.
- A full game backend. If you want accounts, storage, leaderboards and social features from a single provider, Nakama (Apache 2.0, self-hosted or managed through Heroic Cloud) or PlayFab cover the whole stack. Pairiquium only does matchmaking, though it only needs a player ID and a rating, so it can sit alongside a backend you already have.
- Hosting and matchmaking from one vendor. FlexMatch is included in GameLift hosting fees when you host there, so if you want both from the same provider, that is a neat fit. Pairiquium doesn't host servers yet (it is planned), so you bring your own.
- No vendor dependency. Open Match is an open-source framework you run and own. That also means you handle the whole operation of it yourself: deploying, scaling and maintaining it. Some teams want exactly that.
A note on pricing: usage-priced services such as FlexMatch ($20 per million player packages, plus $1 per matching hour) charge by consumption, so the cost per matched player can be very low at high volume, but the monthly total moves with your traffic and the complexity of your ruleset. AWS's own example, at 25 million player packages a month, comes to about $511 with a simple ruleset and about $3,966 with a complex one. Pairiquium takes the other approach: a flat monthly price for a fixed allowance, so you know your bill in advance, with no infrastructure to run. Which suits you depends on whether you would rather have a fixed cost or pay for exactly what you use.
A quick comparison
| Feature | Pairiquium | FlexMatch | Unity Matchmaker | Open Match | Nakama |
|---|---|---|---|---|---|
| What it is | Managed matchmaking only | Managed, usage-billed | Managed, part of Unity's services | Open-source framework | Open-source full backend, or managed |
| Setup effort | Low | Medium | Low (in Unity) | High | Medium |
| Rules | 3 algorithms, per-mode config | Custom rulesets | Rule-based, relaxation and backfill | Code your own | Property-based |
| Cost shape | Flat monthly tiers | Per player and per matching hour | See Unity | Free software, you run it | Free self-hosted, paid managed |
| Hosting included | No | When hosted on GameLift | Works with your provider | No | No |
So who is Pairiquium for?
If you're a solo developer or small team who wants matchmaking working this week, with settings you can reason about and a bill you can predict, Pairiquium was built for you. If you need a rules language, a full backend or bundled hosting, one of the options above will serve you better, and I'd rather tell you that than lose your trust.
Try the free tier (currently waitlisted), read the docs, or tell us in Discord what you'd like to see next. I read everything.
Pairiquium prices, limits and features are current as of this post and may change.