oathDevs is a small, senior AI and software studio in New Delhi, founded in early 2026 by Apram Lamba and Avneesh Gupta. Nineteen builds across fourteen industries since — fourteen for clients, five of our own.
We both came from technical backgrounds and neither of us ever stopped being interested in where the technology was actually going. When AI started moving seriously, we did what we had always done — read the papers, pulled apart each model and tool as it launched, and built things with them to find out what they could really do rather than what the announcements claimed. That stopped being a side interest fairly quickly. oathDevs came out of it.
01
Apram Lamba
AI expert, design lead and client relationships
Owns design and the client relationship end to end, so the person you brief is the person accountable for what you get. Ideas are his half of the studio — new products, and routes through problems that have no known answer. What makes them worth anything is that he builds them: he has shipped AI tools, machine-learning models, real-time 3D and full applications himself, using AI the way this studio tells clients to use it.
He sets what a product does and how it should feel to use it. Avneesh runs the production engineering alongside him, and that is how two people ship at the pace this studio does.
Before this he spent eight years building and running Paradigm, an events company that brought big international artists to India — Russ, Diplo and Wiz Khalifa among them — and ran their shows on the ground across Delhi, Chandigarh, Jaipur and Goa, at crowds of ten to fifteen thousand people.
That run came to more than 500 events — over 25 music festivals, alongside college festivals and brand shows. Across 2023 and 2024 that included holding the main stage at Royal Enfield Motoverse in Goa — all programming and stage management for the three-day festival. That work teaches you to run something large and complicated to a fixed public date, with no second attempt available. Software delivery turns out to be a similar discipline.
02
Avneesh Gupta
Technical lead
Ex-Adobe and TCS. Owns the engineering: architecture, build quality and the decision about what is worth building in the first place.
Avneesh came up through infrastructure and automation before he built anything of his own. At Adobe he worked on the internal cloud, handling environment and deployment issues for teams across the business. At TCS he moved into RPA, automating repetitive back-office work on the H&M and Sanofi accounts. That is where the pattern he now builds around first became obvious: most of what a company calls process is repetitive work nobody has ever costed.
Around the two of us is a small in-house team of engineers and designers. It stays small deliberately — it is the size at which everyone knows every project and nothing gets handed to someone who was not in the room. We work out of Best Business Park, Netaji Subhash Place, New Delhi, with network partners across the UK, US, Canada, Dubai, Germany, Switzerland and Hong Kong.
Held between the two founders.
Microsoft Certified: Azure AI Engineer Associate (AI-102)Google AI Professional CertificateAnthropic Academy — Claude Developer Track
TRUST
Why clients trust us
We build it ourselves.
The people who scope your project are the people who write the code. Nothing is passed down to a junior once the contract is signed, and there is no account manager standing between you and the person doing the work.
We will tell you not to build it.
If a piece of software will not pay for itself, or an existing tool already does the job, we say so before you spend anything. We have talked clients out of custom builds more than once. It costs us work occasionally and it is the reason those clients keep calling.
You own everything, outright.
Source code, hosting accounts, keys, documentation — all yours, in your name, from day one. No per-seat licence, no platform fee, no dependency on us. If you wanted to hand the project to another developer tomorrow, you could.
We build so that you do not need us.
Every system ships documented, with error handling and logging, and a proper handover walkthrough for your team. A build that only its author can maintain is not finished, whatever it looks like on the surface.
We are still there after launch.
Handover is not the point where we stop answering. Most of our work comes from people we have already built for, or from someone they told.
Your work stays yours.
We work under NDA as standard. Several builds on this site carry the mark [ UNDER NDA ] instead of a client name, and they will stay that way — including the ones we would most like to put our name to. When your project is the one in the catalogue, you will get the same protection. We will ask before we publish anything, and a no costs you nothing.
NO
What we say no to
Some of the most useful things we can tell you are the things we turn down.
We do not take over somebody else's codebase.
Inheriting a half-finished system built by another team almost always costs more than building it properly, and it leaves everyone arguing about which problems were already there. If that is what you need, we will tell you straight away and point you towards someone who does it.
We do not work from templates.
And we do not put your logo on somebody else's product and call it custom. If that is the budget, a template is a legitimate answer — it is just not our answer, and we would rather say so than pretend otherwise.
We do not build things you do not need.
If an existing tool already solves your problem, that is the advice you will get, and it costs you nothing.
