PlayFab Pricing 2026: Plans, the Free-Tier Cut & Real Cost (+ a Cheaper Alternative)

Microsoft PlayFab and Crux are both managed game backends, but they target different studio profiles. PlayFab is Microsoft's enterprise-leaning Game Stack platform with a deep feature surface and pay-as-you-grow billing. Crux is the indie / mid-size alternative built for studios that want flat predictable pricing, fast integration, and SDKs that treat Roblox and Godot as first-class citizens - not afterthoughts.

PlayFab pricing in 2026 (what actually changed)

If you are here for the pricing, the headline is the March change: on March 11, 2026 Microsoft replaced PlayFab's old Development Mode with "Foundation Mode," cutting the free starter runway from roughly 100,000 lifetime accounts to about 1,000 - a ~99% reduction - and gating the free tier behind shipping on Xbox. That single change is why most "PlayFab pricing 2026" searches are happening. Here is the current shape:

PlayFab plan (2026)	Cost	What you get
Foundation Mode (free)	$0	Free only if you register a studio and ship (or plan to ship) on Xbox, linked to Partner Center. Replaced Development Mode (now ~1,000 lifetime accounts) on March 11, 2026.
Standard	~$400/mo of meters, then pay-as-you-go	Live-title plan: a monthly bucket of metered usage, then per-meter billing beyond it.
Premium	~$8,000/mo of meters, then pay-as-you-go	Larger metered bucket for bigger live titles.
Enterprise	from ~$10,000/mo	Custom volume / compliance pricing.

The catch beyond the free runway is unchanged: PlayFab bills per meter - CloudScript executions, multiplayer server core-hours, segment evaluations, data egress - so the monthly total scales with both player count and feature mix and is hard to forecast. PlayFab Multiplayer Server (dedicated game-server hosting) is billed separately by core-hours on top. To sanity-check what a comparable flat plan would cost for your player count, run the numbers in the cost calculator. For the full story on the March change and how studios are responding, see PlayFab's 2026 free-tier cut, explained.

Why teams search "PlayFab alternative"

The most common reasons studios start looking after using PlayFab for a while:

• Pricing surprise. The free runway shrank hard - the March 2026 Foundation Mode change cut it from roughly 100K accounts to about 1K and gated it behind shipping on Xbox - and the per-meter usage billing above it is harder to forecast than a flat plan.
• Microsoft platform coupling. PlayFab is part of Azure / Microsoft Game Stack. As Microsoft's strategy evolves, studios worry about feature deprecations, integration changes, and broader platform lock-in.
• SDK depth varies by engine. Unity and Unreal are first-class. Roblox, Godot, and custom-engine integrations are smaller, less polished, or community-maintained.
• Feature complexity. PlayFab ships dozens of subsystems (CloudScript, segments, A/B testing, push, parties, groups). Many indies use 10% of them and pay the cognitive cost of the other 90%.
• Onboarding friction. The Game Manager dashboard is powerful but takes time to map to your game's actual needs.

Core positioning at a glance

Aspect	Microsoft PlayFab	Crux
Primary focus	Comprehensive Game-Stack BaaS - IAM, multiplayer, lobby, matchmaking, leaderboards, segments, CloudScript, push, economy, inventory, parties, automation, A/B testing	Foundational BaaS - auth, persistent state, leaderboards, server registry, live config, matchmaking, currencies, inventory
Target studio	Indie to AAA - broad spectrum, but feature depth favors mid-size and larger	Indie and mid-size studios shipping multiplayer co-op, competitive, or PvE games
Commercial model	Foundation Mode free tier (Xbox-gated, ~1K accounts since March 2026), then usage-based per metric (CloudScript executions, multiplayer server core-hours, data egress, leaderboard entries)	Flat tiers - free / paid plans with all features included at every paid tier; predictable monthly bills
Integration time	Days to weeks - depth and dashboard learning curve come with the territory	Hours to days - drop-in SDKs for Unity, Roblox, Godot, JavaScript, plus REST for any HTTP client
Hosting model	Cloud-hosted by Microsoft on Azure	Fully managed by Supercraft on dedicated infrastructure
Multiplayer / dedicated server hosting	Separate "PlayFab Multiplayer Server" product, billed by core-hours	Server registry built in; Supercraft also operates dedicated game-server hosting under the same vendor
Vendor lock-in concern	Tightly coupled to Microsoft / Azure ecosystem	REST + JSON API; data export available; no platform marriage

Where PlayFab wins

• Feature breadth. If you genuinely need CloudScript, segmentation, A/B testing, push notifications, parties, groups, automated retention campaigns, telemetry pipelines, and economy management all in one product, PlayFab ships them.
• Microsoft Game Stack integration. Pairs naturally with Azure, PlayFab Multiplayer Server, Xbox Live, and Microsoft's broader gaming platform if you're already deep in the Microsoft ecosystem.
• Cross-platform identity at scale. Mature account-linking flows for Steam, Epic, Xbox, PlayStation, Nintendo, Apple, Google, Facebook.
• Track record. Used by AAA live-service titles for over a decade. The platform has battle-tested at very large player counts.
• Telemetry + analytics depth. Built-in dashboards, segment-driven LiveOps, and event ingestion for marketing and retention work.

Where Crux wins

