Most Unity developers end up evaluating Unity Gaming Services (UGS) by default. It is bundled with the editor, the documentation lives in the same place you already read docs, and the SDK installs with one click from the Package Manager. For a small team that wants to ship fast, that path makes sense.
But "it was already there" is not the same as "it is the right fit for where this game is going." If your mobile title is planning a PC release, wants a full store catalog with a battle pass, or needs dedicated game servers by launch, the decision is less obvious.
Fully managed backend providers like AccelByte Gaming Services (AGS) provide authentication, matchmaking, server hosting, economy, cloud save, and live-ops tooling as a hosted service that works across engines and deploys to iOS, Android, PC, and console without changing integration.
This article maps what USG and AGS actually cover, where they diverge on the decisions that matter for mobile studios, and when each one fits better.
UGS is a collection of independently adoptable services that are installed as Unity packages. You can pull in only what you need and pay per service once usage exceeds each product's free tier. The current service list for mobile-relevant features:
The editor integration is the clearest advantage with UGS. Building Blocks and a UI layer inside the Editor lets you wire up authentication, leaderboards, and matchmaking flows without writing SDK boilerplate. A developer new to backend work can have player login and a working leaderboard in an afternoon.
One structural change affects studios planning dedicated game servers: Unity discontinued direct support for Multiplay Game Server Hosting on March 31, 2026. The software was licensed to Rocket Science Group, and Unity Matchmaker continues to work with Relay and Distributed Authority. Unity has said it is working to extend Matchmaker's support to third-party hosting providers. If your mobile game uses peer-to-peer sessions via Relay, nothing changes. If you planned to run authoritative dedicated servers through Multiplay under Unity's umbrella, you now need a separate hosting decision.
If you need to make a hosting decision now, we put together a practical breakdown of what the Multiplay transition means for studios, what your options are, and how to evaluate them. Read the full write up here.
AccelByte Gaming Services (AGS) is a modular backend platform built by engineers who shipped online infrastructure for Fortnite, Xbox Live, and EA Origin. It covers the full live-service stack and is organized into three packages that you adopt individually or together: Foundations, Online, and Multiplayer. The SDK works with Unity, Unreal, and custom stacks, so your integration does not change if your engine does.
Foundations module covers the services every online game needs:
Beyond the core backend, we also provide AccelByte Development Toolkit for crash reporting, build distribution, and playtesting with AI assistant, incremental builds and video captures before crashes.
| Feature area | Unity Gaming Services | AccelByte Gaming Services |
|---|---|---|
| Backend Logic | Multiplay discontinued March 2026. Relay (P2P) still active. Third-party hosting required for dedicated servers. | AMS: dedicated server orchestration across AWS, Azure, and bare metal. 90-day free trial (2,160 hours on a 2vCPU / 2GB instance). |
| Economy & store | Currencies, inventory, IAP sync from Google Play and Apple. Battle pass and seasonal store require Cloud Code + Remote Config assembly. | Full store catalog, storefront config, wallet, inventory, Season Pass built in. IAP sync: Google Play, Apple, PSN, Xbox, Steam, Epic, Twitch. |
| Pricing model | Pay-per-service. Free tier per product. Billing starts when any individual service exceeds its free allowance. | AGS Public Cloud is fully free during development up to 30 CCU, PCCU-based billing after that. |
| Engine coupling | Primarily Unity. Building Blocks UI in the editor. Developer experience is built around Unity. | Engine-agnostic. Unity SDK (2020, 2021, 2022, Unity 6), Unreal SDK, and custom REST API stack all supported. |
| Custom logic | Cloud Code: server-side JavaScript or C# functions triggered by client calls or Events. | Extend overrides default service behaviors via gRPC. Runs in AccelByte-managed infrastructure — swap behavior rather than layering around it. |
| Support | Community forums and documentation on all plans. Dedicated support tied to Unity subscription tier. | Discord and shared Slack channel on all plans, with options up to co-development level support. |
The integration path is close to UGS. From the Unity Package Manager, add the AGS SDK package using the GitHub URL. The editor exposes a configuration window where you set your client credentials and service URL for your game namespace. Authentication, matchmaking, leaderboards, and cloud save all call AGS APIs.
The AGS Public Cloud free trial covers all core services for 90 days or 25,000 play hours, whichever runs out first. No credit card is required to start the backend trial. AMS and Extend require payment information for their separate trials (AMS gets you 2,160 hours on a 2vCPU / 2GB instance; Extend gets 888 VM hours).
To cover the full installation steps, see Set up the AGS Unity SDK.
If your studio outgrows Public Cloud, there is a migration path to Private Cloud (single-tenant, dedicated environment) without rebuilding your integration. The service API surface is the same so the migration just an infrastructure change.
FuzzyBot, an indie studio, used AccelByte Gaming Services (AGS) Public Cloud to ship Lynked: Banner of the Spark without hiring dedicated backend engineers. The team needed matchmaking, on-demand dedicated servers, and offline-to-online persistence, services that would have taken months to build in-house. Using AccelByte, FuzzyBot shipped the game six months faster than their timeline.
For studios that want more depth on what the matchmaking integration looks like specifically in Unity, How to Add Matchmaking to a Unity Game Without Using Unity Matchmaker walks through the configuration end to end.
This is not a close call in either direction as they fit different situations.
Neither platform is a bad choice for a well-scoped mobile title that stays within its natural use case. The risk is building on a platform that does not grow with the game. A studio that starts with UGS Relay-based multiplayer and later decides they need dedicated servers is now sourcing a second vendor mid-roadmap. A studio that starts with UGS Economy and later needs a full battle pass is assembling one from Cloud Code and Remote Config. Those paths are not blocked, just more work than they would be on a platform where both are native.