Home/Company
The companySmall enough to know the code. Old enough to know the risk.
JupiterMint began in 2019 with three engineers and one rule we have kept through every hire since: nobody sells work they could not build themselves. Forty-two people later, that rule is still what the interview process is really testing for.
- 0
- Founded
- 0
- People
- 0
- Systems delivered
- 0
- Client retention
Most software does not fail with an outage. It fails quietly — a launch nobody adopts, a report nobody opens, an AI feature that demonstrates beautifully in March and is switched off by June.
In our experience that happens because the people deciding and the people building get separated too early. So we keep them together. The engineers who will write the code sit in the discovery sessions, talk to the people who will use the system, and know which number the engagement is judged on.
It makes estimates more honest and arguments considerably shorter. It is also, we think, why 98% of clients are still with us a year after the first release.
Remote-first across India and the EU. Six timezones, one backlog, one release calendar.
Five things we do not trade away
An estimate is a commitment
If a date is going to move you hear it the day we know, not at the steering meeting. Padding a number to feel safe is only lying more slowly.
You own everything
Code, cloud accounts, model weights and documentation sit in your organisation from the first commit. There is no proprietary layer you keep paying us to operate.
Something ships every week
Long invisible stretches are where programmes quietly go wrong. If there is nothing to show, that is itself the status report.
No unmeasured AI
Every model in production has an evaluation suite, a cost ceiling and a defined failure behaviour. If we cannot measure it, we do not ship it.
We say no early
We decline a meaningful share of enquiries. A badly matched engagement is expensive for you and demoralising for us, and both of us can tell inside two conversations.
Sound like the way you want to work?
Who you will actually be dealing with
Dewan R.
Founder & Chief Executive
Fifteen years building platforms before founding the company. Still personally reviews the architecture on every engagement, which is occasionally inconvenient for everyone.
Priya N.
Head of Applied AI
From a research background. Responsible for the rule that no model reaches production without an evaluation set, and unmoved by arguments against it.
Marek K.
Principal Engineer
Distributed systems, and the unglamorous work of making them inexpensive to run. Owns our infrastructure standards and the incident review process.
Ana S.
Design Director
Design systems that engineers are willing to build against, and motion that explains state changes rather than decorating them.
What procurement usually asks for
- SOC 2 Type II controls
- GDPR compliance & DPAs
- HIPAA-aligned delivery
- Professional indemnity cover
- Background-checked personnel
- Signed NDA before disclosure
- Source escrow on request
- Client references on request
Security questionnaires and insurance certificates are normally returned within two working days.
We hire slowly and pay properly
Remote-first, a real learning budget, no on-call theatre, and code review treated as teaching rather than gatekeeping. Currently open: Senior ML Engineer, Product Designer, Platform Engineer.