Staff augmentation vs EOR vs PEO vs direct hire in Mexico: who employs whom, and who is exposed

Every model for putting a Mexican engineer on a US team answers the same three questions differently: whose name is on the engineer's contract, who decided whether that person is an employee or a contractor under Mexican law, and who is holding the risk if that decision is wrong. Most vendor pages skip the questions and go straight to the rate. This post answers them for four models, staff augmentation, employer of record, PEO-style shelter arrangements and direct hire, in one table, and then goes through the parts that trip buyers up: what "contractor" means in a partner-held engagement, who signs the IP assignment, what an overlap commitment looks like in writing, and what REPSE is and is not. CodersLink operates all four models, which is the reason we can answer from the contract rather than from a position; it is also a reason to read critically.

What is the difference between staff augmentation, EOR, PEO and direct hire in Mexico?

Staff augmentation: the vendor holds the engineer's contract and you direct the work. Employer of record: a provider legally employs a person you found, on your instructions. PEO or shelter: a Mexican entity co-employs or hosts staff you manage, often for a whole operation. Direct hire: your own Mexican entity employs the engineer. The difference is who signs, who decides classification and who is exposed.

The four are often sold as interchangeable "compliance" options. They are not. Two of them (EOR and shelter) exist to make employment legal for someone you already found; one (staff augmentation) exists to find, keep and replace the engineer as well as contract with them; one (direct hire) is what all the others are substitutes for. Where each sits in the CodersLink stack:

• Staff Augmentation and MESHubs: the engineer's contract is with CodersLink, in Mexico. You direct the work day to day.
• EOR: a mechanism inside Staff Augmentation and MESHubs, used when you bring the person; never a standalone product, and priced so that it does not compound on top of those engagements.
• Nearshore RPO and Direct Hire: you employ the engineer, by design, on your own entity or through a provider you choose.

PEO in the US sense (co-employment for payroll and benefits) does not map cleanly onto Mexican law; what US buyers usually mean by "PEO in Mexico" is a shelter or payroll-hosting arrangement in which a Mexican company is the legal employer of staff the client manages. Intugo and Human Resources Mexico (payrollmexico.com) are the archetypes, as described on their own sites in September 2026. We include that model below under "PEO / shelter" and note where the analogy breaks.

Who holds the contract and who is exposed under each model?

Under staff augmentation the vendor holds the contract and makes and carries the classification decision. Under EOR the provider is the legal employer and carries employment compliance; you carry the choice of person and the day-to-day direction. Under a shelter the Mexican host employs; you manage. Under direct hire your entity holds everything. Exposure follows the signature.

The row that matters most is the fifth one. In staff augmentation and EOR the party that signed the contract is the party that answers for it. That is the whole value of both models, and it is why the vendor's willingness to say so in writing is the first thing to test. A vendor that describes itself as "just a legal layer" is telling you it will not find or replace the engineer; a vendor that will not say whose contract the engineer is on is telling you something too.

What does "contractor" mean in a partner-held engagement?

In CodersLink Staff Augmentation the engineer is an independent contractor to CodersLink under a Mexican structure we designed; CodersLink is not a payroll function and does not describe itself as one. What the engineer receives on top of compensation is a voluntary engineer-care package: private major medical with dental and vision, paid time off, paid Mexican holidays, a home-office allowance, an end-of-engagement bonus and performance reviews.

This is the point most often misrepresented, sometimes by us in old copy and sometimes by competitors. Precision matters, so here is the exact position.

Engineers on Staff Augmentation contract with CodersLink as independent professionals under Mexico's simplified tax regime for individuals, and carry their own statutory obligations. CodersLink does not "handle statutory contributions" for them and does not say it does. What CodersLink does is run an engineer-care function: the benefits above are added back voluntarily and are stated as voluntary. The classification decision, contractor rather than employee, is ours to make and ours to carry as the contracting party. A marketplace does not do this; it matches you with a contractor and the relationship, and its risk, is between you and the individual.

Alcor, which sells an anti-outstaffing "R&D center" model, makes the sharpest public version of the argument against this arrangement: that a rented engineer is a legal layer between you and your team (alcor.com, September 2026). It is a fair challenge and the honest answer is in two parts. First, the layer is doing real work: sourcing from a community of 45,000 engineers with about 300 holding the Top 1% Standard at any one time, replacing without limit, and holding retention that we publish as 15% voluntary turnover and an 18 to 24 month average tenure. Second, when you want the layer gone, MESHubs is designed to transfer the team onto your entity, and NetProtect is the published case where that happened: a Guadalajara team grown from six to forty over eighteen months and moved to the client's own payroll (case study).

Who signs the IP assignment, and under which law?

In a partner-held engagement the vendor signs a present assignment of IP to you and flows the same assignment down to each engineer under Mexican law. In EOR and shelter models the assignment sits in the provider's employment template and must be checked. Do not rely on US "work for hire" language for anyone in Mexico; it does not transfer cleanly.

The IP question is the second of the nine that buyers ask and vendors rarely answer in writing. The mechanics in Mexico are not exotic but they are specific. The US concept of work for hire, under which the employer is treated as the author, does not carry over as written into Mexican contractor law. What does work is an explicit present assignment: the engineer assigns, now and not merely promises to assign later, all rights in the work product, worldwide and in perpetuity, and the vendor assigns the same to you in the engagement contract. That is how CodersLink contracts on Staff Augmentation and MESHubs, and it is one of the six diligence questions on our comparison hub.

