Nakama · FinOps Profile

Nakama Finops

FinOps view of running Nakama. Because Nakama is open source (Apache-2.0), the cost model splits in two. Self-hosting has no software license fee; spend is your own compute (Nakama server nodes), the PostgreSQL/CockroachDB database, storage, egress, and operations labor. Managed usage runs on Heroic Cloud, billed as a tiered monthly subscription (Nakama nodes, database capacity, concurrent-user allowance, support) with scaling above the included allotments. The main cost drivers are concurrent users, realtime message volume, database size and IOPS, and node count.

Nakama Finops is the FinOps profile for Nakama on the APIs.io network, aligned with the FinOps Foundation Framework.

It defines 6 billable meters, billed in USD, on a monthly cycle, and pricing category subscription plus usage-based (heroic cloud); self-hosted infrastructure cost.

The profile maps 8 FOCUS columns for cost-allocation reporting.

Tagged areas include Gaming, Game Backend, Realtime, Open Source, and FinOps.

Category: Game Backend and Realtime Infrastructure Pricing: Subscription plus Usage-Based (Heroic Cloud); self-hosted infrastructure cost Billing: Monthly FOCUS v1.3
GamingGame BackendRealtimeOpen SourceFinOpsCost ManagementFOCUS

Framework Alignment

Framework
FinOps Foundation Framework
Data Spec
FOCUS v1.3

Charge Categories

UsagePurchaseAdjustment

FOCUS Columns

BillingCurrency
USD
ChargeCategory
Usage
InvoiceIssuerName
Heroic Labs
PricingCategory
Subscription
ProviderName
Heroic Labs
PublisherName
Heroic Labs
ServiceCategory
Game Backend and Realtime Infrastructure
ServiceName
Nakama / Heroic Cloud

Meters

managed_nodes
Unit: nodes
Managed Nakama compute nodes provisioned on Heroic Cloud.
concurrent_users
Unit: concurrent_users
Peak concurrent connected users (CCU), the primary Heroic Cloud scaling dimension.
database_capacity
Unit: gigabytes
Managed database storage and capacity provisioned for the project.
realtime_messages
Unit: messages
Realtime socket message volume across chat, matches, and matchmaking (a load/cost driver).
egress_bandwidth
Unit: gigabytes
Outbound network bandwidth from the deployment.
self_hosted_compute
Unit: hours
For self-hosting, underlying cloud compute hours for Nakama server nodes.

Sources