Technology overview
We build the platformbehind the game.
Player services, operations, identity, project work and team processes are all built by EaseCation. The platform serves more than 100,000 players every day and keeps the team moving behind the scenes.
One platform, from player requests to internal delivery.
Software the team uses every day.
A player request may begin in MyEC, reach an operator in Console and become a tracked piece of work in Mobius. IAM keeps the identity consistent while each product owns its part of the job.
Interactive demo · Playground sample data
Operate a live game network from one place.
Console brings rooms, servers, player records and moderation tools into one operational workspace. It is built for repeated work: information stays dense, actions stay close to their context, and permissions follow the operator.
One identity across every internal product.
IAM handles sign-in, applications and authorisation across the platform. Products can share an identity without sharing all of their permissions or business rules.
Turn feedback into work that can be followed through.
Mobius connects issues, discussions, testing and release work. The team can see where a request came from, who owns the next step and what happened before it shipped.
Give recurring team processes a proper system.
The HR Center handles applications, approvals, records and finance workflows. Clear states replace scattered messages, while each participant sees only the work relevant to them.
September 5, 2026
Operations overview
Match loadLast 12 hours
00:0006:0012:00
Cluster healthAll healthy
- BedWars96 rooms
- RuneLegend42 rooms
- Lobby12 nodes
Identity & access
Connected applications
EaseCation ConsoleOperations console
12 permissions MobiusProjects and issue tracking
8 permissions HR CenterTeam processes and records
6 permissions Latest sign-in verifiedPasskey · Shanghai · just now
Player experience / This week
High-priority follow-up
ABC
From 8 player reports
From player support
Platform team · this week
Test pool 7 / 9
Released to Playground
Good afternoon, Alex
4 items need your attention today
Recent processes
| Process | Initiator | Status | Updated |
|---|---|---|---|
| Event budget request | Sample member A | Pending | 10 min ago |
| Creator payment | Sample member B | Processing | 1 hour ago |
| Member onboarding | Sample member C | Completed | Yesterday |
A new product does not start from another login page.
The main products use React and TypeScript, with API contracts maintained alongside the code. Web, Android, real-time collaboration and Agent workloads use the runtime that fits them, while identity, interfaces and release practices carry into the next product.
React + TypeScript Product interfaces
Shared contracts Frontend and backend
Web + Android Reusable product capability
WebSocket + Yjs Real-time collaboration
Each kind of work runs where it fits.
Most interfaces are delivered close to the user. Stateless APIs and scheduled jobs run on demand; services that keep a WebSocket, a collaborative document or an Agent runtime stay online. Product data remains in standard databases and object storage.
01 People and clients
Players
Operators
Team
Lark
02 Product interfaces
MyEC
Console
IAM
Mobius
HR Center
03 Application services
Serverless APIs
Scheduled jobs
Persistent services
Agent runtime
04 Data and visibility
MySQL (RDS)
Redis
Object storage
SLS logs
Interfaces
Static delivery through OSS and CDN
On demand
Stateless APIs and scheduled work
Always on
WebSocket, collaboration and Agent runtime
Changes are tested away from production.
Every product has a separate Playground. A change is built and verified there first, then the same release moves into production. Health checks, structured logs and business audit events continue to show what happens after launch.
01
Playground
Build, integrate and verify
Isolated sample data 02
Production
Release the verified build
Live serviceOne request, one visible trail.
SLS brings request logs, service events and business audits into the same view. When something fails, the team can follow the request instead of reconstructing it from separate systems.
The platform can now do work through conversation.
Lark Agent uses Codex as its execution harness. It understands the current conversation, loads the API Skill for the task and calls the authorised product. The answer returns to Lark, while created work stays in the system that owns it.
EaseCation AgentOnline
Lark
Codex
API Skill
Mobius
Identity and access still follow IAM. The Agent only receives the access required for the current task.
One part of the platform is open to explore.
OpenMyEC contains the player interface, staff interface, shared packages and a mock backend. Developers can run the account and support workflows locally without connecting to EaseCation services.
View OpenMyEC on GitHubBuilt for EaseCation. Ready for harder problems.
The same team can design and deliver account systems, operational consoles, identity platforms, workflow products and enterprise Agent integrations. We start from the work that needs to happen, then build the smallest platform that can carry it reliably.