lonng/nano

Lightweight, facility, high performance golang based game server framework

View on GitHub ↗Jump to charts ↓

lonng/nano has 3k+ stars and 450+ forks on GitHub, is written in Go, and was last pushed on Feb 26, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 39 minutes ago
Added to GitGenius on September 21st, 2026
Created on August 2nd, 2017
Open Issues & Pull Requests: 33 (+0)
GitHub issues: Enabled
Number of forks: 465
Total Stargazers: 3,228 (+0)
Total Subscribers: 71 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 97.6 days
Mean response time: 178.7 days
90th percentile: 634.1 days
Tracked items: 5

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 6
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,001 days
Stale 30+ days: 6
Stale 90+ days: 5

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • question (4)
  • bug (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Nano is a lightweight game server framework written in Go that emphasizes high performance and minimal overhead.

The framework addresses the need for efficient real-time communication in game servers by providing built-in support for multiple transport protocols including TCP and WebSocket. It handles the complexity of distributed systems through a modular architecture that allows developers to structure game logic as independent components. The framework manages message routing, serialization through both JSON and Protocol Buffers, and connection lifecycle automatically, reducing boilerplate code that developers would otherwise need to write.

Nano suits projects where performance and resource efficiency matter, particularly multiplayer games and real-time applications that need to handle many concurrent connections. The framework's lightweight nature makes it appropriate for developers who want a structured foundation without the overhead of larger game engine ecosystems. It works well for teams building backend services that need straightforward networking primitives rather than comprehensive game development tools.

The project shows consistent maintenance with regular updates addressing bugs and adding incremental improvements. Development activity demonstrates responsiveness to issues raised by users, with fixes and enhancements being integrated into the codebase. The maintainers appear focused on keeping the framework lean and performant rather than expanding its scope significantly.