• Predictable flat pricing. No usage-based billing surprises. PlayFab's per-feature usage costs (CloudScript executions, leaderboard entries, segment evaluations) compound as you grow; Crux tiers include everything.
• Engine-equal SDK quality. Roblox (Lua), Unity (C#), Godot (GDScript), JavaScript / TypeScript, and curl-friendly REST are all officially supported and documented to the same depth.
• Days, not weeks. The SDK quickstart authenticates a player and writes a save in a single screen of code per engine - no Game Manager configuration tour required.
• No Microsoft lock-in. If your studio is already wary of platform consolidation (Game Pass / Activision-Blizzard / Bethesda dynamics), Crux sits outside that orbit.
• Unified hosting + backend. Supercraft operates dedicated game-server hosting too - one vendor, one billing relationship, one support team for both your backend services and your game servers.
• Free tier with all features, no Xbox requirement. 2,000 MAU free with every feature unlocked. PlayFab's Foundation Mode free tier is now Xbox-gated and capped near 1,000 accounts after the March 2026 cut.

Pricing reality

As of March 2026 PlayFab's free runway is Foundation Mode - free only if you ship on Xbox, and capped near 1,000 accounts (down from the old ~100K). Beyond it, billing is per-resource consumption: CloudScript executions, multiplayer core-hours, segment evaluations, photon CCU, data egress, and so on. For a small studio this is hard to forecast - your monthly bill scales with both player count and feature mix.

Crux uses a flat-tier model: a free tier for prototyping (2,000 MAU, all features), then paid tiers that include every feature at every tier. The main growth axis is monthly active players, not a basket of per-feature meters. Predictable for cash-flow planning at indie and mid-size scale. See the cost calculator for a worked example.

PlayFab Multiplayer Server vs Crux server registry

This is one of the more confused comparisons. PlayFab has a separate PlayFab Multiplayer Server product (formerly Thunderhead) that hosts your dedicated game servers and bills by core-hours. It's powerful but commits you to Azure compute pricing.

Crux takes a different approach: the server registry tracks which dedicated servers are alive and what sessions they host, while the actual server hosting is decoupled. You can run dedicated servers on Supercraft's hosting (one-vendor convenience), self-host on your own VMs, or mix. The registry-plus-matchmaking pattern lets you switch hosting providers without touching your client SDK code.

Migration considerations (PlayFab → Crux)

If you're already on PlayFab and considering a switch, the dedicated 10-step PlayFab → Crux migration checklist walks through exporting player data, mapping the API surface, handling CloudScript, billing transition, and zero-downtime cutover. The summary below is the executive view.

• Player data export. PlayFab supports player data export via the Admin API. The shape of the exported JSON maps reasonably onto Crux's persistent-state model with a transformation script.
• Title-data → live config. PlayFab Title Data corresponds to Crux's live config bundles. The migration is mostly a key-rename pass.
• Leaderboards. PlayFab statistics map cleanly to Crux leaderboards. Reset windows (weekly / monthly / all-time) are supported on both.
• CloudScript. The largest-effort piece. CloudScript is JavaScript executed server-side on PlayFab. Crux doesn't run customer code server-side; instead it ships well-defined endpoints (auth, state, leaderboard, matchmaking, server registry) and assumes business logic lives in your game server or a dedicated workflow service. For most indie use cases this is a simplification rather than a regression.
• Multiplayer Server VMs. If you're using PlayFab Multiplayer Server core-hours, the Crux pattern is server registry + your own hosting (Supercraft's, AWS, OVH, etc.). The migration includes choosing a host and updating your dedicated-server boot scripts to register with Crux on startup.

When to pick each

Pick Microsoft PlayFab if: Your studio is deep in the Microsoft ecosystem, you need CloudScript / segments / A/B testing / push notifications as first-class features, your title is at six-figures of MAU and the per-feature billing math works out, or you have a platform engineering team to manage the dashboard configuration and data pipelines.

Pick Crux if: You want predictable flat pricing without per-feature billing surprises, your team uses Roblox or Godot (where Crux SDKs are first-class), you want to ship a working multiplayer backend in days without a multi-week dashboard onboarding, or you also need dedicated game-server hosting under the same vendor.

Common migration triggers

• PlayFab → Crux: Monthly bill became unpredictable as the game grew; team uses 10-20% of the feature surface; engine isn't Unity / Unreal; concerns about Microsoft platform consolidation; or the March 2026 free-tier cut made the starter tier unworkable.
• Crux → PlayFab: Team scaled past hundreds of thousands of MAU and needs CloudScript-style server-side custom logic, deep segmentation, or Microsoft Game Stack integration.

Bottom line

PlayFab is a comprehensive enterprise-grade BaaS with a feature surface that spans more than a decade of Microsoft Game Stack development. Crux is the leaner alternative for indie and mid-size studios that want flat predictable pricing, fast integration, equal SDK depth across engines, and no Microsoft platform marriage.

If your team uses PlayFab today and you're tracking month-over-month bill volatility, or you're starting fresh and want a backend that ships in days, Crux is built for that lane.

Try Crux

The free tier covers 100 monthly active players with every feature unlocked - auth, persistent state, leaderboards, server registry, live config, matchmaking, currencies, inventory. Sign up free, copy the SDK quickstart for your engine in SDK quickstart, or work through the full reference at /docs. Pricing details on /pricing/.

Related comparisons

• PlayFab cut its free tier 99% (2026): Foundation Mode and how to respond - the pricing change driving most PlayFab migrations this year
• AccelByte vs Crux - for studios weighing AAA-class enterprise backends
• Beamable vs Crux - for live-ops-heavy mid-size studios
• Brainslug vs Crux - for studios weighing web3 / creator-economy backends
• Epic Online Services vs custom backend
• Colyseus vs managed backend
• Game backend pricing models - full comparison