EOR vs PEO vs Outstaffing in Belarus: Which Model Fits Your Company (and When to Switch)

Here’s a thing that happens to almost every foreign founder who decides to hire from Belarus.

You get on calls with three different providers in a single week. The first one calls what they offer “EOR.” The second calls what looks like the same thing “PEO.” The third uses the word “outstaffing,” and the structure they describe sounds suspiciously similar to provider number one. The proposals come in. One quotes $400 per employee per month. One quotes 12 percent of gross salary. The third quotes “cost-plus-22-percent” and you’re not entirely sure what “total cost” includes.

By Friday afternoon you’ve got a three-tab spreadsheet, a slight headache, and a growing suspicion that everyone’s using the same words to mean slightly different things.

Welcome to the Belarusian hiring market. The terminology really is messy, and that’s before you get into the legal differences that actually matter.

I’ll tell you something most comparison articles won’t. We sell all three of these services — EOR, PEO, and outstaffing. So we’re going to walk through when each one is the right choice and, more importantly, when each one is the wrong choice. The point of this article isn’t to convince you to pick the option with the highest margin for us. It’s to help you pick the one that actually fits your situation, even if that turns out to be different from what you walked in expecting.

We’ll cover what each model actually is under Belarusian law (which, spoiler, isn’t what your American lawyer thinks it is). We’ll get into real 2026 costs. We’ll talk about which model fits which situation. And then — the section most comparison pieces skip — how to switch when your situation changes, because most foreign companies eventually do.

What each model actually is, under Belarusian law

Most generic comparison content treats this as a quick definition section. I think that’s a mistake. The differences are legal-structural, and most foreign companies don’t fully grasp them until something goes wrong — a termination, an IP dispute, a regulatory inspection. By then it’s a bit late to be reading the contract carefully.

EOR (Employer of Record). A Belarusian legal entity becomes the formal, legal employer of the engineer. The employment contract is between them and the EOR provider. The provider handles the contract, payroll, tax filings, the 34 percent social security contribution, the 3.5 percent health insurance, benefits, statutory leave, sick leave, and termination compliance. You manage the engineer’s day-to-day work — assignments, performance, integration into the team — but you don’t carry the legal employer obligations.

The defining feature: full legal separation. You have no direct employment relationship with the engineer. If the engineer is terminated improperly, the EOR provider bears the labour-law risk, not you.

PEO (Professional Employer Organization). Co-employment. You maintain some form of legal employer relationship — typically because you have, or are setting up, a local entity — and the PEO provider handles HR and administrative functions on your behalf.

Important note for American readers especially: PEO in Belarus isn’t the same as PEO in the United States. The US has a statutorily-recognised co-employment structure with explicit liability allocation — something Globalization Partners and other global EOR vendors flag in their own documentation. Belarus doesn’t have that structure. “PEO” in the Belarusian market generally means the provider handles payroll, HR admin, compliance support, and benefits administration for a client who maintains some form of local presence or is in the process of building one. If your American lawyer hears “PEO” and assumes Belarusian PEO works like a US PEO, they’re going to be wrong about who carries which risk.

The defining feature: shared responsibility. The legal employer obligations stay (at least partially) with you. The PEO is an HR partner, not a legal substitute.

Outstaffing. A Belarusian provider company employs the engineer directly. You contract with the provider for the engineer’s services rather than for their employment. The engineer is on the provider’s books as an employee; you pay the provider an invoice each month covering the engineer’s salary, taxes, social contributions, and the provider’s margin. Day-to-day work direction comes from you.

The defining feature: the legal relationship between you and the engineer is a services contract, not an employment one.

Now here’s where things get confusing. From your perspective — the foreign client’s perspective — EOR and outstaffing in Belarus often look almost identical. Both involve a Belarusian provider employing the engineer. Both have you managing the day-to-day work. Both invoice you monthly. The structural differences sit in the contract terms and the fee structure, and they matter most when something goes sideways: termination, IP ownership disputes, regulatory inspections, or a change in your strategy.

