PlayFab Cut Free Tier 100K to 1K Users (March 2026). Here's What Indies Are Switching To

On March 11, 2026, Microsoft replaced PlayFab's Development Mode with Foundation Mode. The headline number in the dev community: the previous free tier covered up to 100,000 users. Development Mode now caps at 1,000 lifetime player account creations. That's a 99% reduction in free runway for studios who built their backend evaluation around the old terms.

The PR framing is that Foundation Mode is "free" - and it is, if you check three boxes. This post explains the boxes, what happens if you can't check them, and what indie studios who don't ship on Xbox are actually doing.

What changed, in one paragraph

PlayFab Development Mode used to be a no-friction sandbox: up to 100,000 player accounts at no cost, no payment instrument required, intended for "lightweight, low-volume usage" during the build. As of March 11, 2026, Development Mode is capped at 1,000 lifetime player account creations per title and limited to 10 titles per account. Above that, you either move to a paid tier or you switch to Foundation Mode.

Foundation Mode: free, with strings

Foundation Mode is the new free tier, but it's gated on three eligibility checks:

1. You register a studio in PlayFab Game Manager.
2. You ship or plan to ship your game on Xbox.
3. You link your PlayFab account to your Partner Center studio and product.

Hit all three and Foundation Mode gives you the seven cross-platform service pillars: identity, progression, community, multiplayer, live service management, economy, and game data stream. No payment instrument required.

The catch is in step 2. If your game is PC-only, mobile-first, Switch-exclusive, or otherwise not Xbox-bound, Foundation Mode is not for you. You're back in Development Mode's 1,000-account corral.

What 1,000 lifetime accounts actually buys you

1,000 sounds like a number until you do the math on a real playtest.

Phase	Typical account creation	When the wall hits
Internal alpha	~20-50 accounts (team + ops)	Comfortable
Friends-and-family playtest	~50-200 fresh accounts	Mostly comfortable
Discord closed beta (200 testers)	~1,000-3,000 (re-tests on fresh accounts)	Hits the wall mid-beta
Steam playtest / Next Fest demo	~10,000+ in week one	Wall hit immediately

The Development Mode cap is fine for an internal sandbox. It's not fine for any external playtesting larger than the team's group chat.

What indie studios are switching to

Studios who looked at the Foundation Mode requirements and concluded "this isn't for us" have a small handful of real options in May 2026.

Crux

Free tier covers 2,000 monthly active users and 2,000,000 API calls per month. No Xbox requirement, no Partner Center linkage, no payment instrument needed during evaluation. Includes auth, leaderboards, player progression, server registry, and dedicated server orchestration in a single platform. Flat-rate paid plans above the free tier instead of usage-based meter math.

Best fit for: indie / mid-size studios who want a unified backend with predictable pricing and no platform lock-in. See pricing.

Nakama (self-hosted)

Open source, Apache-licensed, you run the ops. Infinite "free" in the sense that there's no per-account cap, but you're now responsible for PostgreSQL, your Linux fleet, your backups, and your on-call rotation. Heroic Labs offers a managed Nakama Cloud if you want to outsource the ops.

Best fit for: studios with a platform engineer on staff who would rather own the infrastructure than rent it.

Firebase

Google's BaaS. Free tier is generous for auth and Firestore reads. The gap: Firebase has no dedicated game server orchestration, no built-in leaderboards (you build them on top), no live ops dashboard for game-specific events. It's a good auth+database foundation but not a complete backend for multiplayer games.

Best fit for: turn-based mobile games and casual multiplayer where dedicated servers aren't needed.

Beamable

Managed game backend with a free tier and per-MAU paid pricing. The free tier is smaller than Crux's but the platform is mature and has been live for several years. Strong on live ops tooling specifically.

Best fit for: studios who want a managed alternative to PlayFab without re-onboarding to Microsoft's platform.

Migration: what touches and what doesn't

If you're migrating off PlayFab, the work is real but bounded. Here's what your engineering team actually touches:

• Client SDK calls - every PlayFab.AuthenticationApi.LoginWith*, PlayFab.LeaderboardsApi.*, PlayFab.DataApi.* call becomes a different SDK call. Wrap PlayFab in your own thin client BEFORE migrating to make this easier.
• CloudScript handlers - server-authoritative game logic running in PlayFab needs a new home (your own backend service, or the equivalent feature in your new BaaS).
• Scheduled tasks - PlayFab's scheduler runs cron-style jobs. Whatever replaces it (cloud cron, k8s CronJob, your new BaaS scheduler) needs to be wired up before you cut over.
• Player ID continuity - the hardest piece. If existing players have PlayFab IDs and saved data, you need a one-time export and mapping into the new backend. Without this, your live game's players lose their progression on migration day.
• Live ops dashboard - your community manager / data team currently watches PlayFab's dashboard. Whatever they watch next needs the same event feed wired up before cut-over.

Two to four engineering weeks is the standard estimate for a mature title. Most of the time is in the player ID migration and validation, not the API call rewrites.

What we're recommending in May 2026

If you were on PlayFab Development Mode and you got blindsided by the March 11 cap, here's the decision tree:

• Shipping on Xbox in the next 12 months: Foundation Mode is genuinely free and the path of least resistance. Sign up, link Partner Center, move on.
• Not shipping on Xbox, indie / mid-size: Crux. Free tier covers a real playtest, no platform gating, and the paid plans are flat-rate instead of usage-based meter math. See pricing.
• Have a platform engineer and want to own the stack: Self-hosted Nakama. Free in dollars, expensive in ops time. Worth it if your team has the muscle.
• Casual / turn-based mobile only: Firebase. It's not a game backend, but for non-realtime mobile titles it's a fine foundation.

Related reading

• PlayFab Alternative: Crux vs Microsoft PlayFab - the deeper feature-by-feature comparison.
• Unity Multiplay Shut Down: Where Studios Actually Went - if your PlayFab setup also used Multiplay for hosting, you need to plan both migrations at once.
• Game Server Backend Platform Buyer's Guide - broader buying framework.
• Cost calculator - model your MAU and API call curve against Crux's flat-rate pricing.