Context
Operating a large game-account fleet is an infrastructure problem before it is anything else: accounts, access, state, health and process all need a control layer. The project grew from that operational need into a broader research platform.
Problem
Account fleets fail through unmanaged state — lost access, problems nobody notices until they compound, manual operations. The deeper goal raised the bar further: creating the technical environment in which autonomous game-playing agents can be trained and operated.
My role
Founder and technical lead. I designed the infrastructure architecture, organized the account management and server infrastructure, own product development, and formed the team around the project.
System
A control plane over account operations — infrastructure for managing the fleet and the processes around it — plus the technical environment for AI research: the systems an autonomous agent needs to be trained and to operate.
What I led
I lead a five-person team — technical direction, task ownership and payroll. Architectural decisions and infrastructure responsibility sit with me.
Current state
The platform is under active development. The AI program is a research direction — the goal is an agent that plays CS2 autonomously; it is not a finished capability and is not presented as one.
Facts
- Technical direction and infrastructure architecture for a large CS2 account fleet
- Account management and operational control systems
- Server infrastructure designed and organized for the project
- Product development managed end to end
- A five-person team formed around the project — task ownership and payroll are my responsibility
- Long-term goal: an AI/ML system able to play Counter-Strike 2 autonomously; I lead this research direction