Most of the software a business needs never gets built. Not because it is hard, but because there is nobody to build it with the craft it takes.
The name
In kabuki, Japan's classical theatre, there are people on stage the audience agrees not to see: the kuroko. Dressed head to toe in black, they move the scenery, hand the actor a fan at the right moment and change a costume in seconds, in full view.
Kuro comes from kuroko. Tomo (友) means friend. Kurotomo is the friend behind the curtain: we do the work so you can be the protagonist.
Black (in this context) means invisible. The actor shines; the kuroko makes it possible.
01
Writing code is faster today than it has ever been. Autocomplete and chat solved that part, and yet backlogs keep growing.
Because writing was never the bottleneck. The expensive part is everything else: working out what is actually needed, wiring it in, testing it, reviewing it, deploying it and not breaking anything along the way. That is where people's time goes, and that is where almost nobody has automated a thing.
02
What we automate is not the writing of code. It is the way professionals with 30+ years of shipping software actually work: the methods that held up, the decisions that avoided disasters, the lessons that were expensive to learn. That process was refined and polished over years.
That is exactly the difference from leaving a model to work alone. The model writes; the process decides when to understand, when to ask, when to test and when to stop and wait for a person. That is what anyone can now use, not only those with a veteran team in house.
03
Kurotomo is not another assistant suggesting lines while someone codes. It is the whole process: it picks up the ticket, refines it when it is ambiguous, implements it, tests it, opens the pull request and deploys.
The output is not suggested code in an editor. It is a working change, with its history and its audit trail, ready for someone to approve.
04
A system that runs unsupervised is not a promise, it is a risk. That is why the flow has gates: quality checks and human approval before anything reaches production.
You decide where each gate goes. The difference is that you stop walking every ticket from start to finish and only show up where your judgement changes the outcome.
05
This does not replace developers. It takes away the part of the craft nobody misses: the repetition, the glue between systems, the same deploy as always, the ticket that has been waiting two weeks.
What it gives back is time. Time for judgement, architecture and the problems that genuinely deserve a human mind. And time to not be stuck on a ticket list at eleven at night.
06
You pay per active project, not per ticket. Charging for delivered work punishes exactly what we want to happen: that you ask for more.
A project that is switched off costs nothing, tickets are unlimited, and each additional project gets cheaper. Every figure we publish comes from the same place your invoice does.
07
Your code stays in your repositories, your issue tracker stays yours, and your deploys keep their schedule. There is no platform to migrate to.
Every client runs on their own instance, with their credentials encrypted. And your data is not used to train any model: that is written in our privacy policy, not just here.
The best way to know whether this works for you is to hand it something to build.
