What Is GearN?

GearN Server is a self-hostable backend server for games. It gives your project ready-to-use APIs for authentication, player data, inventory, currency, statistics, leaderboard, content, multiplayer, cloud logic, and live operations.

The main goal is simple: your team should spend less time rebuilding backend systems and more time building gameplay. GearN handles common game backend problems through reusable modules and a dashboard.

Game BackendDashboardREST APISocket APILiveOpsCloudScriptOpen Source
GearN In One Picture
GearN logo
Game Client

Unity, C#, JavaScript, TypeScript, Java, Cocos Creator, or any client that can call HTTP/socket APIs.

GearN Server

Central backend layer that validates requests, applies permission rules, runs handlers, and stores game data.

GearN Dashboard

Admin interface for configuration, player support, data inspection, and LiveOps operations.

For Developers
  • Use ready APIs instead of writing the same backend features again.
  • Configure only the modules your game actually needs.
  • Extend server behavior with CloudScript and EventCallbackScript.
For Admins
  • Search and inspect player, group, inventory, store, and content data.
  • Fix player issues without waiting for a client update.
  • Track logs, leaderboard changes, currency changes, and suspicious behavior.
For LiveOps
  • Adjust content data and remote config without shipping a new build.
  • Operate leaderboards, events, currencies, inventory, and player segments.
  • Push real-time events to players through socket workflows.
Development And Live Environments

By default, GearN Server separates game data by environment. The usual setup is dev for development and testing, and live for production players.

EnvironmentPurposeTypical Users
devTest backend settings, API flows, CloudScript, events, and data changes safely.Developers, QA, internal testers
liveServe real players with stable production configuration and controlled permissions.Players, admins, LiveOps team
customAdd staging, review, seasonal, or regional environments when your workflow needs them.Release managers, operators
Supported Client Direction

GearN is backend-first. The client only needs to call the public APIs correctly and keep authentication tokens safe.

Unity iconUnity / C#

Good default path for Unity game projects.

Cocos Creator iconCocos Creator

Useful for TypeScript-heavy game clients.

TypeScript / JavaScript

Works for web tools, launchers, services, and browser-based clients.

Java / Custom Client

Any platform can integrate through HTTP and socket protocols.

What GearN Server Can Do
  • Authenticate users with Custom ID, username/password, Google, Apple, Google Play Games, Game Center, Facebook, generic services, and more.
  • Link and unlink accounts across supported authentication providers.
  • Organize entities such as MasterPlayer, GamePlayer, CharacterPlayer, Group, Inventory, and StoreInventory.
  • Store generic data like DisplayName, Avatar, Currencies, Statistics, Tags, Segments, Data, and CustomDatas.
  • Manage leaderboards for currencies and statistics, including reset workflows.
  • Track logs for currency changes, statistic changes, server activity, and player operations.
  • Push socket events to one player, multiple players, rooms, or all connected players.
  • Manage content as remote configuration for gameplay data.
  • Run multiplayer matchmaking based on queues, tickets, matches, and custom rules.
  • Execute CloudScript to extend server logic with TypeScript.
  • Override default behavior with EventCallbackScript hooks.
  • Control access with Permission Rules for client, admin, and server operations.
Core Modules
ModuleMain Responsibility
AuthenticateLogin, register, token refresh, account linking, third-party identity.
MasterPlayer / GamePlayer / CharacterPlayerPlayer identity, game profile, character profile, social and progression data.
GroupGuild, clan, group membership, group data, group messages.
Inventory / StoreInventoryOwned items, store items, purchases, grants, item metadata.
ContentRemote configuration, uploaded files, content data for game tuning.
CloudScript / EventCallbackScriptCustom backend logic and event-based override points.
When GearN Is A Good Fit
  • You are building a game and need common backend systems quickly.
  • You want full control over hosting, data, configuration, and server behavior.
  • You need dashboard-driven operations for support, tuning, events, and moderation.
  • You expect your backend model to evolve as your game grows.