The key thing to land here is this: these three terms describe genuinely different legal structures, but in the Belarusian market they’re used loosely. Don’t assume that because a provider says “PEO” they mean what a US lawyer would mean by that term. Don’t assume that because a provider says “EOR” they’re structuring it the way a Deel or Remote contract would structure it. Read the actual contract.

The three models, side by side

Here’s the comparison we use internally when we’re scoping with a new client. It’s also the version I’ll send people who ask me about this on LinkedIn.

Dimension	EOR	PEO	Outstaffing
Legal employer	Provider	Client (or shared)	Provider
Need a local entity?	No	Usually yes	No
Setup time	5–10 business days	1–3 months (with entity)	5–10 business days
Pricing structure	Flat $300–$600/employee/month, OR 10–20% of gross	Retainer + per-employee fee	Cost-plus markup, typically 15–25%
Termination risk sits with	Provider	Shared	Provider
IP ownership	Client (per contract)	Client (per employment terms)	Client (per services agreement)
HTP residency benefit	If provider is HTP-resident	Depends on client entity	If provider is HTP-resident
Best for headcount	1–15	10+ with entity	1–25
Switching cost (out)	Low to moderate	Low (you have entity)	Moderate to high

The choice usually comes down to four questions. How many people are you hiring in Belarus? How long do you plan to operate? Do you need a local entity for any other reason? And how much HR ownership do you actually want yourself? Answer those and the right model usually picks itself.

But — and this is the part I want you to internalise — “right now” and “six months from now” might pick different models. We’ll get to that.

What it actually costs in 2026

Let’s talk numbers. Real ones, current as of the writing of this article. If you’re reading this in 2027 or later, treat these as starting points and verify with whoever you talk to.

EOR pricing in Belarus. Two pricing models in the market right now.

Flat fee per employee per month. Range from roughly $300 on the low end to $600 on the high end, depending on provider, complexity, and what’s bundled in. Most established providers sit in the $400–$500 band for standard senior tech roles.

Percentage of gross salary. Typically 10–20 percent. The lower end (10–13 percent) shows up when the engineer’s salary is high enough that the percentage produces a comfortable margin in absolute dollar terms. The higher end (15–20 percent) shows up when salaries are lower and the absolute fee would otherwise be too small to be worth doing.

One thing the brochures don’t make obvious. Flat-fee pricing is often cheaper for senior engineers — 15 percent of $5,500/month gross is $825, but a flat $450 fee for the same engineer is, well, $450. Percentage pricing is often cheaper for junior or mid-level roles — 12 percent of $2,000/month gross is $240, versus a flat $400. So before you sign, do the math against the actual people you plan to hire. We’ve seen clients pick a structure that looked good on paper and then realise twelve months in that they were paying meaningfully more than the alternative would have cost.

Statutory employment costs that exist no matter which model you pick. These aren’t EOR fees — they’re the cost of legal employment in Belarus, and someone’s paying them regardless of which model is on the contract.

Social security contributions: 34 percent of gross salary, paid by the employer. Health insurance: 3.5 percent. A few smaller contributions for occupational injury insurance and similar, totalling under 1 percent. Add it all up and you’re looking at roughly 38 percent of gross salary in employer-side statutory costs before any provider margin. The current figures and rates are published on the Belarus government legal information portal and through the Ministry of Labour and Social Security.

For an engineer earning $5,000/month gross, employer-side statutory costs add roughly $1,900/month before any provider fee. That’s the price of legal employment in Belarus. Doesn’t matter if it’s EOR, PEO, outstaffing, or your own entity — someone’s writing that cheque. The Stack Overflow Developer Survey gives you reasonable benchmarks for the salary half of the equation; the statutory burden is what people forget to include in their internal modelling.

