We build software, then we keep it running.

We began in 2019 as three engineers taking on the work larger agencies handed back: the integration nobody wanted to own, the platform migration that had slipped twice, the internal tool that was quietly holding a business together. The pattern was always the same. The hard part was not writing the code. It was understanding the system well enough to change it safely, and then staying long enough to see the change hold.

So we built the company around that second half. We write software, but we also carry the pager. We migrate the database, but we also watch the first month of production traffic. That changes how we design things from the first day: we choose boring, well-understood tools; we leave the code readable for the team that inherits it; we prefer a system that is cheap to operate over one that looks clever in a demo.

Today we are a team of engineers, designers, and one very patient project lead, working from Jakarta and Bandung. We take on a handful of clients at a time — enough to stay busy, few enough that a real senior engineer is on every project. We would rather turn work down than staff it thin.

We are not trying to be the biggest shop in the market. We are trying to be the one a CTO calls when the thing has to actually work.