What does "games as a service" mean?
Games as a service (GaaS) describes games designed to be operated continuously over years rather than sold once and finished, with ongoing content updates and ongoing revenue.
The contrast is the traditional model: a game ships, you buy it, you finish it, the studio moves to a sequel. GaaS replaces this with a live product — regular content drops, seasonal events, balance patches, an in-game store, and a player community expected to return indefinitely.
Why publishers pursue it:
Revenue over time far exceeds a single sale. A player spending modestly each month for three years is worth many times a single purchase.
Predictable income rather than lumpy release-driven revenue.
Lower risk per update than betting a studio on a new title.
Player retention compounds, since an established community attracts more players.
What it requires, and why so many fail. Running a live service needs continuous content production, server infrastructure, live operations, community management and rapid response. It is fundamentally different from shipping a game, and studios without that capability struggle. The market is also saturated — GaaS games compete for the same finite player time, and players can realistically sustain only a few. High-profile, expensive live-service launches have closed within months.
What it means for players:
The good: substantial ongoing content, an evolving game, an active community, and often a free-to-play entry point.
The bad, and it is genuinely significant:
Games can be switched off. When the servers close, the product frequently ceases to exist — including for people who paid for it. This is the central consumer objection, and it prompted the Stop Killing Games campaign and regulatory interest in the EU.
Design pressures toward retention rather than satisfaction — daily logins, grind, engagement mechanics.
Content is drip-fed rather than complete at launch.
Preservation is nearly impossible without offline modes.