Skip to main content

What are you looking for?

Explore our services and discover how we can help you achieve your goals

Client Workspace

US Companies Choosing Onshore, Nearshore or Offshore Developers: SOC 2, State Privacy Laws and a Zero-Overlap Working Model

A US company should choose by data and by how much live collaboration the work needs, not by location alone: onshore when the data or contract requires US persons, nearshore when daily live overlap is essential, and offshore, such as Netbase in Hanoi, when scope is written down and a zero-overlap handoff can carry it.

Book a solution review See the cloud ERP solution

By Huy Nguyen (David), Founder & CEO · Updated · 10 min read

star

Written by Netbase JSC, a software company whose only office is in Hanoi, Vietnam, so Netbase sells the offshore option this guide compares; the onshore and nearshore options are described only from public rules and sources, accessed 2026-11-17.

This guide is for a US CTO, product owner or compliance lead who must defend a delivery location in a security review. It sits under Netbase's custom software development service and adds a data-class matrix, location-neutral SOC 2 questions and the rules of a working model with no shared office hours.

In this guide

What actually differs between onshore, nearshore and offshore for a US buyer?

Three things change with location: shared office hours, the evidence a vendor must give for its controls, and how much of the work must be written down before anyone builds it. Code quality, stack and AI use depend on the team, not the location.

Onshore means developers in the United States, on the same legal system and close to the same hours. Nearshore usually means Latin America, where most capitals sit within a few hours of US time. Offshore means a different continent; for Vietnam, which stays on UTC+7 all year, the gap to New York is 12 hours in winter and 11 in summer.

The overlap arithmetic for an offshore team is blunt. Netbase's Hanoi office hours are Monday to Saturday, 9:00 to 18:15 Vietnam time. That window ends at 6:15 in the morning in New York in winter and at 3:15 in the morning in California, so a US team and a Hanoi team share no normal office hours at all. The time-zone overlap models guide compares live, windowed and handoff models by region; this page assumes the US case and asks what has to be true for zero overlap to work.

How do the three options compare on overlap, compliance and fit?

Option Shared office hours with a US team Compliance work that stays with you Choose it when
Onshore (US) Full or near-full day Vendor due diligence, contract terms and access reviews; no cross-border questions A contract, regulator or customer requires US persons, or the work is discovery-heavy with daily live decisions
Nearshore (Latin America) Most of the day, depending on the country The same review plus foreign employment, contract law and data-transfer questions per country Live pairing and same-day decisions matter more than written scope, and the vendor's controls survive your review
Offshore (Vietnam) None in normal office hours; handoffs are written The same review plus a stricter written scope, acceptance criteria and a handoff discipline Scope and acceptance criteria can be written before the build, data can be minimised or masked, and a fixed-price contract suits the work

Which data rules decide the location before cost does?

Start with the data the developers will touch: data sets the constraints, and cost only ranks the options that remain.

  • Public or synthetic

    Example
    Marketing content, generated test data
    Location rule of thumb
    Any model
    What the contract must say
    IP ownership and confidentiality
  • Consumer personal information

    Example
    Customer accounts, order history
    Location rule of thumb
    Any model, if the vendor works only on your instructions
    What the contract must say
    How the vendor helps you answer access, deletion and correction requests
  • Regulated records

    Example
    Health, payment or financial account data
    Location rule of thumb
    Any model only with masked or minimised data and the agreements your regulator requires
    What the contract must say
    The specific agreement your counsel names, plus access logging
  • Restricted to US persons

    Example
    Some government and defence work
    Location rule of thumb
    Onshore only
    What the contract must say
    The US-person clause itself

State privacy law is now the common case, not the edge case. According to MultiState, 24 states had comprehensive consumer privacy laws by 28 October 2026, after Alabama, Louisiana, Oklahoma and Vermont enacted laws in 2026. California's Attorney General lists the rights a consumer holds under the CCPA: to know, delete, correct, opt out of sale or sharing, and limit the use of sensitive data. The page states that the business, not its service provider, is responsible for responding to those requests.

