Backend and API development in Pune
Automotive suppliers around Pune live on their customers' systems. The carmaker publishes delivery schedules, expects an advance shipping notice before every truck leaves, sends quality notices when a part fails inspection, and changes the format of all three when it upgrades its supplier portal. Many suppliers still handle this by downloading files and retyping them into their ERP, which works until a schedule change is missed and a line at the customer's plant stops.
We build the backend that handles those exchanges automatically. Integrations with each customer's portal, EDI feed or API, run through queues with retries you can see and alerts when a message fails. Schedules flow into your ERP, shipping notices are generated from actual dispatches, and every message in and out is logged so a dispute can be settled with evidence. When a customer changes a format, only one adapter changes.
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 read the code, write down what it does versus what everyone believes it does, and give you the list of the five things most likely to page someone at night. Then we fix those first.
Usually queries, not architecture. We profile under real traffic, fix the plans and the indexes, and only then discuss whether anything needs splitting apart.
A mobile client, a partner integration, a public API. We design the contract first, version it properly, and write the docs your consumers will read.
Jobs that silently vanish, retries that duplicate charges, a queue nobody monitors. We make it idempotent, observable, and boring.
A moderated messaging backend where sends acknowledge in-band and the review runs behind them.
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.
Can you work in our existing codebase?+
Yes, and it is most of what we do. We do not require a rewrite as a condition of working with you. If we think a rewrite is genuinely the right call we will say so, with the reasoning and the cost, and you can decide.
What if the backend is in a language you do not list?+
Then we will tell you. We are useful in Node, Python and TypeScript. We can read Go and PHP well enough to migrate off them. We would not take a Rust or Elixir project and learn it on your budget.
Do you write tests?+
For anything with money, permissions or data loss in it, yes. We do not chase a coverage number. We will tell you which parts are covered and which are not in the handover notes.
Who owns the code?+
You do, from the first commit. Repositories live in your organisation. If we set them up, we transfer them before the first invoice.
What happens when the engagement ends?+
You get runbooks, architecture notes and a recorded walkthrough. We stay available for questions for a month at no cost, because a handover that needs us on retainer is not a handover.