Insights
Nearshoring software development to Turkey: time zones, contracts, and IP
Nearshoring works when the working day overlaps, the contract says who owns what, and personal data stays where your obligations say it must. Each of those can be checked before a proposal is signed.
How much do working hours overlap?
Türkiye keeps UTC+3 throughout the year and does not change its clocks. Central Europe is on UTC+1 in winter and UTC+2 in summer, so Istanbul is two hours ahead in winter and one hour ahead in summer. Reorigin's office hours are Monday to Friday, 09:00–18:00 Europe/Istanbul. The table shows what that means in each region.
| Region | Offset from Istanbul | Istanbul 09:00–18:00 is |
|---|---|---|
| Central Europe, winter (UTC+1) | 2 hours behind | 07:00–16:00 |
| Central Europe, summer (UTC+2) | 1 hour behind | 08:00–17:00 |
| United Kingdom, winter (UTC+0) | 3 hours behind | 06:00–15:00 |
| United Kingdom, summer (UTC+1) | 2 hours behind | 07:00–16:00 |
| Saudi Arabia (UTC+3) | Same time | 09:00–18:00 |
| United Arab Emirates (UTC+4) | 1 hour ahead | 10:00–19:00 |
What belongs in the contract?
Three clauses matter more than the rate. Intellectual property: the default Reorigin discusses is that you own the product code delivered for your engagement and Reorigin keeps its pre-existing tools, and the signed agreement is the source of truth. Confidentiality: ask for an NDA when discovery will cover unpublished detail. Handover: the production deploy, monitoring, and operating notes should be named as deliverables.
Language is a practical clause too. Delivery at Reorigin is in English and Turkish, and the written proposal, the scope, and the handover notes are in the language you work in.
Where does personal data live?
A team in Istanbul does not require data in Istanbul. If your contracts say EU personal data stays in the EU, the product is deployed to an EU region, with backups and logs in the same place, and the region is chosen before the first deploy. We deploy to Cloudflare, AWS, and GCP.
Access is a separate question from hosting. Türkiye is not on the European Commission's list of adequacy decisions, so when engineers in Türkiye need to reach EU personal data, your counsel will want to decide the transfer mechanism, for example standard contractual clauses, or keep production personal data out of reach and work with test data. That is a legal decision. The engineering controls are in KVKK and GDPR for SaaS built in Turkey.
What does Reorigin not claim?
Reorigin has no office in Europe or the Gulf. Delivery runs from Şişli, Istanbul. The planning bands are the same wherever the buyer is: a custom software MVP at $2,000–$40,000 and a production SaaS MVP at $1,000–$30,000. They are planning ranges, not quotes. How delivery works for a European buyer is in custom software for European teams.
How does Turkey compare with Poland and Romania?
Poland and Romania are EU member states, so a vendor there works under GDPR and EU personal data sent to it stays inside the Union. Turkey is outside the EU, which is why the access question above exists at all. Poland shares Berlin’s clock and Romania is one hour ahead of it, so both overlap Central Europe more than Istanbul does. Istanbul is the only one of the three on the same clock as Riyadh.
If your contracts rule out any access to personal data from outside the EU, an EU vendor is the simpler choice and we will say so. The three locations are set side by side in software outsourcing to Turkey vs Poland vs Romania.
Can the contract be enforced across borders?
Arbitration is the usual answer. Turkey has been a party to the New York Convention on the recognition and enforcement of foreign arbitral awards since 1992, and the convention has 172 parties. Which law governs the contract and where the arbitration sits are choices for your counsel. One Turkish rule is worth knowing early: a transfer of economic rights in software has to be in writing and list each right. Both points are in the software development contract checklist.
What should the first two weeks look like?
Nearshoring goes wrong in the first fortnight or not at all. Agree one channel for decisions and one person on each side who can make them. Put the repository and the cloud accounts in your company’s name on day one. Fix a standing call inside the shared hours in the table above. Ask for something running in a production-like environment by the end of the second week, even if it does one thing. A vendor that cannot show working software early will not show it late.
Start with how we work, or contact the studio to schedule a discovery conversation.
Sources and further reading
- Adequacy decisions — European Commission list of countries with an adequacy decision.
- Standard contractual clauses — European Commission, for transfers outside the EU.
- Regulation (EU) 2016/679 (GDPR) — official text on EUR-Lex.
- Law No. 6698 on the Protection of Personal Data (KVKK) — the Turkish regime the Istanbul studio works under.
- EU countries — European Union, the list of member states.
- Status: New York Convention — UNCITRAL, the list of parties and accession dates.
FAQ
What time zone is Turkey in for nearshore work?
Türkiye is on UTC+3 all year. Istanbul is two hours ahead of Central Europe in winter and one hour ahead in summer, and at the same time as Saudi Arabia.
Who owns the code when I nearshore to Turkey?
Whatever the signed agreement says. The default Reorigin discusses is that you own the product code delivered for your engagement and Reorigin keeps its pre-existing tools and libraries.
Can data stay in the EU if the team is in Istanbul?
Yes. The product can be deployed to an EU region with backups and logs there. Whether and how engineers in Türkiye may access EU personal data is a transfer question for your counsel.
Does Reorigin have an office in Europe?
No. Delivery runs from Şişli, Istanbul, in English and Turkish, Monday to Friday 09:00–18:00 Europe/Istanbul.