The HTP angle, which is where things get interesting. If the engineer is employed by a High Tech Park-resident company, the employer benefits from materially reduced statutory costs. HTP residents pay 1 percent of revenue rather than the standard tax burden, and individual income tax on engineers’ salaries is also reduced. This is a real cost differentiator, and it’s one that most generic global EOR comparison content doesn’t capture because it’s Belarus-specific.

If you work with a non-HTP-resident provider, you’re paying full statutory burden through the chain. If you work with an HTP-resident provider — which we are — you’re benefiting from the reduced rates. Worth verifying with any provider you evaluate. We handle HTP applications and ongoing residency as part of our standard service, both for our own EOR clients and for foreign companies setting up their own entity.

PEO pricing. Less standardised than EOR. Typical structure is a monthly retainer plus a per-employee fee. The retainer covers the HR and administrative service layer; the per-employee fee covers headcount-driven work. Total cost depends heavily on what’s included — entity setup support, HR consulting, benefits administration, recruiting, payroll, or some bundled combination. Hard to give a tight range here because providers structure these very differently.

Outstaffing pricing. Cost-plus markup. You pay the engineer’s full employed cost (salary plus statutory contributions plus benefits plus admin overhead) plus the provider’s margin, typically 15–25 percent. The advantage is transparency — the cost tracks 1:1 with the engineer’s actual employment cost. The disadvantage is that, at scale, the percentage markup can become more expensive than a flat-fee EOR for the same engineer.

Here’s the cost question that almost no comparison article addresses honestly: all three models include some form of provider margin. Pretending one is “margin-free” is silly — someone’s running a business on the other end. The question isn’t which model has no margin. It’s which margin structure makes sense for your specific headcount and salary band. We’ve put together a 2026 cost-to-hire breakdown that runs the numbers against current Belarusian salary ranges — worth a look before you sign anything.

When each model is the right choice (and when it isn’t)

This is the section that’s going to make this article useful or not. So let me be direct.

EOR is the right choice when: 

You’re hiring 1–15 people in Belarus and you don’t plan to set up your own entity. Speed matters — you need someone onboarded in 5–10 business days, not 3 months. You want full legal separation from employer obligations. You’re testing the Belarusian market and want exit flexibility. Your headcount is unpredictable, and you want to scale up and down without entity overhead. Or the engineer is critical and you can’t risk losing them to a slow contracting process.

EOR is the wrong choice when: 

You’re planning to scale beyond 15–20 people in Belarus and stay long-term. At that point the cumulative EOR fees outweigh the cost of running your own entity, and you’re paying a service premium for something you no longer need. You want to grant equity directly to the engineer — structurally complicated through an EOR. You have specific operational needs (executive presence, banking relationships, regulatory licences) that require a local entity. Or the engineer’s role has regulatory requirements that demand direct employment by your operating company.

PEO is the right choice when: 

You already have a Belarusian entity, or you’ve decided to set one up, and you want the HR and administrative work outsourced. You want HR partnership but want to maintain direct legal employer status — sometimes for regulatory reasons, sometimes for strategic ones. You’re scaling past the EOR break-even point and want to retain full operational control. Or you need ongoing HR consulting and compliance support beyond the basic EOR scope. Our HR consulting service often pairs with PEO arrangements for clients in this position.

PEO is the wrong choice when: 

You don’t have a local entity and don’t want to set one up. You’re much better off with EOR. You’re hiring fewer than 10 people, where the entity overhead doesn’t pay back. Or you want full legal separation from employer risk — PEO doesn’t give you that.

Outstaffing is the right choice when: 

You’re hiring engineers as part of a defined project rather than as long-term team members. You want a services-contract relationship rather than an employment-adjacent one. You’re working with a Belarusian development partner who already employs the engineers. The engineering work is being delivered as a deliverable rather than as ongoing employment. Or you want maximum flexibility on team composition — scaling individual engineers up and down without dealing with employment-lifecycle questions.

Outstaffing is the wrong choice when: 

