Short answer: onshore means a team in your own country, nearshore means a nearby country with most of your working day in common, and offshore means a distant country with little or no overlap. Onshore costs the most and is the simplest to contract with. Offshore costs the least and demands the most discipline in written communication. Nearshore sits between. Choose based on how much live collaboration the work really needs, then judge individual teams on their shipped work, not their region.
What the terms mean from where you sit
There is no official definition. In practice "nearshore" means a time difference of roughly zero to three hours and a short flight, and "offshore" means everything further. That makes the map different for each buyer.
| Buyer in | Onshore | Typically called nearshore | Typically called offshore |
|---|---|---|---|
| United States | US-based agencies and freelancers | Canada, Mexico, Central and South America (Colombia, Argentina, Brazil and others) | Central and Eastern Europe, Türkiye, South Asia, Southeast Asia |
| Canada | Canadian agencies and freelancers | The United States (nearby but not cheaper), Mexico, Latin America | Europe, Türkiye, South Asia, Southeast Asia |
| United Kingdom | UK agencies and freelancers | Portugal, Spain, Poland, Romania, the Baltics, Ukraine, the Balkans, Türkiye | South Asia, Southeast Asia, Latin America |
| Australia | Australian agencies and freelancers | New Zealand, and Southeast Asia (Vietnam, the Philippines, Indonesia, Malaysia), where the difference is about two to four hours | South Asia (sometimes counted as nearshore), Europe, Türkiye, the Americas |
Two points follow. First, a vendor's own label is marketing: an Eastern European studio will call itself nearshore on its UK page and may avoid the word offshore on its US page, though it plainly is. Second, for a Canadian buyer the nearest "nearshore" market, the US, is more expensive than home, which shows that the label describes geography and the decision is about something else.
Comparison at a glance
The cost bands are planning estimates for experienced agency teams, consistent with the rate table in the MVP cost guide. They are not survey data, and individual quotes fall outside them in both directions.
| Onshore | Nearshore | Offshore | |
|---|---|---|---|
| Approximate hourly rate band (USD) | $100–$200+ in the US, UK, Canada and Australia | Roughly $35–$100, depending on the region | Roughly $20–$80, depending on the region |
| Working-hour overlap | Full, or close to it across a large country | Most of the day: five to eight hours | Zero to three hours; sometimes none |
| Travel | Same-day meetings are possible | A short flight; a quarterly visit is practical | Long-haul; most engagements are fully remote |
| Legal familiarity | Same law, same courts, standard local contracts | Foreign law, sometimes within a shared framework, such as EU data protection rules for European vendors | Foreign law; enforcement is slower; practical controls carry more weight |
| Payments and tax | Domestic invoices and sales tax or VAT as usual | Cross-border invoice; ask your accountant about withholding and reverse-charge rules | Same as nearshore |
| Talent pool | Deep but expensive and competitive | Deep in established hubs | The largest overall; the widest spread between the best and worst teams |
| Language and working culture | Shared | English is common in established hubs; business norms are often close | Varies most; test it directly |
| How it tends to fail | The budget runs out before the product is finished | Paying a premium for overlap the project does not use | Misunderstandings discovered late, because questions waited overnight |
The honest trade-offs
Onshore
What you get. Conversation without scheduling, in-person workshops, a contract under familiar law, and a team that knows your market's conventions for payments, tax, privacy and consumer expectations without being told. For regulated products, or where stakeholders insist on meeting in person, this can be decisive.
What you give up. Budget. At two to three times the rate, the same money buys a narrower first release or a shorter runway. A high rate is also no guarantee of seniority: some onshore agencies sell locally and deliver through offshore subcontractors, so ask who writes the code, whatever the location.
Nearshore
What you get. Most of the convenience of onshore at a noticeably lower rate. Questions get answered within the hour, pairing and workshops are possible, and a visit is a short trip.
What you give up. Some of the saving, since popular nearshore hubs have risen in price as demand grew. The contract is still cross-border, so the legal and tax points are the same as for offshore. And the comfort of overlap can hide weak process: a team you can call at any time may never be pushed to write things down.
Offshore
What you get. The lowest cost for a given level of seniority and the largest pool to choose from. A time difference can also be put to use: feedback sent at the end of your day is addressed by the next morning, and a team ahead of your time zone can deploy and test while your users sleep.
What you give up. Spontaneity. Every ambiguity costs a day instead of five minutes, so vague specifications become expensive. Someone has to take calls at an awkward hour, and it should be agreed who. The spread in quality is wide, so vetting takes more effort, and you cannot fall back on a convenient local court if things go wrong.
What location does not tell you
- Code quality. Disciplined and careless teams exist in every country. Judge shipped products, a sample of code and the quality of the questions asked about your brief.
- Communication. Written clarity is an individual skill. A short paid discovery phase tests it better than any assumption about a region.
- Reliability. It comes from process: visible progress, staging demos, code pushed continuously to a repository you own.
Decision rules
| If this describes you | Lean toward |
|---|---|
| Requirements are still forming and you want daily working sessions | Onshore or nearshore, at least for discovery |
| Scope is written, the budget is tight, and you are comfortable working in writing | Offshore or nearshore |
| Procurement, regulation or a client contract requires a domestic supplier or in-country data handling | Onshore, or a split where sensitive parts stay onshore |
| You have no technical person and have never managed a software project | Any location, but choose the team with the strongest written process and budget for an independent technical adviser |
| You need production support during your business hours | A team whose day covers yours, or an explicit on-call agreement |
| You plan a long-term product team without hiring locally | Nearshore or offshore on a monthly engagement, with overlap agreed in the contract |
Whether to use an outside team at all is a separate question, covered in in-house team or outsourced development. Whether that outside team should be a company or an individual is covered in agency versus freelancer.
Making a distributed engagement work
These practices matter in proportion to the time difference. With eight hours of overlap they are good habits. With two they are the project.
- Put the overlap window in the agreement. Named hours, in both time zones, with a note on what happens when daylight saving shifts them. Schedule the weekly demo and any standing calls inside it.
- Write specifications that survive the night. Each task should have acceptance criteria and a design reference clear enough that a developer can finish it without asking. Where a question is likely, answer it in advance.
- Make decisions in the tracker. A decision made on a call is written up the same day by a named person. Six weeks later nobody remembers the call.
- Use recorded walkthroughs. A five-minute screen recording of a finished feature, or of a bug, replaces a meeting and can be watched at any hour.
- Keep a staging environment you can open yourself. Progress you can click through is the only progress report that cannot be misread.
- Agree response times, not availability. "Blocking questions answered within one working day, urgent production issues within two hours during these hours" is workable. "Always reachable" is not.
- Appoint one decision-maker on your side. With a time difference, a question that waits for an internal debate costs two days instead of one.
- Own the accounts from day one. Repository, hosting, domains and store accounts in your company's name, with the vendor given access. It removes most of the risk people associate with distance.
- Start with something small and paid. A discovery phase or a first milestone shows you how the team writes, estimates and reacts to feedback before the large commitment.
- Plan the first week together. If a visit is practical, the kickoff is the time for it. If not, spend a few longer calls early, then settle into the written rhythm.
The contract side of a cross-border engagement, including IP assignment, handover and governing law, is set out in the checklist of clauses for a development agreement. The broader mechanics of choosing and engaging a vendor are in the guide to outsourcing an app or SaaS build.
Where BBR sits
BBR Studio Labs is an independent studio in Istanbul, working remotely and in English, with no offices elsewhere. Istanbul is on UTC+3 all year with no daylight saving, so the difference to your city changes by an hour when your clocks move. Plainly:
- UK and Europe: close to nearshore. Istanbul is two to three hours ahead of London, so most of the working day is shared. The page for UK clients covers the hours and the contract, VAT and UK GDPR points.
- United States: offshore. East Coast mornings overlap with the Istanbul afternoon and evening; Pacific time has no overlap within standard office hours, so calls need an agreed early or late slot. The US page goes through it zone by zone.
- Canada: offshore, with the same pattern from Halifax to Vancouver. See working with BBR from Canada.
- Australia: offshore. The shared window falls at the end of the Australian working day, and teams in Southeast Asia offer more overlap than Istanbul does. The Australia page explains how an engagement is run so that it does not depend on the overlap.
The cost position follows from the location: studios in Türkiye generally price within the nearshore and offshore bands in the table above, not the onshore one, for the same engineering effort. That is a statement about the market, not a BBR price list; a real figure needs a written scope. The working model is the one described in this article: a scoped roadmap with agreed acceptance criteria, working increments you can inspect, agreed meeting windows, and source-code handover with documentation. If a project needs daily in-person collaboration or a domestic supplier for regulatory reasons, an onshore team is the better choice and we would say so. For what BBR builds, see custom software development or, for ongoing work, the monthly product engineering engagement.