Supercraft Game Server Backend
Player auth, persistent data, leaderboards, server registry, economy, and live config delivery in one platform — built for Unity, Roblox, and custom multiplayer games.
Ship multiplayer features without stitching together auth, player storage, leaderboard logic, server discovery, and runtime config delivery from scratch.
Most backend tools handle players. Most hosting tools handle servers.
The Supercraft Game Server Backend brings both together, so the runtime needs of dedicated-server games stop living across custom scripts, ad hoc endpoints, and operational guesswork. Use one platform to authenticate players, store progression and shared game state, run leaderboards and seasonal resets, register and discover dedicated servers, deliver live configs, and keep staging and production separate.
Better fit for live operations
Configs, player state, rankings, and server availability stay connected instead of drifting apart operationally.
Built around dedicated-server games
Not just auth plus data storage. It also covers the runtime surfaces that server-based games actually need.
Less platform stitching
Move faster without assembling separate tools for auth, persistence, rankings, config rollout, and discovery.
Cleaner rollout path
Go from prototype to live environment with less risk that the backend becomes the part slowing down shipping.
What you get
Core backend services for dedicated-server and session-based multiplayer games, with enough breadth to run live operations without dragging in a giant platform you do not need.
Player Authentication
Email/password, guest sessions, OAuth, and Roblox verification so you can support real accounts, onboarding, and authenticated player access without building auth flows from scratch.
Persistent Data
Player-scoped and project-scoped JSON documents for progression, profiles, unlocks, event flags, inventories, and shared runtime values.
Leaderboards
Ranked and seasonal boards with configurable rules, fast ranking reads, recurring resets, and support for timed events or score-based loops.
Economy
Currencies and inventory with atomic updates for rewards, sinks, consumables, grants, and server-authoritative progression systems.
Dedicated Server Registry
Register, heartbeat, and search dedicated servers to power server browsers, active session discovery, region-aware listings, and stale cleanup.
Live Config Delivery
Upload versioned bundles and activate them per environment so balance changes, rotations, loot tables, and rulesets ship without a full patch.
One API. Three auth modes.
API Key
Admin scripts, CI, tooling, and control-plane access.
Server Token
Dedicated game servers and trusted runtime services.
Player JWT
Authenticated players issued by the auth system.
This keeps players, servers, and operators on separate trust boundaries while staying simple enough to integrate with Unity, Roblox, or any HTTP client.
Example outcomes
- Player profiles and progression
- Guest-to-account upgrade flows
- Seasonal scoreboards and rank loops
- Server browser features
- Live event configuration
- Balance and loot tuning
- Server-authoritative reward systems
- Environment-specific staging and rollout flows
Built around dedicated-server games, not generic app backends.
Most generic backends stop at auth and storage. Supercraft also covers the runtime needs of server-based games, with a better fit for live operations and environment-aware rollout.
Best suited for
- Dedicated-server games
- Multiplayer survival and co-op games
- Region-based game server fleets
- Unity and Roblox-connected services
- Indie and mid-size studios that want backend velocity
- Teams that do not want to build a platform team before shipping gameplay
Less suited for
- Purely offline games
- Projects that only need a generic login database
- Highly specialized AAA matchmaking stacks from day one
Why say this clearly? Because the offer is stronger when it reads like a tool built for a specific class of multiplayer game, not a vague “backend for everything.”
Infrastructure block
| Component | Role |
|---|---|
| Go API server | Single binary API service |
| PostgreSQL | Primary data store |
| Redis | Caching and rate limiting |
| Object storage | Config bundle storage |
Built-in background workers handle leaderboard resets, matchmaking processing, stale server cleanup, and token cleanup.
- Clean environment isolation. Production, staging, and test setups stay separated by design.
- Server-aware runtime APIs. Dedicated servers do not have to impersonate admin clients.
- Live-ops friendly. Configs, rankings, and player state fit together operationally.
- Stack-flexible. Use it with launchers, dashboards, custom tools, and game services.
Explore the Game Server Backend wiki
Want the deeper architecture and Roblox-specific implementation guides? Visit the Game Server Backend wiki for auth, persistence, discovery, live config, and Roblox backend patterns.
Multiplayer Game Backend Architecture
Map identity, player data, runtime server APIs, discovery, and liveops without building five disconnected systems.
Player Authentication for Dedicated-Server Games
Design guest flows, account upgrades, OAuth, Roblox verification, and cleaner trust boundaries between players and servers.
Server Registry and Live Config Delivery
Power a server browser, keep stale sessions out of the list, and roll runtime config safely per environment.
Roblox HttpService for External Backends
Connect Roblox server scripts to an external backend for auth, progression, support tooling, and live configuration.
Roblox DataStore vs External Database
Know when native Roblox persistence is enough and when you need a broader backend for shared identity and operations.
Roblox Matchmaking with MemoryStore and Reserved Servers
Use MemoryStore queues with TeleportService reserved servers, then connect match results back into a fuller backend.