You’re building a long-term core team where engineers should feel like full employees. The engineer’s relationship with your team needs to be employee-grade — equity, internal title progression, deeper IP commitments. Or retention matters more than flexibility. We see this last one a lot. Outstaffed engineers often have weaker ties to the foreign client because their employer-on-paper is the provider, not you. This affects retention in measurable ways and similar sources put the cost of replacing a tech employee at 50–60 percent of annual salary as a floor, and that’s before you start counting the institutional knowledge that walks out. We covered the full dynamics in our retention playbook, and the short version is: if you want the engineer to feel like part of your team, EOR is structurally better than outstaffing for that goal, all else equal.

When and how to switch models

Most comparison articles stop at the static comparison and treat model choice as a one-time decision. In our practice that’s rarely how it works. Foreign companies frequently outgrow their initial choice and need to migrate. The question isn’t whether you’ll ever switch — it’s how much friction the switch will cost when the time comes. I’d argue this is the most under-discussed part of the whole EOR/PEO/outstaffing question.

Four migration paths we see regularly, with what triggers them and how the mechanics typically run.

Outstaffing → EOR. Trigger: you realise you want the engineer to feel like an employee rather than a contractor. Maybe for retention reasons, maybe for IP-ownership clarity, maybe because the engineer themselves has asked. Mechanics: the EOR provider takes over the employment contract, the engineer formally transfers from the outstaffing provider to the EOR (sometimes the same parent company, sometimes not), and you transition from a services contract to an EOR services agreement. Typical timeline: 4–8 weeks. The risk to manage is continuity — the engineer’s employment record, vacation accrual, and benefits all need to transfer cleanly so the change feels administrative, not destabilising.

EOR → Direct entity employment. Trigger: headcount has grown to 15–20+ in Belarus and the cumulative EOR fees have started to outweigh the cost of running an entity. Or you want the operational and strategic benefits of having your own entity — banking relationships, executive presence, equity flexibility. Mechanics: you set up a Belarusian legal entity (typically as an LLC or representative office, depending on planned activities), and engineers transition from EOR employment to direct employment by the new entity. Timeline: 3–6 months for entity setup and migration combined. Most companies underestimate this one. The entity setup is the slow part, and there’s a transition period where engineers need to be formally re-onboarded.

EOR → PEO with new entity. Trigger: you’ve decided to set up an entity but you don’t want to take the full HR and compliance overhead in-house. Mechanics: similar to EOR → direct, but the new entity contracts with a PEO provider for ongoing HR and admin support. Timeline: 3–6 months. This is the path for companies that want the strategic benefits of an entity without the operational overhead of running one alone.

Outstaffing → Outstaffing with a different provider. Trigger: you’re unhappy with your current outstaffing partner. Communication problems, retention problems, quality problems. Mechanics: the new provider has to formally hire the engineers, who in turn have to formally resign from the old provider. This is the migration with the highest people-risk. Engineers may decide not to make the move, or they may use the moment to negotiate, or they may use it to leave entirely. Timeline: 4–6 weeks if the engineers cooperate, indefinite if they don’t.

The continuity challenge that breaks migrations. Every model migration risks the engineer’s experience. From their perspective, what they care about is: continuity of their employment record (which matters for mortgage applications, social security history, future job references), continuity of their accrued vacation and benefits, and continuity of their take-home compensation. Foreign clients sometimes try to migrate models without thinking about these things from the engineer’s side, and they lose people during the migration. Sometimes a third of the team. Sometimes more.

Belarus-specific things that affect the choice

Generic global EOR/PEO comparison articles don’t address these. They matter.

Currency and payment mechanics. Salaries in Belarus are paid in Belarusian rubles (BYN). Your payments to providers are typically in USD or EUR. The provider handles the conversion — but the conversion mechanics, the rate used, and any FX margin matter for your effective cost. Worth asking explicitly when you’re comparing provider quotes. Two providers with identical headline prices can deliver materially different effective costs once FX is in the picture.

