Web platform development in Pune
A supplier portal is a harder platform than it looks. A Pune tier-one supplier might deal with dozens of sub-suppliers, each with several users, all exchanging drawings, quality documents, approvals and corrective actions. One supplier must never see another's prices or drawings, an approval must record exactly who approved which revision, and the portal has to cope with users who log in twice a year and have forgotten everything.
We build these multi-organisation platforms in Next.js with the permission model at the centre. Organisations, users and roles modelled explicitly, access to every drawing and document enforced in the data layer, approval workflows with full revision history, and SSO for your own staff alongside simple, secure logins for suppliers. A support view lets your team see what a supplier sees without asking for their password.
Pune runs two economies inside one metropolitan area. It is one of India's most important automobile and manufacturing hubs, with plants in Chakan, Pimpri-Chinchwad and Talegaon; Chakan alone hosts vehicle plants for Mercedes-Benz, Volkswagen, Bajaj Auto, Mahindra and Jaguar Land Rover, surrounded by hundreds of component suppliers. It is also one of the country's largest IT hubs, spread across Hinjewadi, Kharadi, Baner and Viman Nagar. And it makes vaccines: the Serum Institute of India, the world's largest vaccine manufacturer, is here too.
The most interesting software problems sit where those economies meet. Carmakers expect their suppliers to exchange schedules, shipping notices, drawings and quality documents electronically, and to keep up when the format changes. Plants want to know why a line stopped, which machine keeps failing and what the real output was per shift, but the data sits in machine controllers, a manufacturing execution system, an ERP and a supervisor's register, none of which agree. Industrial software startups, often founded by engineers who know those plants from the inside, are building products to fix exactly that, and selling them in India and abroad.
Our place is the software above the machines, working alongside your automation partner. We build the integrations that read what your machines and systems already expose, the data pipelines and dashboards that turn it into one picture, the supplier portals, the mobile apps for technicians and inspectors, and the SaaS products that package all of it. Pune also has a deep bench of IT services and engineering services firms, and a firm like ours can take a specialist piece of their larger programme, delivered under their name.
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. Most of the work runs through your repository and a shared chat channel, and you talk directly to the engineer who writes the code. What we learn about your process, from calls, documents and photos of the floor, is written down as we go, so everyone works from the same picture.
We are the right fit for a defined build, an integration with an end date, or a product that needs to reach its first pilot plant before your own team is hired. Start with a fixed-price two-week piece and judge us on what ships. Pune's IT services and engineering firms can also 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 Pune teams.
How do you work with teams in Pune?+
We are in Bengaluru and share your time zone, so calls, reviews and releases fit inside your normal working day. We work in your tools, Slack, GitHub and Linear or whatever your team already uses, and you talk directly to the engineer writing the code. Photos, short videos and a walk-through call from the floor go a long way, and everything we learn is written into your repository as runbooks and architecture notes.
Can you connect to our machines and plant systems?+
Yes, through the data they already expose. We integrate with what your manufacturing execution system, historian, SCADA or machine gateways publish, whether that is a database, an API, a message broker or exported files, and build the pipelines, dashboards and apps on top. We work alongside your automation partner, who looks after the controllers, and help you specify any new data points worth adding to the line.
How does your rate compare to hiring in Pune?+
PayScale puts a mid-career software engineer in Pune at about ₹14 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 work white-label for our IT services firm?+
Yes. Work ships under your name, in your client's repositories and through your delivery process, and we sign an NDA before specifics. We stay behind your team unless you want us in the room. It works best for a well-defined specialist piece inside a larger programme, such as a data pipeline, a mobile app or an infrastructure migration, and the code belongs to your client from the first commit.
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.