Backend for s&box games.
Hosted player data, secure endpoints, inventory, economy, analytics, sync, and revision-safe rollout for P2P or dedicated servers.
Library calls stay small. Rules stay server-side.
Read data, send safe updates, or call an endpoint when the backend needs to decide prices, rewards, and limits.
var
player
=
await
NetworkStorage.GetDocument(
"players",
steamId
);
await
NetworkStorage.UpdateDocument(
"players",
steamId,
ops
);
var
receipt
=
await
NetworkStorage.CallEndpoint(
"buy-item",
new
{
itemId
}
);
read
player
->
check
price
->
write
inventory
What Network Storage handles.
One library. Hosted storage. Clear operations.
Gameplay endpoints
Validate purchases, rewards, inventory, saves, and stats before data changes.
Player data
Store profiles, inventories, currencies, progression, and game records.
Analytics
See player timelines, economy movement, errors, and live behavior.
Sync and revisions
Push actions, collections, game values, migrations, and safe rollouts.
Security
s&box identity, request signing, encrypted sessions, and trusted server keys.
Reliability
Distributed storage, replication, worker failover, and backup infrastructure.
Use it for the systems players try to exploit first.
Network Storage works best when the game sends intent and the hosted endpoint decides prices, rewards, limits, and final writes.
Install Network Storage from Library Manager.
Native C# calls for endpoints, player data, Game Values, and sync-ready YAML Source projects.
Built for live game systems.
P2P and dedicated server ready
Use the same hosted backend layer whether players host matches or you run dedicated servers.
Source-defined actions
Declare endpoint behavior in your project and sync changes without hand-rolled REST glue.
Trusted runtime paths
Use public keys from game clients and keep secret-key operations behind trusted tooling.
Premium support
Get help shaping data models, endpoints, migration hooks, and production rollout plans.