// the find
youngmonkeys/ezyfox-server
A socket server (include SSL) supports realtime application, realtime game, MMORPG, messaging, chat and streaming data with TCP, UDP and Websocket
EzyFox Server is a Java socket server framework for building real-time multiplayer games and chat/streaming apps, bundling TCP/UDP/WebSocket/SSL transports with an app/zone/plugin architecture and its own DI container. It's aimed at small studios who'd otherwise pay for SmartFoxServer or Photon and are willing to run and operate the infrastructure themselves.
Genuinely broad protocol support in one server (TCP, UDP, WebSocket, SSL, plus HTTP/RPC) rather than bolting WebSocket onto an HTTP framework as an afterthought. Client SDK coverage is unusually wide for a project this size — Android, iOS, Unity, Flutter, C++, Swift, React Native — which matters a lot for a game-server product where the client is half the integration work. The zone/app/plugin split with dependency injection gives a real multi-tenant story (one server instance, multiple isolated apps) instead of the common one-process-per-game hack.
Targets JDK 1.8, so anyone adopting this in 2026 inherits a decade-old language baseline and whatever GC/NIO limitations come with it — no visible move to virtual threads or modern Java. The benchmark claim (1000 concurrent users on a 512MB/1-core VPS) is presented as proof of scale but is a single unverified video, not a reproducible load-test report, and says nothing about latency percentiles or message throughput. Documentation lives entirely off-repo on youngmonkeys.org, so the README is a features list with no code sample for actually wiring up a handler — you have to leave GitHub to learn the API. The example projects are toy-scale (lucky wheel, tic-tac-toe-style 'one-two-three'), so there's no reference for what a production deployment (clustering, reconnection handling, persistence) actually looks like.