About
Engineers who stay
after the handover.
CodeGang is a software engineering company. We ship production AI, multi-tenant platforms and mobile apps for clients in Brazil, Australia, India, the USA and Europe, and we stay on to keep them running after launch.
500+
Projects delivered
most under NDA
100+
Clients served
BR · AU · IN · US · EU
20
Systems live
in production now
0
Account managers
you talk to the engineer
Why we exist
Software that ships, and then keeps shipping.
CodeGang exists because most studios optimise for the handoff: scope it, build it, hand you a repo, disappear. We do the opposite: the same engineers who scope a system stay on it after launch, so the thing that shipped on day one still works on day five hundred.
Standups, architecture reviews, release day: same people, every time.
The team
The people whoactually build it
“Good work compounds quietly, long after the launch post.”
Co-founderGourav Chakraborty
Chief Executive Officer
Architecture and the code that has to survive production.
If it can't survive production, it isn't finished.
Co-founderSubhadip Sasmal
Chief Technology Officer
Interfaces that respect the person using them.
Good design is the shortest path between a user and their goal.
Co-founderSushant Choudhary
Chief Operating Officer
Runs the engagements and keeps the roadmap honest.
Scope honestly, then ship exactly that.
Co-founderSourajit Mitra
Chief People Officer
Hiring, and keeping this a place senior engineers stay.
A team only works when everyone in it is genuinely trusted.
Co-founderSunny Srivastava
Chief Information Officer
Cloud, security and the pipelines every system ships through.
Boring infrastructure is the goal, not a compromise.
Nishika Jha
Head of Design
How every system looks and how it feels to actually use.
If a user needs the manual, the interface lost.
Sara Jones Duke
Head of Custom Solutioning
Onsite · USA
Shapes bespoke builds with clients before a line is written.
The right scope beats the clever solution, every time.
Abhrajit Ray
Founding Engineer
Builds and hardens the systems behind the case studies.
Simple systems survive. Clever ones page you at 3 a.m.
Sahib Dokal
Chief of Marketing/Sales
Building brand. Driving growth. Creating impact.
Good marketing doesn't just sell a product, it builds a movement people believe in.
How we build
Engineering your delivery pipeline,four layers, one accountable team
Product & Interfaces
Web, mobile and admin surfaces end users actually touch
Application Engineering
APIs, auth, business logic, third-party integrations
AI & Data Systems
RAG pipelines, deep-learning modules, ETL
Cloud Infrastructure
AWS / Azure, CI/CD, observability, security
What we do: We build production software, AI platforms, multi-tenant SaaS, mobile apps, ERP suites and healthcare systems, and then keep them running. Every category maps to something already live.
How we do it: Scope, build, ship, stay. Short cycles in your repository from day one, deployed into your cloud account, with the same engineers on maintenance afterwards.
Why CodeGang: There is no sales layer to get past and no delivery team you have not met. The engineer who scopes your system is the engineer who writes it.
Studio operating model
The value of a studio that doesn’t leave
A four-stage loop, not a four-stage project. Stay feeds straight back into the next Scope, so a system keeps improving instead of freezing the day it ships.
Scope
We agree what the system does and what shipping means, in writing.
Build
Short cycles in your repository, running before it is finished.
Ship
Deployed into your cloud account, reachable by a real user.
Stay
Maintenance and roadmap by the same engineers who built it.
Repeats for every release. Stay feeds the next Scope
Why the systems hold up
Production engineering: We combine architecture, cloud infrastructure and deployment practice to build systems that stay up, not just ones that demo well.
Applied AI: RAG pipelines, multi-LLM gateways and deep-learning modules embedded inside real business software, not a standalone demo bolted on afterward.
Design & usability: Interfaces the actual end user runs their day on: a nurse, a call-centre agent, a store manager, not just the buyer who signed off on the build.
The road so far
20 systems live,six of them in detail
Explore the work
Real systems,scroll to see more
Built for production
20
systems live in production right now, across Brazil, Australia, India, the USA and Europe, not prototypes, not staging environments.
A demo is easy. Software that survives a real customer, a real deadline and a real production incident is the actual job. Every system we ship follows the same five habits:
- Deployed into your cloud account, not a shared sandbox you have to migrate off later.
- CI/CD from the first commit, every system ships through the same pipeline it runs on in production.
- Code review on every change: nothing merges without a second pair of eyes from the studio.
- The engineer who built it maintains it: no handoff to a team that has never opened the repo.
- Weekly checkpoints, not milestones: you see real progress every week, not at the end of a quarter.
Our principles
What we’re opinionated about
Six things we hold the studio to, on every system regardless of client, budget or timeline.
Directness: We say the tradeoff, not the pitch. If a deadline or a budget doesn't work, you hear that in the scoping call, not after the invoice.
Ownership: The engineer who scopes a system ships it and stays on it. Nothing gets handed to a support desk that has never opened the repo.
Evidence: Every claim on this site links to a system you can inspect: a live URL, a Play Store listing, a case study with real screens.
Craft: Code the next engineer can read, including future us, six months into maintaining what we built today.
Momentum: Short cycles and a staging URL from week one. You watch a system grow; you don't wait for a reveal.
Candor: Bad news travels as fast as good news. A slipping estimate gets a message the day it slips, not the day it's due.
Who we build for