Game operations ecosystem · Engineering and operations for a fan-made game with an audience of millions.
↓ SCROLL FOR DETAIL
Game operations ecosystem
I lead engineering across a fan-made multiplayer game project and design and maintain its software and operations platform. Over three years, my work grew from small contributions into leading its engineering and product operations.
The platform connects analytics, moderation, support, traffic, partnerships, incident response, administrative tools, and internal team workflows across more than 10 production services.
2023–present · lead engineer and product operator · standleo.com ↗ · main channel ↗ · Python · Node.js · TypeScript · Next.js · Postgres · MySQL · Mongo · Telegram
Scale of the project I work on.
9M
unique accounts created over three years
0.8M
monthly active audience
440k+
subscribers on the main channel
80
admin operators using the internal platform
110k+
members in the main public chat
3,000
average concurrent players online
30k
report cases reviewed in 3 months
10+
separate services inside the ecosystem
What it is
The ecosystem is the set of tools the team uses to run the project. It brings player activity, incidents, moderation, support, and current work into one operational view. The development and admin teams use the same data and workflows.
Before I built it, metrics were spread across chats and incomplete dashboards, purchase fulfillment was split across several services, and moderation depended on manual coordination. Now those parts are connected and the team can see who is responsible for each piece of work.
The game is a fan-made project run by a small team. This case study covers the infrastructure, backend systems, automation, and operational software I built and maintain.
Since September 28, 2026, I have also taken on overall leadership of the project alongside my role as lead engineer.
Architecture
The repository is shown as a tree. Select a branch to see what it does, its stack, and its size. Classic and Lite are separate versions of the game with their own audiences.
Chat moderation now runs as an autonomous supervision service with contextual text and media review, automatic warnings and restrictions, persistent decisions, retry queues, and support appeal tools. Classic also has its own portal and store connected to the wider operations platform.
* Architecture snapshot as of October 6, 2026, from the local ecosystem repository. Sizes count tracked source lines, including comments and blank lines; tests, dependencies, data assets, generated files, runtime overlays, and deployment archives are excluded. Game client and backend repositories are separate.
ecosystem/148,442 LOC total
core_agent/50,226 LOC
main/27,456 LOC
apps/portal/11,303 LOC
apps/donate_bot/8,145 LOC
apps/promo_donate_bot/4,472 LOC
apps/promo_code_bot/2,298 LOC
apps/shared/852 LOC
administration/40,484 LOC
apps/support_bot/5,765 LOC
apps/ban_bot/1,250 LOC
apps/beta_access_service/2,789 LOC
apps/chat_moderation_bot/5,412 LOC
apps/partnership_bot/20,024 LOC
apps/anti_cheat_service/656 LOC
classic/23,747 LOC
app/11,081 LOC
apps/portal/4,773 LOC
lite/4,833 LOC
infrastructure/1,696 LOC
docs/7 docs
core_agent/
Operations AI agent
Reads project data, answers admin questions, and produces charts, daily finance reports, incident summaries, and community analytics across Main, Classic, and Lite. It retains follow-up context and operator memory. The configured model runs through OpenRouter; explicit tools access the owning services without taking over their data.
I lead engineering across the game project and oversee its overall direction and operations. My hands-on work covers infrastructure, backend systems, automation, development coordination, incidents, analytics, and community operations. I designed and built the software that connects those areas.
What it handles in practice
01
After an attack wiped a database containing 7M player records, I played a key role in restoring the live state within one week. Players saw no downtime, and moderation and fulfillment continued to run during the recovery.
02
One admin can generate up to 200 analytical summaries per month by asking questions in plain language. The agent keeps the context between follow-up questions.
03
Purchase flows from several providers share one state and fulfillment model, giving the team a consistent history instead of disconnected service records.
04
The main chat processes about 5,000 messages per day. Volunteers reviewed 30k cheater reports in three months, and the results are collected as operating data I can follow across cases and over time.
The work in practice
My role spans engineering leadership, product operations, the operations agent, and the production systems around the project.
AI engineer
The operations agent serves 80 admins. It answers questions with deterministic tools and SQL, remembers follow-ups, audits three chat categories, and produces audience and moderation reports. Failed requests stop with an explicit error.
Lead engineer
I lead the technical direction across the game project, including development coordination, infrastructure, backend systems, automation, and incident response, while continuing to build directly.
Product operator
I connect engineering work with moderation, support, partnerships, analytics, and the daily decisions needed to keep a large live project operating.
Fullstack
I built the core Python and Node.js services, the Mongo, MySQL, and Postgres data layer, fulfillment, admin tools, analytics, and the public Next.js site. The ecosystem spans more than 10 separate production services.
Private production evidence is available on request.
For serious hiring or partnership discussions, write to [email protected]. I can walk through the system, show selected parts of the source code, and provide a live walkthrough of relevant analytics or selected database records supporting the figures on this page without exposing raw user data.
