ABOUT
Two people who ship.
No account managers, no layers, no one to hide behind. You talk to the people writing the code.
WHY A KATANA
One cut, or none at all.
A katana is not sharp because it is heavy. It is sharp because every stage of making it — folding, shaping, tempering, polishing — removes something that did not need to be there.
That is the whole idea. Most software is heavy: bloated with features nobody asked for, built to fill a proposal rather than solve a problem. We would rather ship the thing that does the job and nothing else.
The name is a promise about what we take out, not what we add.
WHAT WE HOLD TO
Prices in the open
Every figure we charge is published. You should not have to book a call to find out whether you can afford us.
Scope before code
Nothing gets built until we both know what is being built. Almost every project that goes badly went badly here first.
Show, don't report
You see progress you can click on, not status updates you have to take our word for.
Say the awkward part
Non-refundable, out of scope, will take longer — we say it up front. A surprise at invoice time costs more than an honest conversation does.
WHO YOU WILL BE WORKING WITH
Lekhansh
Co-founder · Engineering
Builds the things you actually touch — interfaces, 3D, motion, the front end. Learned by shipping rather than by certificate, which shows in a preference for working software over neat diagrams.
Antariksh
Co-founder · Engineering
Drives the technical architecture, backend deployment, and deep system logic. Delivers unique value by treating infrastructure and code optimization as the most critical features of any reliable product.
WHAT WE BUILD
Still reading?
Then you are probably the kind of client we work best with. Tell us what you are building.