Vadodara
Our officeOur one office, and everyone who would work on your project sits in it. The address is published, and it is an office you can actually turn up to.
Your working day and ours are the same one.
The Vadodara officeWhere work is done
One office, five cities, and a working day you can check against your own clock
We have one office, and it is in Vadodara, India. Everyone who would work on your project is in India.
Every city we list, apart from Vadodara, is here because companies there hire us, not because we have anyone in it. If yours is not one of them, nothing below changes except the clock arithmetic. The Vadodara address is published, and it is a real working office.
Our working day is Monday to Friday, 10:00 to 19:00 IST. That is 04:30 to 13:30 UTC, every week of the year, because India does not change its clocks. Yours probably moves twice a year. Ours does not, so you can convert that window once and it stays converted.
Which leaves three things that genuinely change depending on where you are. How many of our hours land inside yours. Whether your own clock shifts in the summer. And whether you can sit in the room with the team.
A claim about presence is easy to make and hard to test. These three are the opposite. Each one comes with the thing that proves it.
Three things you can check before contacting anyone
One office
Office 501, Privilege Avenue, Behind Atlantis, Sarabhai Campus, Sarabhai Road, Vadiwadi, Vadodara, Gujarat 390007, India. Everyone who would work on your project is in India, and this is our one office. There is no second address, in any country, and no desk we could point at in any other city.
One legal entity
Atyantik Technologies Private Limited, a private limited company registered in Vadodara, Gujarat, India, CIN U72300GJ2015PTC083687. Wherever you are, that is who signs and that is who invoices you. There is no separate local company anywhere else.
One working day
Monday to Friday, 10:00 to 19:00 IST, which is 04:30 to 13:30 UTC every week of the year. India observes no daylight saving, so the window never moves. Convert it to your own clock and you know what you are buying before you speak to us.
Five cities
What changes from city to city
One of these is our office. We have nobody in the other four, and what moves between them is where our day lands on your clock.
London
Area we serviceOur day runs 04:30 to 13:30 on your clock through the winter and 05:30 to 14:30 once the clocks go forward. Against a nine to five that is four and a half hours of shared time in winter, five and a half in summer.
The one city here where a standing meeting is easy to arrange.
Where the London hours landNew York
Area we serviceEastern time. Our day ends at 08:30 on your clock through the winter and 09:30 once the clocks go forward, so a team starting at 08:00 catches the last half hour, or the last hour and a half in summer.
Everything else moves by written handover.
The New York handoverToronto
Area we serviceThe same Eastern clock as New York, so the same answer. Our day ends at 08:30 on your clock through the winter and 09:30 once the clocks go forward.
The same company signs, wherever you are.
The Toronto arrangementSan Francisco
Area we serviceOur day ends at 05:30 on your clock through the winter and 06:30 in the summer. No hour of ours falls inside a normal working day there, in either season.
Fully asynchronous, and what happens in the nine hours your office is closed.
How San Francisco work runs
Every city we work with, grouped by region
If your city is not one of these, our working day is still the number that matters.
Americas
- New YorkHow work is handed over when almost none of our hours overlap yours.
- San FranciscoHow an engagement is run with no shared working hours at all.
- TorontoThe same Eastern clock, answered for a Canadian company.
- MiamiUnited States
- PhiladelphiaUnited States
- BostonUnited States
- Washington DCUnited States
- SeattleUnited States
- San DiegoUnited States
- Los AngelesUnited States
Europe
- LondonWhat four and a half hours of shared time actually buys you.
Asia Pacific
- VadodaraThe street address, and what an arranged visit involves.
How many of our working hours land inside a local nine to five
Show data table
| Dimension | Standard time | Summer time |
|---|---|---|
| London | 4.5 h | 5.5 h |
| New York | 0 h | 0.5 h |
| Toronto | 0 h | 0.5 h |
| San Francisco | 0 h | 0 h |
London has real shared time in both seasons. Our day runs 04:30 to 13:30 London time through the winter. Once the clocks go forward it is 05:30 to 14:30. Against a nine to five that is four and a half hours in winter. In summer it is five and a half. A standing meeting there is easy to arrange. New York and Toronto keep the same clock, so the answer is the same in both. Our day ends at 08:30 on your clock through the winter and at 09:30 once the clocks go forward. Almost all of it happens while you are asleep. A team starting at 08:00 catches the last half hour in winter and the last hour and a half in summer. San Francisco has none in either season. Our day ends at 05:30 through the winter and 06:30 in the summer, so no hour of ours falls inside a normal working day there. Vadodara is not on the chart, because there the question does not arise. Our working day is 10:00 to 19:00 and so is yours.
How the work runs, whatever your number was
The overlap figure changes how a project is run day to day. It does not change whether it can be run.
- Our default keeps developers on Atyantik hours, because a rested developer ships better code than a tired one.
- Where a live standup or sync is needed, a project coordinator can host it.
- An overlap shift can be arranged on request. It is somebody's evening, so we agree it rather than assume it.
- Overlap commitments are agreed at scoping, so what you get is settled before anything starts.
Five answers that are the same wherever you are
These are the questions procurement asks first. The answer is identical wherever you sit, which saves you asking it once per city.
| What you are asking | London | New York | San Francisco | Toronto | Vadodara |
|---|---|---|---|---|---|
| Who you contract with | Every cityAtyantik Technologies Private Limited, India | ||||
| Where the code and deployments live | Every cityYour repositories, your cloud accounts | ||||
| Who you talk to | Every cityA lead software engineer, in India | ||||
| Support acknowledgement targets | Every citySame, and bounded to our hours | ||||
| Certifications held | Every cityNone. Built to pass yours | ||||
On certifications the full answer is this. We do not hold SOC 2, GDPR or HIPAA certifications ourselves. We engineer systems that pass your audits. We document architectural decisions in the technical requirements specification so your compliance team can verify the design intent. If your engagement needs a certified vendor, we will tell you upfront and refer where appropriate.
Those five answers hold in London exactly as they hold in Vadodara. Our answer to each of them is the same in every market, so if your question is one of them, you already have it.
Support targets, and the hours they run inside
| Priority | Acknowledged within, Monday to Friday 10:00 to 19:00 IST |
|---|---|
| P1 | 4 working hours |
| P2 | 24 working hours |
| Everything else | 72 working hours |
That is acknowledgement by a named person who engages with the issue. It is not a fix, because how long a fix takes depends on what the issue turns out to be.
The clock runs inside those hours only. Raise a P1 at 11:00 in London and it is inside our day in either season, so the four hours start when you raise it. In New York and Toronto our day ends at 08:30 on your clock in winter, 09:30 in summer. Anything raised after that waits for the next morning in India. In San Francisco our day has closed by 05:30 in winter and 06:30 in summer. A P1 raised in your working day always starts its clock when ours opens.
The P2 and 72 hour targets work the same way. All three are counted in working hours inside that window, not in elapsed clock time, so a Friday evening in San Francisco is a Monday morning in Vadodara.
What the arrangement has covered so far
This is not a new way for us to work. We have been running projects from Vadodara since 2015, for companies that are somewhere else. The distance is not something we are trialling on you, and this is the reach it has added up to.
50+engagements
7countries
Since 2015working this way, from one office in India
Source: Atyantik's own figures.
*Disclaimer: All of them run from India.
Seven countries counts where that work was for, not where we are. All of that work was done from one office in Gujarat, by people working Monday to Friday, 10:00 to 19:00 IST. There is no office behind any of those seven flags.
References available when you are ready to verify.
Questions we get before anyone picks a city
Where an answer is specific to one city, it sits on that city's own page. The clock arithmetic is the main one that is.
Do you have an office in my city?
No, unless your city is Vadodara. We have one office: Office 501, Privilege Avenue, Behind Atlantis, Sarabhai Campus, Sarabhai Road, Vadiwadi, Vadodara, Gujarat 390007, India. Everyone who would work on your project is in India. Every other city here is listed because companies there hire us, not because we have anyone in them. There is no desk, no local representative and no second address.
Who am I actually contracting with?
Atyantik Technologies Private Limited, a private limited company registered in Vadodara, Gujarat, India, CIN U72300GJ2015PTC083687. That is the same wherever you are. There is no separate local company in London, New York, San Francisco or Toronto, and nothing about the contracting party changes depending on where you are.
Can we have a live standup?
Yes, and it is arranged rather than assumed. Where a live standup or sync is needed, a project coordinator can host it, or an overlap shift can be arranged on request. Our default keeps developers on Atyantik hours, Monday to Friday 10:00 to 19:00 IST, because a rested developer ships better code than a tired one. We agree overlap commitments at scoping, so expectations are clear from day one. This is not cover through your night, and we do not staff a desk while India is asleep.
How fast do you respond when something breaks?
Business hours are Monday to Friday, 10:00 to 19:00 IST. Within those hours we target acknowledgement by a named person within four working hours for a P1, twenty-four for a P2 and seventy-two for everything else. That is acknowledgement by someone who engages with the issue, not a fix, because how long a fix takes depends on what the issue turns out to be. Anything raised outside those hours starts its clock when they open.
Do you hold SOC 2, GDPR or HIPAA certifications?
No. We do not hold SOC 2, GDPR or HIPAA certifications ourselves. We engineer systems that pass your audits. We document architectural decisions in the technical requirements specification so your compliance team can verify the design intent. If your engagement needs a certified vendor, we will tell you upfront and refer where appropriate.
What if we do not have our own cloud accounts?
Then we set them up and hand them to you. If you have your own Git hosting, cloud accounts and storage, we work inside them. If you do not, we provision them, set them up, and hand the keys over. Either way the code lives in your repositories, deployments run in your cloud accounts, and both are yours from day one.
Who this works for, and who it does not
Two lists, at the same weight. The second one is where we say no, and we mean it. If any of those three is you, stop here and spend the time somewhere better.
- Your work can run on written handover plus a scheduled call, and code moving forward while you sleep is useful rather than alarming.
- You want the code in your own repositories and deployments in your own cloud accounts from day one, with the runbook yours if you offboard us.
- You are in Gujarat and want to sit in the room with the team.
- You need somebody at a desk through the whole of your night, every night. That is not the arrangement we run. A coordinator can host a live sync and an overlap shift can be arranged on request, and neither of those is cover from your evening to your morning.
- You need a person in your building. All of our developers are currently based in India, so if that is a requirement rather than a preference, we are the wrong call.
- Your engagement needs a certified vendor. We do not hold SOC 2, GDPR or HIPAA certifications, and we will tell you upfront and refer where appropriate.
None of those three is a soft no. Two of them have no destination we could honestly send you to, so we are not going to invent one. We would rather you stopped now than found out in week three, and we would rather you spent the budget somewhere it will work.
If none of them is you, start with the city you are in. The arrangement reads the same whichever one that turns out to be. The only thing that changes is how much of our day sits inside yours.
Four things worth repeating to whoever approves this
Most of what gets decided about a supplier is decided in a conversation the supplier is not in. These four survive that conversation, because each one can be checked by the person hearing it.
None of those four needs anybody to take our word for it. The hours convert with arithmetic that holds in every week of the year. From day one every line of code is your IP, in your own repositories. The address is on a map. These four hold wherever you are, and only the clock arithmetic changes.
Forward this part
Four things worth repeating to whoever approves this
- The working day. The working day is Monday to Friday, 10:00 to 19:00 IST, which is 04:30 to 13:30 UTC every week of the year.
- Code and deployments. Code lives in your repositories and deployments run in your cloud accounts. It is yours from day one, and you keep all of it, runbook included, if you offboard us.
- Who you talk to. You talk to a lead software engineer directly, plus a core team assigned only to your project. All of them are in India.
- One office. One office, in Vadodara. The street address is published, and it is a real working office.