Open Source Go Game Servers

The simplest, free, open source game management panel. PufferPanel is an open source game server management panel designed to be easy to use and easy to install. PufferPanel supports Minecraft, Forge, Spigot, Sponge, Source Dedicated Servers, BungeeCord, PocketMine, Forge, and much more. In addition to being a free and open source project, PufferPanel provides an easy-to-use interface for everyone from individual users to large networks or companies. We strive to create a friendly community, and we would love for you to join us.

Distributed server for social and real-time games and apps. Users can connect with friends, and join groups. A built-in social graph to see how users can be connected. Extend the server with custom logic written in Lua, TypeScript/JavaScript, or native Go code. Build scalable games and apps with a production-ready server used by ambitious game studios and app developers all around the world.

Multiplayer dedicated game servers anywhere. An open source, batteries-included, multiplayer dedicated game server scaling and orchestration platform that can run anywhere Kubernetes can run. Define and manage groups of ready-game servers through YAML configuration or API calls. Integrated SDK for managing game server lifecycle, health and configuration. Integration with OpenCensus for platform-independent game server metrics and monitoring dashboards. Agones replaces usual bespoke or proprietary cluster management and game server scaling solutions with a Kubernetes cluster that includes the Agones custom Kubernetes Controller and matching Custom Resource Definitions for GameServers, Fleets and more. With Agones, Kubernetes gets native abilities to create, run, manage and scale dedicated game server processes within Kubernetes clusters using standard Kubernetes tooling and APIs. This model also allows any matchmaker to interact directly with Agones via the Kubernetes API.

Leaf, written in Go, is a open-source game server framework aiming to boost efficiency both in development and runtime. Simple APIs. Leaf tends to provide simple and plain interfaces which are always best for use. Self-healing. Leaf always tries to salvage the process from runtime errors instead of leaving it to crash. Multi-core support. Leaf utilize its modules and leaf/go to make use of CPU resouces at maximum while avoiding varieties of side effects may be caused. Each module runs inside a separate goroutine. Modules communicate with one another via a light weight RPC channel(leaf/chanrpc). Leaf suggests not to take in too many modules in your game server implementation. Gate module, for management of connection. Login module, for user authentication. Game module, for the main business.