None of those rights says where a developer sits; each is something your systems must do on request. A team in any location is acceptable if it can build and keep those request paths working.

What should a US buyer ask for as SOC 2 evidence, wherever the team sits?

SOC 2 is an attestation report, not a law and not a location rule. The AICPA describes it as an examination of a service organisation's controls relevant to security, availability, processing integrity, confidentiality or privacy. The same questions apply to an onshore, nearshore or offshore vendor:

  • Type and period. A Type II report covers how controls operated over a period, which says more than a Type I snapshot.
  • Scope. Check that the services you are buying, not only a different product line, fall inside the system the report describes.
  • Your own controls. Reports list the controls the customer is expected to run; for a development partner these are usually account provisioning, repository access and production approvals.
  • Gaps between reports. Ask what covers the months since the last period ended.

Netbase holds a SOC 2 Type II attestation and ISO 27001 certification for its own operations. Those cover how Netbase runs its work; they do not certify your product or your hosting, and your own audit still has to cover the system you operate.

How does a zero-overlap working model run day to day?

A zero-overlap model works when every hand-off carries enough for the other side to act without a meeting. These seven rules belong in the statement of work.

  1. Write acceptance criteria before the sprint

    Each item states what done means in a form both sides can test, so nobody waits a day to ask.

  2. End every Hanoi day with a written status

    What was finished, what is blocked, which decision is needed and the default the team will take if no answer arrives.

  3. End every US day with answers

    The product owner clears the decision list before logging off, so the next Hanoi day starts unblocked.

  4. Name a default for every open question

    A team that can proceed on a stated assumption loses hours, not days, when an answer is late.

  5. Keep one scheduled live call per week

    Planning or a demo at an edge hour, rotated so neither side always carries it.

  6. Agree an incident path in writing

    Who is called, by what channel and within what window when production breaks outside office hours.

  7. Review access monthly

    Accounts, repository rights and production approvals checked against the current team list, with the evidence kept.

One calendar detail helps a US client: the Hanoi Saturday falls on the US Friday evening and night, so work handed over on a US Friday afternoon can move before the US Monday.

Where AI fits

Netbase works with the major commercial and open-source AI tools and models, chosen per project. AI is part of how Netbase delivers its own projects. In a zero-overlap model, AI can draft the end-of-day status from commits and tickets, summarise review threads and propose test cases from acceptance criteria; engineers check every summary and test before it is sent, and a person still owns each decision on the list.

What delivery record exists, and what does not?

Most Netbase projects come from clients outside Vietnam, mainly in the United States and Europe, and Netbase has case clients in the USA. One US example is a multi-tenant cloud ERP for a US client, not named, where Netbase works as the offshore development partner on a SaaS product for small and mid-sized businesses. Another client record is the 4over4 print e-commerce work.

Most Netbase projects are delivered on fixed-price contracts; dedicated teams and project-based work are also offered. Delivery communication is in English. For custom development the client owns the IP created for it. Security practice includes secure code review, role-based access control, MFA for admin dashboards, and NDAs and DPAs on request, and Netbase follows CCPA practices for clients with US customer bases.

What does not exist. Netbase's only office is in Hanoi and every service is delivered remotely, so this guide does not point work restricted to US persons to Netbase. No Netbase record gives a measured delivery speed, defect rate or satisfaction score for zero-overlap work, and this guide quotes none. The SOC 2 and ISO 27001 statements above cover Netbase's own operations only.

Alternatives: how should you pick between the three?

Use three tests in order. First, the data test: if any data set is restricted to US persons, the answer is onshore for that work, and the rest can still go elsewhere. Second, the collaboration test: if the next three months are mostly discovery, with daily product decisions nobody can write down in advance, nearshore or onshore will waste less time. Third, the scope test: if scope and acceptance criteria can be written, offshore with a zero-overlap handoff is a fair choice, and a dedicated development team or an offshore development center are the two common shapes.

