Built in Tokyo.
Run from Miami.
Kakero is a two-person studio for the work that has to ship now and survive afterward. We pair a senior engineer with a senior operator and stop there. No layers, no offshoring, no slow-down.
Tokyo HQ
Engineering, security audits, and the Japan practice. Mornings spent reading code, afternoons in production.
Miami
Operations, scoping, and client relationships. Where the first call happens and the contract gets written.
How we got here.
First production system
Francisco ships his first commerce platform in Tokyo. Reads every CVE that ships against it for the next decade.
Security practice
After three years of incident response, Francisco starts taking standalone security audits alongside engineering.
Adrian joins
Adrian sets up the US practice. Scoping moves from "few weeks" to fixed-date, fixed-price.
AI engineering
First eval-driven LLM build for a fintech. The pattern becomes a third practice area alongside security and modernization.
Two markets, one team
Tokyo + Miami coverage. Two-person studio by choice. Booking through Q3 2026.
Small by design. Senior by default.
Kakero is a two-person studio. You work directly with the people doing the work — the engineer reading your code and the operator scoping your project. No account managers, no juniors, no B-team.
駆けろ — kakero. The Japanese imperative form of run. Said to someone who needs to move, now. We picked it because it's what every brief sounds like by the time it reaches us.