Under an EOR the chain is the provider's employment contract with the engineer plus the provider's services agreement with you. The large platforms have invention-assignment clauses in their Mexican templates; read them, and read the governing-law clause, because the assignment has to be enforceable where the engineer lives, not where you are. Under direct hire it is your employment contract, and Mexican counsel should draft the clause. Under a shelter it is the shelter's template, which was probably written for back-office staff rather than software engineers; ask.

What should an overlap commitment look like in writing?

A committed window, in hours, tied to a named US time zone, with live standups as the default. CodersLink commits to seven to eight hours of daily overlap with US time zones; central Mexico is UTC-6 year-round since October 2022, so only the US side of the window shifts. Most vendors describe overlap; few commit to it.

This is the third question nobody answers in writing, and it is the one buyers say decides whether nearshore works at all. The geographic fact is simple: the Ley de los Husos Horarios (DOF, 28 Oct 2022) abolished daylight saving across most of Mexico, so Mexico City, Guadalajara and Monterrey sit on UTC-6 all year. Against a US Central working day that is seven to eight hours of shared time; against Eastern and Pacific the window is comparable and moves only when the US clocks do. What CodersLink puts in writing is the window and the working assumption that the engineer attends your standup live. What an EOR or a shelter puts in writing is nothing on this point, because they do not manage the engineer's day; that is by design and not a criticism.

The comparison with a nine-hour offset, and what the missing hours cost, is in nearshore vs offshore staff augmentation.

What is REPSE, and does it apply to your engagement?

REPSE is Mexico's registry of providers of specialised services, created by the 2021 labour reform that restricted outsourcing of core activities. It applies when a Mexican company supplies personnel to another company under a Mexican contract. CodersLink MX S.A. de C.V. holds a REPSE registration, and it applies to engagements contracted directly with that Mexican entity.

REPSE (Registro de Prestadoras de Servicios Especializados u Obras Especializadas) came out of Mexico's April 2021 reform to the Ley Federal del Trabajo, which prohibited the subcontracting of personnel for a company's core business and required providers of specialised services to register with the Secretaría del Trabajo y Previsión Social. Since then, any Mexican entity that provides personnel to another Mexican entity under a services contract needs to be on the registry, and the client needs to check that it is.

Two precisions that vendors, including us in older copy, have got wrong. First, REPSE is held by a Mexican entity, not a US one: the registration is held by CodersLink MX S.A. de C.V., and it is that entity's registration that applies when a client contracts with it directly. A US entity, including CodersLink LLC, is not registered under REPSE and it would be wrong to say it is. Second, REPSE is triggered by the Mexican contracting structure, not by nationality: if your contract is with a US vendor entity, the analysis is different, and your Mexican counsel should look at it. The right question to ask any vendor is "which of your entities will my contract be with, and is that entity REPSE-registered?"; the answer should name an entity and a registration, not a country.

What REPSE is not: a guarantee about classification, IP or anything else in this post. It is a registry, and being on it is the floor, not the ceiling. Mexican payroll and shelter providers, such as Human Resources Mexico, publish their REPSE status and are right to; it tells you they can lawfully host staff. It does not tell you whether they can find an engineer.

Which model should you choose?

If you already have the candidate and make one or two international hires a year, an EOR at a published flat fee is cheaper and faster than any staffing partner. If you are opening a whole operation, a shelter or your own entity. If you need to find and keep ten engineers in Mexico and have no pipeline there, staff augmentation, graduating to a hub. If you have an entity and want volume, RPO into direct hire.

The one thing every model has in common is that the rate card comes last. On CodersLink's side the structure is published for every service and the starting rates are too: Staff Augmentation from $6,500 (mid-level), $7,500 (senior) and $10,500 (staff+) per engineer per month, all-in by role family; MESHubs at a standard 15% markup and as low as 12% on expansions of ten or more full-time engineers. We never take a cut of the engineer's pay. The Mexico Tech Salaries Report 2026, with 10,246 verified respondents across 36 roles and 32 states, is the compensation baseline under any of those numbers.

What should you ask every vendor before you sign?

Six questions, and the answers should be sentences, not categories: who holds the engineer's contract and in which country; employee or contractor under that country's law, and who decided; what the engineer actually receives; who owns the IP and under which law; what hours overlap and whether they will join your standup; what happens when a hire does not work out.

1. Who holds the engineer's contract, and in which country? CodersLink: in Staff Augmentation, MESHubs and EOR, CodersLink, in Mexico. In RPO and Direct Hire, you, by design.
2. Employee or contractor under that country's law, and who decided? CodersLink: our engineers engage through a Mexican contractor structure we designed and carry; the classification decision is ours.
3. What does the engineer actually receive? CodersLink: private major medical with dental and vision, paid time off, paid Mexican holidays, a home-office allowance, an end-of-engagement bonus and performance reviews, plus a dedicated success team.
4. Who owns the IP, and under which law? CodersLink: a present assignment of IP to you, worldwide and perpetual, in the engagement contract.
5. What hours overlap, and will they join my standup? CodersLink: seven to eight hours daily with US time zones; live standups are the default.
6. What happens when a hire does not work out? CodersLink: on Staff Augmentation, replacement is unlimited and free for the life of the engagement, and sourcing restarts within one business day. On Direct Hire and RPO, a 90-day warranty.

Ask the same six of Deel or Remote, of a shelter, and of every staffing firm on your list; the vendor pages on our hub, for example CodersLink vs Terminal (platform plus EOR) and CodersLink vs Revelo (talent cloud with payroll included), show where each has published an answer. If, after the six, the right model for you is an EOR at a flat fee, we will say so on the call. Book a 30-minute fit call.

This post is general information about engagement models, not legal or tax advice. Mexican labour and tax rules change; last reviewed September 2026. Take Mexican counsel on your specific structure.