Judge us on the merge log
Every engineering company says it ships fast. Almost none will show you the number. Here is ours, how it is produced, the ways you can engage us — and the three things we cannot give you yet.
01 — Measured, not claimed
In the 90 days to 1 September 2026, across the whole estate.
GitHub search: org merged PRs, 90-day window, automated dependency bots excluded. 5,271 including bots.
Every merge above is attributable to one of them. No contractor churn behind the number.
Distinct non-bot PR authors in the same window.
Each with an owner, a changelog and someone on call.
Deployed brand applications and their APIs.
Applications, APIs, mobile apps and shared libraries under one engineering standard.
Repository count for the organisation.
On one product's front end, right-to-left included, as a layout mode rather than a fork.
Locale directories in the education web repository.
Versioned and reversible. We change live databases often, and safely.
Migration files in the education API repository.
Figures produced on 1 September 2026. Ask and we will send the exact query for any of them, or run it in front of you on a call.
02 — Three ways to engage us
Pricing depends on the shape of the work and the seniority it needs, so we quote after a scoping call rather than publishing a rate card that would be wrong for most of you. That call is free and it produces a written scope whether or not you engage us.
Dedicated pod
You have a roadmap and need throughput you can plan around.
A standing team — engineers plus a lead who owns delivery — working your backlog on a monthly basis. You get the same people week to week, they join your standups and your Slack, and the pod scales up or down with a month's notice. This is the model most agencies and scale-ups use with us.
Fixed-scope build
The thing you want is well defined and you want a price for it.
We scope it properly first — a short paid discovery that produces an architecture, a milestone plan and a fixed price — and then build to that. If discovery shows the idea is wrong, you keep the document and owe nothing further. Milestones are demoable, not status-reported.
Embedded specialist
Your team is strong but missing one capability.
One senior engineer inside your team for a defined stretch — an AI/LLM engineer, a platform engineer, a mobile specialist. They work under your process and your code review, and they leave documentation rather than dependency.
03 — The questions procurement asks
- Who owns the code?
- You do. Our standard client agreement assigns all work product to the client on payment, with a full waiver of moral rights, and every engineer on your engagement is under a written IP assignment to Codnov before they touch your repository. Pre-existing Codnov tooling that we bring to the work is licensed to you perpetually and irrevocably rather than assigned, and we list it explicitly in the SOW rather than burying it in a definition.
- Where does the work happen?
- In Kerala, India. Our engineers overlap with US Eastern time from roughly 06:30 to 11:30 ET and with US Pacific from 03:30 to 08:30 PT as standard, and pods on US engagements shift later to widen that. We do not sub-contract to a third party without telling you, and we will not put a name on a CV that is not the person doing the work.
- What law governs the contract?
- Our standard agreement is governed by the laws of India, with venue in the courts of Thiruvananthapuram, Kerala. For US clients we will sign under Delaware or New York law with arbitration seated in Singapore or London where your procurement requires it — say so early and it is a paperwork question rather than a negotiation.
- How do we pay you?
- Codnov AI Private Limited invoices in USD to a corporate account and is a registered Indian company, so the paperwork your finance team needs — a W-8BEN-E for withholding, a tax residency certificate, GST treatment for export of services — is routine rather than an exception. We provide all three without being chased.
- What happens if it is not working?
- Pods run on one month's notice, both directions, from month two. There is no termination fee and no minimum term beyond that. If you cancel we hand over a written state-of-play, the credentials and the deployment runbook within five working days — the same handover we would give an incoming team, because one day it will be.
04 — What we cannot tell you yet
You will ask these in due diligence. Here they are first.
- We do not hold SOC 2, ISO 27001 or HIPAA attestation. No audit has been performed and no readiness engagement is under way. If your procurement requires an attestation before signature, we are not yet the right vendor and we would rather say so now.
- No third-party penetration test has been performed against our own products. We run automated dependency and secret scanning and static analysis, and our controls are listed line by line on the security page.
- We have no completed external client engagement to reference, because the company was incorporated in July 2026. The systems on our case studies page are products we built and operate ourselves, and they are labelled that way.
Bring us something hard
A scoping call with an engineer, not a salesperson. You leave with a written architecture and a plan whether or not you engage us.