Banking and sanctions context. Some Western banks decline correspondent transactions to Belarusian counterparties categorically, regardless of the underlying transaction’s compliance status. Before you sign a long-term provider contract, verify with your own bank that they’ll process the relevant transactions. This affects all three models equally — it’s not specific to EOR or PEO or outstaffing. It’s about the banking pipe between your country and Belarus working at all.

Contract language. Belarusian employment contracts must be in Russian or Belarusian. You don’t need to read or sign these — they’re between the provider and the engineer — but it’s worth understanding that the underlying employment instruments are in a different language than your services contract with the provider. If a dispute later involves the underlying employment contract, you’ll need translation.

Post-2022 enforcement-suspension exposure. If you’re from an “unfriendly” state (per Belarus’s classification, which includes EU member states, the UK, US, Canada, Switzerland, Australia, and a few others), enforcement of foreign judgments or arbitral awards may be suspended on the Belarusian side in the event of a dispute. This affects how you should think about provider selection and contract drafting — particularly the dispute resolution clause. Ask any provider whether their template contracts have been reviewed in light of the post-April 2022 regime. If the answer is a blank stare, that tells you something.

Five questions that usually settle the choice

Run through these in order. The first one with a clean answer is usually the answer.

1. How many people are you hiring in Belarus, and over what timeframe? Under 15 with no entity plans → EOR. 15+ long-term → entity plus PEO, or direct employment. Project-based with defined deliverables → outstaffing.

2. Do you need (or want) a Belarusian legal entity for any other reason? If yes → PEO with your entity, or direct employment. If no → EOR or outstaffing.

3. How fast do you need this person onboarded? Five to ten days → EOR or outstaffing. Three months is acceptable → entity setup is on the table.

4. How important is full legal separation from employer obligations? Critical → EOR. Comfortable with shared responsibility → PEO. Not relevant because the structure is a services contract → outstaffing.

5. How critical is retention of these specific engineers as long-term team members? Very critical → EOR is structurally better than outstaffing for retention, all else equal. Less critical → outstaffing’s flexibility may matter more than the retention edge.

These five questions cover roughly 90 percent of the decision space. The other 10 percent is edge cases and specific operational requirements, and that’s what scoping calls are for.

Frequently asked questions

We’ve been told “EOR and PEO are the same thing” by one provider. Are they?

No. They’re different legal structures with different liability allocations. EOR means the provider is the legal employer; PEO means there’s a co-employment arrangement where you (typically with your own entity) maintain some legal employer status. If a provider is telling you they’re the same thing, either they’re using the terms loosely or they’re calling their service one thing and operating it as another. Read the actual contract, not the marketing.

What’s the actual legal difference between outstaffing and EOR in Belarus, given that the engineer is in both cases employed by a third party?

The relationship between you and the engineer differs. Under EOR, your relationship with the engineer is structured as employment-adjacent — you direct their work, you’re named in the contract as the entity they work for in practice, and the EOR provider’s role is explicitly that of legal employer-on-behalf. Under outstaffing, your relationship with the engineer is structured as a services contract — the provider is selling you the engineer’s services, not their employment. In day-to-day operation these can look identical. They diverge most when something goes wrong: termination, IP disputes, changes in scope, or migration to direct employment later.

Can we hire an engineer through EOR and later migrate them to direct employment if we set up an entity?

Yes, and this is one of the most common migration paths. It typically takes 4–8 weeks once your entity is operational. The engineer’s employment contract transfers from the EOR provider to your new entity, ideally with continuity of accrued vacation, benefits, and seniority. The cleanest migrations are the ones where you’ve discussed the future direct-employment scenario with the engineer at hire stage — so when it happens, it’s an expected step rather than a surprise.

How do EOR or outstaffing arrangements affect the engineer’s eligibility for HTP benefits?