A split often beats a single answer: keep product ownership and regulated data onshore and send well-specified build, test and integration work offshore with masked data. Avoid offshore when your product owner cannot spend the last half hour of each day answering written questions.

Before the contract, read how to protect IP when outsourcing software development and the security questions to ask a software development partner.

What are the limits of this guide?

  • It is not legal advice. State privacy laws differ, and the count of states changes as new laws pass; check the current list with counsel.

Plan the next step with a Netbase consultant

Frequently asked questions

No. SOC 2 is an attestation report on a service organisation's controls, not a law about location. It asks whether controls such as access management and change approval are designed and operating, and a team in any country can be inside the scope of a report.

The consumer privacy laws described here set rights that your business must honour, such as access, deletion and correction, rather than a rule about where developers sit. Your contract should make any vendor help you meet those requests.

Yes, when scope and acceptance criteria are written before each sprint and both sides close their day with a written status or answers. It fails when daily decisions cannot be written down, which is the case for early discovery work.

Nearshore is the better choice when the work needs live pairing or several same-day product decisions, for example during discovery or a redesign, and the vendor's controls pass your security review.

Next step

Tell us which data your developers will touch and how your product owner works, and we will book a solution review to test the three location options and the zero-overlap rules against your project before any contract.

AI-enabled custom software development built around your workflow AI-enabled custom software development built around your workflow

Netbase provides custom software development for companies whose workflow no off-the-shelf product fits, from discovery through architecture, build, testing and handover, with AI where it removes manual steps and the IP left with you. Since 2012 Netbase has worked with 500+ businesses across 80 countries; according to the published USticker case study, design-tool users converted 40% more often.

Learn More
line
An AI-augmented dedicated development team in Vietnam that answers for results An AI-augmented dedicated development team in Vietnam that answers for results

Netbase provides dedicated development teams from Vietnam for product companies and enterprises that need engineering capacity. Teams of 3 to 30 people work only on your product, use AI-assisted engineering under review, report to a named account manager and project manager, typically start within one to two weeks after discovery, and the IP they create is yours.

Learn More
line
An AI-enabled offshore development center in Hanoi, when a long roadmap needs one An AI-enabled offshore development center in Hanoi, when a long roadmap needs one

An offshore development center (ODC) in Vietnam is a long-running engineering team that a partner abroad staffs, manages and documents for your product roadmap. Netbase runs ODC teams from its only office, in Hanoi, with AI-assisted engineering, weekly governance and knowledge transfer built in. When the work has a defined outcome, a fixed-price project usually fits better.

Learn More
line
Custom cloud ERP with AI forecasting and document capture: projects, finance, HR and CRM in one system Custom cloud ERP with AI forecasting and document capture: projects, finance, HR and CRM in one system

A custom cloud ERP from Netbase is one browser-based system where a growing company runs its projects, finance, HR and customer relationships on shared data, with AI that reads invoices and forecasts demand and cash. It suits SMEs that have outgrown spreadsheets but not their own way of working, on the foundation of Cloodo Workspace, which Netbase built and runs.

Learn More
line

Work with Netbase remotely

Every Netbase engagement is delivered remotely, so clients in any country and any industry can work with us; Netbase has worked with clients in 80 countries. Contracts and invoices are issued by Netbase JSC, and payment is made by bank transfer to Netbase JSC's company account or PayPal Business. Talk to the CEO, Huy Nguyen (David), on WhatsApp or by email.

Contact Netbase

Discuss a project

Netbase JSC helps organizations design, build, modernize, and operate digital products and AI-enabled business systems.
Project enquiries

project@netbasejsc.com

WhatsApp

+84 937 869 689

Office address

91 Nguyen Chi Thanh, Dong Da, Hanoi, Vietnam

Get in touch

Tell us what you want to build, modernize, or operate.

Tell us what you want to build, modernize, or operate.

Contact Netbase