Own the surface
The studio works on properties it can operate, measure, and improve directly.
Rootstar Studios builds from inside real operating problems: leagues that need tools, families that need care, characters that need memory, and infrastructure that needs to stay under the operator's control.
Founder and CEO of Rootstar Studios. Forty years of computing, 27 years in IT operations from 1999 to 2026, and a development practice built around directing AI agents like a distributed engineering team.
Built his first setup at age 9.
Started earning by wiring modular phone jacks so neighbors could get online.
Sold PC software through the Windows-era boom.
Bought the machine he thought was the ceiling the year he graduated high school.
Formal IT career begins, leading through field engineer, IT manager, and Director of IT.
Cambridge Emergency Communications Center. Answered the calls that couldn't wait — the instinct behind Tala's escalation design.
The operating model becomes the development model. The engineers are agents now.
Tim has been managing distributed technical work since 1999. Agent orchestration is not a pivot from operations, it is the natural extension of it. The engineers are agents now, but the work still depends on sequencing, inspection, standards, delegation, review, and production accountability.
The origin story is not nostalgia for old machines. It is the belief that computing gets interesting when a person bends the machine toward a human connection. Rootstar builds the thing that gets you to the thing: the call to your mother, the league that still feels alive, the character that remembers, the operating surface that lets one founder steer more than one founder should be able to steer.
The C64, the 486 DX/2, the LAN, the server, the model, the agent swarm. Different eras, same instinct.
Good systems come from sequencing people, tools, constraints, and timing until the work holds together.
Directing eight agents is still technical management: assign ownership, review output, integrate, verify, and ship.
The software matters because it keeps a family, league, world, or workflow connected.
Rootstar is built on a practical belief: the next studio advantage is not headcount, it is operator taste plus agent leverage plus production discipline.
The studio works on properties it can operate, measure, and improve directly.
Every product needs a real user path, not just an impressive prototype.
Rootstar prefers local-first systems, private state, and infrastructure the operator can reason about.
Documentation, verification, and repeatable deployment matter as much as the first launch.