We built what we needed.
Tashi began in 2025 with a problem we kept seeing: small studios need backend infrastructure that well-resourced teams build in-house. So we built it.
Why Tashi
Small studios shipping multiplayer often build lag compensation, configure servers, hire for netcode, and hope launch goes well. Anti-cheat comes six months later, after cheating starts.
The solutions exist, but larger teams built them with dedicated infrastructure staff. A two-person team still has to build another product before using them.
Tashi packages those solutions for studios that cannot spend three months on netcode before writing game logic.
Our team
Two people in Singapore.
Amar was a gameplay engineer at a mid-size multiplayer game studio before founding Tashi. He was often handed server-side work, learning the cost of netcode problems without dedicated infrastructure staff.
Kenji works across network infrastructure and distributed systems. Before Tashi, he built real-time data pipelines at a financial services platform and worked on game server infrastructure at a mobile game company. His focus is low-latency state synchronization.
The pain point
A game we worked on shipped with static lag compensation: 80ms for every connection. Players near the server saw the same lag window as players across the continent.
The result was more than bad feel. High-latency players sometimes hit shots low-latency players never saw, because 80ms was too short for high-latency packets and generous to low-latency ones. Server hit registration was correct, yet confusing on clients.
A proper per-player adaptive system took months. We finished and thought: this should be an initialization call.
That is Tashi.
Talk to us
We reply to every real question. Developers evaluating Tashi or studios with integration questions can email us directly.
6 Battery Road, Level 20, Singapore 068809