Standard price
$23,500/mo ÷ 1,800,000
Per user $0.0131 /mo
GS2-Steady
For titles above a certain scale, backend cost of around $0.016 per user per month.
A new pricing plan aiming for around $0.008 with a one-year commitment.
~$0.016
Monthly cost per user
for titles above a certain scale
~$0.008
Monthly cost per user
with a 1-year commitment
16.6ms or less
Average response time
within the same data center
1.02M RPS
Requests per second
the largest fleet absorbs
Why we built it
As coding agents advance, the cost of building a game backend has dropped sharply.
But the servers and databases you pay for every month after launch cost about the same as they always have — and the longer you operate, the more that adds up.
So we redesigned the GS2 backend architecture and built GS2-BufferedSession to bring down the cost of running itself.
Price level
Example: a 1,800,000 MAU title that fits in std1.large
Standard price
$23,500/mo ÷ 1,800,000
Per user $0.0131 /mo
1-year commitment
$11,800/mo ÷ 1,800,000
Per user $0.0066 /mo
The fleet you need depends on your game design and API usage. To estimate with your own numbers, use the calculator.
Architecture
GS2-BufferedSession sits between the GS2 API and the database, keeps player data in memory, and writes updates in batches.
It delivers its best cost performance in games that update the same player data many times a minute.
STEP 01
Every player action calls the API, and every API call reaches the database. Database access costs more than the servers themselves.
STEP 02
Each request becomes a database access, and the number of accesses is what you pay for.
STEP 03
GS2-BufferedSession keeps player data in memory and writes updates to the database in batches. However many times the same data changes, it takes a single write.
STEP 04
When a critical update arrives — spending paid currency, for instance — the pending updates for that player are flushed first, and then it goes straight to the database. Even mid-window, important data never waits.
STEP 05
Fewer accesses mean less waiting. With the database round trip gone, the API responds in under one frame (16.6ms) on average.
Monthly game server cost
The biggest share goes to the database
* Illustrative. Actual shares vary by setup and game.
Requests 0
DB accesses (without buffering) 0
DB accesses (BufferedSession) 0
Reduction (in this animation) -
When a critical update arrives, pending updates are flushed first, and then it is written to the database immediately.
One game frame(60fps)
Without buffering
BufferedSession
* Measured within the same data center, excluding internet latency. The bar without buffering is illustrative.
Fixed at 15 minutes. Repeated writes to the same data inside the window never touch the database — they are handled in memory. An unexpected failure can lose whatever the window still held.
Because GS2 exposes fine-grained game context as APIs, it knows how important each write is. A write that matters — spending paid currency, for instance — flushes the buffer and reaches the database immediately, even mid-window.
Whether you scale up or scale in, a retiring instance flushes its buffer before it leaves. Nothing in the buffer is lost, and there is no downtime.
With the database round trip gone from ordinary API calls, responses average under one frame (16.6ms) and stay under 100ms even at p99 (round-trip time within the same data center).
An illustrative AWS cost comparison
An illustrative AWS Tokyo configuration for 60,000 CCU and about 4,000 peak external RPS. With an average fanout of four, the GS2 side processes about 16,000 internal RPS, compared here using std1.large.
Infrastructure costs for this example
The faded AWS bar shows 30-day on-demand costs. The one-year commitment is the annual cost divided by 12.
This is an estimate of selected infrastructure costsunder the stated assumptions. It does not demonstrate matching performance, durability or operations. Excluded AWS costs must be added.
| Item | Configuration / assumption | On-demand, 30 days | 1-year prepaid, monthly equivalent |
|---|---|---|---|
| API servers | Fargate x86 · 16 vCPU / 32 GiB × 18 (6 × 3 AZ) | $12,800 | $10,100 |
| Database instances | Aurora I/O-Optimized db.r8g.2xlarge × 12 | $15,000 | $9,650 |
| Database storage | Aurora I/O-Optimized · 1 TiB | $276 | $276 |
| Cache | Redis cache.r7g.xlarge × 6 | $2,260 | $1,470 |
| Log ingestion | CloudWatch Logs Standard · 2 KiB / external request | $4,510 | $4,570 |
| Log storage | CloudWatch Logs · 30 days · assumed compression ratio 1.0 | $196 | $196 |
| Log queries | Logs Insights · 1 full scan / month | $45 | $46 |
| Subtotal (excluded costs extra) | $35,000 | $26,300 |
The AWS example uses one region and multiple AZs; its topology and operations are not identical to GS2. GS2 ordinary updates may lose unpersisted data within the 15-minute buffer window, while important updates are persisted immediately. No equivalence in performance, durability or operations is claimed.Load testing and failure planning must follow your requirements.
GS2-Steady starts at $2,700/mo. For titles below a certain scale, GS2's pay-as-you-go plan may be cheaper. Once you grow into it, you can switch across without moving any data.
Pricing
Balanced games want the std family.
Games with many concurrent users want ccu, which carries more memory for buffering.
Games that call the API very frequently want rps, with extra throughput.
| Fleet | Max CCU | Max RPS | Standard | 1-year commit |
|---|---|---|---|---|
| std1.nano | 3,000 | 1,000 | $2,700/mo | $1,300/mo |
| std1.micro | 9,000 | 2,000 | $4,000/mo | $2,000/mo |
| std1.small | 12,000 | 4,000 | $6,300/mo | $3,200/mo |
| std1.medium | 28,000 | 8,000 | $12,200/mo | $6,100/mo |
| std1.large | 60,000 | 16,000 | $23,500/mo | $11,800/mo |
| std1.xlarge | 124,000 | 32,000 | $46,700/mo | $23,300/mo |
| std1.2xlarge | 248,000 | 64,000 | $90,000/mo | $45,000/mo |
| std1.4xlarge | 496,000 | 128,000 | $176,700/mo | $88,300/mo |
| std1.8xlarge | 992,000 | 256,000 | $343,300/mo | $171,700/mo |
| std1.16xlarge | 1,984,000 | 512,000 | $671,700/mo | $335,800/mo |
| std1.32xlarge | 3,968,000 | 1,024,000 | $1,313,300/mo | $656,700/mo |
| Fleet | Max CCU | Max RPS | Standard | 1-year commit |
|---|---|---|---|---|
| ccu1.small | 28,000 | 4,000 | $7,300/mo | $3,700/mo |
| ccu1.medium | 60,000 | 8,000 | $14,000/mo | $7,000/mo |
| ccu1.large | 124,000 | 16,000 | $28,300/mo | $14,200/mo |
| ccu1.xlarge | 248,000 | 32,000 | $53,300/mo | $26,700/mo |
| ccu1.2xlarge | 496,000 | 64,000 | $103,300/mo | $51,700/mo |
| ccu1.4xlarge | 992,000 | 128,000 | $201,700/mo | $100,800/mo |
| ccu1.8xlarge | 1,984,000 | 256,000 | $391,700/mo | $195,800/mo |
| ccu1.16xlarge | 3,968,000 | 512,000 | $765,000/mo | $382,500/mo |
| ccu1.32xlarge | 8,064,000 | 1,024,000 | $1,495,000/mo | $747,500/mo |
| Fleet | Max CCU | Max RPS | Standard | 1-year commit |
|---|---|---|---|---|
| rps1.small | 12,000 | 8,000 | $11,700/mo | $5,800/mo |
| rps1.medium | 28,000 | 16,000 | $22,500/mo | $11,300/mo |
| rps1.large | 60,000 | 32,000 | $45,000/mo | $22,500/mo |
| rps1.xlarge | 124,000 | 64,000 | $86,700/mo | $43,300/mo |
| rps1.2xlarge | 248,000 | 128,000 | $168,300/mo | $84,200/mo |
| rps1.4xlarge | 496,000 | 256,000 | $328,300/mo | $164,200/mo |
| rps1.8xlarge | 992,000 | 512,000 | $643,300/mo | $321,700/mo |
| rps1.16xlarge | 1,984,000 | 1,024,000 | $1,261,700/mo | $630,800/mo |
All prices are monthly and exclude tax. "1-year commit" is the monthly equivalent when you prepay a full year of usage. Prices are preview estimates and may be revised when the service becomes generally available.
You can move between GS2-Steady and the pay-as-you-go plan in either direction. Both plans share the same database, so no data migration is required. A move does involve downtime, so we expect it around launch or at a turning point in live operations. Moving between plans requires a project that uses database schema v2.
Calculator
Four numbers is all it takes. We size the fleet for the launch month and for everything from day 30 onward.
Launch month
—
—
Downloads through day 7
—
Your input
Day 1 downloads
—
× 0.5
Peak-hour actives
—
× 0.5
Login RPS
—
÷ 3600 × fetches
In-session RPS
—
Peak CCU × requests per minute ÷ 60 × 4
Peak CCU
—
× session minutes ÷ 60
Day 30 onward
—
—
Downloads through day 30
—
Day 7 total × 1.5
Day 30 active users
—
× 0.1
Peak-hour actives
—
× 0.5
Login RPS
—
÷ 3600 × fetches
In-session RPS
—
Peak CCU × requests per minute ÷ 60 × 4
Peak CCU
—
× (session minutes × 0.8) ÷ 60
Estimated from average GS2 statistics. Per-user prices use downloads through day 30 as the launch-month MAU, and day 30 active users converted at a 50% DAU/MAU ratio from day 30 onward.
Building a backend is easier than ever.
So GS2 gives you a foundation that keeps your game running for years, for less.
That is the value the new GS2 aims to bring as a BaaS.
Preview
We are accepting preview registrations ahead of general availability. Register and we will let you know when it opens, and talk through a configuration sized for your title.