Software development for clients across India, run from one office in Pune

No. TantraDev has one office — C1304, C1305, 41 Evoke, Ravet, Pune, Maharashtra 412101 — and that is where the team works. We serve clients across India remotely and travel to your site for kickoff, workshops, UAT and go-live. If a vendor tells you it has a branch in your city, it is worth asking who actually sits there.

A written standup each working morning, a fixed weekly call with whoever owns the decisions on your side, and a fortnightly demo on a live environment rather than a deck. You hold the repository, the cloud account and the CI pipeline from week one, so you can see the work in progress at any point instead of waiting for a status report. Because we are all on IST, questions get answered inside the same working day.

Yes, and the trips are planned rather than improvised. Bengaluru, Hyderabad, Delhi NCR, Chennai, Ahmedabad and Kolkata are a direct flight from Pune; Mumbai is about three hours by expressway, longer into south Mumbai. We usually plan on-site time for discovery and kickoff, any workshop involving your existing systems or vendors, UAT with the operations team, and go-live week. Travel and stay are billed at actuals and the expected number of trips is written into the SOW.

As an ordinary domestic engagement. TantraDev Information Technologies LLP is an Indian LLP: an MSA with a per-project SOW, invoices in INR with GST applied as applicable and your GSTIN carried on the invoice so you can claim input credit, TDS deducted by you in the normal course, and Pune as the governing jurisdiction unless we agree something else. No cross-border paperwork, no currency conversion, no ambiguity about which law applies.

It moves privacy from a policy document into the schema and the code. Practically that means a consent notice tied to a specific purpose, consent recorded as data with a timestamp and version so you can prove what was agreed, retention and deletion that actually run rather than living in a wiki, a working path for a data principal to access or erase their data, and a breach process defined before you need it. Obligations under the Act and the rules made under it are being phased in and timelines have shifted before, so we design for the requirements themselves rather than a deadline — the architecture is the durable part.

Payments come first over UPI and mandates rather than saved cards, so success and failure states, retries and reconciliation get more design attention than the checkout screen does. Identity and documents flow through Aadhaar-based eKYC and DigiLocker, which means designing for the outage as well as the happy path. Invoicing carries GST logic. And the device on the other end is usually a mid-range Android phone on a connection that will drop — which pushes you toward offline-first storage, small payloads, restrained background work, and testing on the phones people own rather than the one on your desk.