It depends on whether the provider is itself an HTP resident. If yes — and most established Belarusian IT-focused providers are — the engineer benefits from HTP-resident employment, which means reduced employer-side statutory burden and reduced individual income tax. If the provider isn’t an HTP resident, the engineer is on standard tax treatment. Worth confirming with any provider before you sign.

We’re using outstaffing now and one of our engineers wants to be a “real employee.” What are the options?

Three real options. Migrate them to EOR — they remain employed in Belarus by a provider, but the structure is closer to direct employment in feel and contract. Set up your own entity in Belarus and hire them directly. Or, if relocation is on the table for both sides, hire them into your foreign entity and support a relocation. The right answer depends on what’s really driving their request — sometimes it’s about tax structure, sometimes it’s about benefits, sometimes it’s about feeling like a member of the company rather than a vendor. Ask. The conversation is informative.

Who owns the IP created by the engineer in each model?

You do, in all three models, if the contracts are drafted properly. The mechanism differs. Under EOR and outstaffing, IP ownership is typically allocated to you through the services or EOR contract with the provider, and the provider’s employment contract with the engineer assigns IP to the provider, who then assigns it to you. Under PEO with your own entity, IP is allocated through the engineer’s direct employment contract with your entity. The contract has to actually do this work — IP doesn’t flow to you automatically because you’re paying invoices. Read the IP clause carefully, in every model.

What happens to our engineers if we want to wind down our Belarus operation?

Under EOR or outstaffing: you give the provider notice per the contract. The provider then handles the engineer’s termination per Belarusian labour law (which has notice periods and severance obligations the provider absorbs). Your direct exposure is the contract notice and any agreed-upon termination fees. Under PEO with your own entity: termination is your responsibility as the legal employer, with all that entails under Belarusian labour law — which can be more involved than what you’d find in some Western jurisdictions. This difference matters at exit time, even if it doesn’t look material at hire time.

Can we use one provider for EOR and a different provider for outstaffing within the same team?

Yes, and we see this occasionally for hybrid teams — some long-term core engineers on EOR, some project-specific contractors on outstaffing. It’s administratively heavier (two providers, two invoice streams, two sets of contracts) but it’s entirely legal. We’d caution that running two providers is more complexity than most foreign clients need, and consolidating onto one provider that handles both models is usually simpler. But sometimes the team genuinely splits along these lines and the dual-provider setup is the right call.

How are termination and severance handled differently across the three models?

Under EOR, the provider is the legal employer and absorbs the labour-law termination process — notice periods, severance, statutory protections. Your exposure is limited to your contract with the provider. Under PEO with your own entity, termination runs through your entity, and Belarusian labour-law termination obligations sit with you. Under outstaffing, the engineer’s termination is handled by the provider, and your exposure is the services-contract notice. The cleanest from a foreign-client risk perspective is EOR; the most exposing is PEO with your own entity. Worth knowing up front, not at termination time.

Where this leaves you

These three models look similar from outside but operate differently under Belarusian law. EOR is the right starting point for most foreign companies hiring 1–15 engineers in Belarus. PEO fits when you’ve already committed to a local entity. Outstaffing fits when the engineering work is project-shaped rather than team-shaped. None of them is universally “best.” The right answer depends on headcount, timeframe, retention priorities, entity strategy, and a few other things that take a 30-minute scoping call to surface properly.

The migration question is the one most foreign companies don’t think about until they’re already inside their initial choice. Building in a clean migration path from day one — through the contract, through the engineer relationship, through the documentation — is what separates a setup that ages well from one that becomes a lock-in. If your initial provider can’t articulate how you’d migrate out of their service when the time comes, that itself is information.We handle all three models, and we migrate clients between them when the situation changes. The conversation usually starts with “we don’t know which model fits.” The first call clarifies which one actually does — sometimes it matches what the client expected, sometimes it doesn’t. Get in touch if you want to have that conversation. We’ll start from your situation and work backwards to which model fits, instead of starting from the model and trying to fit you into it.