Web platform development in Delhi NCR
Platforms sold to government departments and public sector undertakings in Delhi carry an authorisation model more complicated than most commercial software. Access follows the organisation chart: a district sees its own records, a state sees its districts, a ministry sees everything, and a nodal officer approves what a clerk proposes. Built as a role column and a few if statements, a model like that breaks the first time a department is reorganised or an officer is transferred, and the support team ends up editing permissions by hand.
We build these platforms in Next.js with the hierarchy modelled properly from the start. Scoped access enforced in the data layer, approval workflows with a record of who proposed and who approved, change logs that cannot be quietly edited, and transfers and reorganisations handled as data rather than code changes. Input validation, session handling and security headers are done properly from the first screen. If the platform is already live, we rebuild the permission model in increments and document each change.
Delhi NCR is not one market but three, joined by expressways and a metro. Gurugram is where much of India's consumer internet grew up: food and grocery delivery, travel, logistics, home services and fintech, alongside the Indian offices of many multinationals. Noida has a different mix, with large IT services firms, edtech, media and healthcare technology companies selling to hospitals in the US. Delhi itself holds the government, and with it every company whose customer is a ministry, a state department or a public sector undertaking.
The consumer companies share an operational problem. Their software coordinates people in the physical world, riders, couriers, technicians and sellers, on cheap phones and busy roads, and the backend has to cope with status updates that arrive late, twice or out of order. Many of them are now past the stage of growth at any cost and into the stage of unit economics, which turns engineering questions into money questions: what does each order cost to serve, and which part of the cloud bill is paying for nothing.
Companies that sell to government need software shaped like the organisation it serves. Access follows the organisation chart: a district sees its own records, a state sees its districts, a ministry sees all of them, and every approval has a proposer and an approver. Noida's healthcare technology companies need something similar for hospital customers abroad, with each customer's data kept firmly apart. Across all three cities the hiring market is crowded. The consumer companies, the multinationals and the IT services firms compete for the same senior engineers, so a defined piece of work often waits months for someone to own it.
We are in Bengaluru and share your time zone, so the working day is the same on both sides, and a problem raised in the morning gets a response that morning. You talk directly to the engineer who writes the code. Most of the work happens in your repository and a shared chat channel, and the decisions, runbooks and architecture notes are written down as we go for everyone who was not on the call.
We are the right fit when an NCR team needs senior capacity quickly: a defined build, a backend that has to stop losing orders, or the months while your permanent hire works out their notice. Start with a fixed-price two-week piece and judge us on what ships. Agencies and IT services firms can bring us in white-label under their name.
Four ways this arrives.
We replace the role column with a permission model that can express teams, access to individual resources and roles the customer defines, add SAML or OIDC sign-in, and write the audit log their security questionnaire will ask about.
Or very nearly did. We find every query that can cross a tenant boundary, enforce the tenant in one layer rather than in every handler, and add tests that try to read across that boundary on purpose.
We build the admin side properly: search across organisations, an audited view-as-user mode, and screens for access and usage. Support stops asking an engineer to run a query against production every time a customer says something looks wrong.
An early Next.js app with auth stitched into middleware, a custom server, and a release process that lives in someone's head. We move it forward in small steps, with preview environments and a pipeline anyone on the team can ship from.
A Next.js platform scoped per organisation, where an administrator can view the app as any other user and each Tableau report opens only for people granted it.
Read the write-up →Asked by Delhi NCR teams.
How do you work with teams in Delhi NCR?+
We are in Bengaluru and share your time zone, so calls, reviews and releases happen inside your normal working day, whether you are in Gurugram, Noida or Delhi. We work in your tools, Slack, GitHub and Linear or whatever your team already uses. You talk directly to the engineer writing the code, from the first 30-minute call onwards, and the decisions, runbooks and architecture notes are written down in your repository as we go.
Do you build for delivery and logistics companies?+
Yes. We build the systems that coordinate riders, couriers and technicians: order and shipment state that stays correct when events arrive late, twice or out of order, partner apps that keep working offline and upload proof of delivery when the network returns, and reconciliation that catches what still slips through. We also build the data pipelines that finally give everyone one answer to what an order costs to serve.
How does your rate compare to hiring in Delhi NCR?+
PayScale puts a mid-career software engineer in Gurugram at about ₹16 lakh a year. Our published rate is $35 an hour, with a $5,000 minimum. That buys a senior engineer who writes the code, works in your Slack, GitHub and Linear, and starts within days, with no recruiting round, notice period or employment overhead. Begin with a fixed-price two-week piece at $2,800 and judge us on what ships.
Can you take over a platform another team built?+
Yes, and it is a common way in. We start by reading the code and writing down what it actually does: the services, the background jobs, the parts only one person understood. The fixed-price two-week piece is usually the failure that costs you most, fixed and documented. At the end you have working code, a map of the system and a written plan for what comes next, all in your repository.
What is wrong with a role column?+
Nothing, until you have more than one kind of customer. A role says who a user is; most real questions are about what they can do to one specific thing, inside one specific organisation. Encoded as role checks, every new requirement becomes a code change in many places. We model permissions as data, check them in one place, and test them like any other logic.
Should we use an auth provider or build our own?+
Use a provider for identity: passwords, magic links, SSO and multi-factor. It is a solved problem and getting it wrong is expensive. Authorisation, meaning what a signed-in user may do, is specific to your product and usually belongs in your own code and database. We wire the first to the second and keep the line between them clear.
How do you handle multi-tenancy?+
Usually one database with a tenant ID on every row, enforced in one place: Postgres row-level security, or a data-access layer every query has to pass through, rather than each handler remembering. A separate database per tenant is sometimes right, for one very large customer or strict isolation, and we will say if that applies to you.
Where does it get hosted?+
Wherever suits your team. Vercel is the least effort for Next.js and fine for most platforms. If cost or long-running background work make that awkward, we run it in containers on Railway, AWS or your own Kubernetes. The repository, the cloud accounts and the bill are in your name either way.
What do enterprise customers ask for, and can you build it?+
Single sign-on through SAML or OIDC, audit logs, role management, session controls, encryption and data export. We build each of them into the platform and help you answer the technical questions on a customer's checklist accurately, so the security conversation speeds the deal up instead of stalling it.