Что такое договор о неконкуренции и непереманивании в Беларуси в 2026 году

Here’s a scenario we see often. A company offboards a senior engineer, who walks straight into a competitor with a head full of your roadmap. Legal pulls up the signed contract, points to the non-compete, and feels covered. Then local counsel reads it and explains that, as written, it does almost nothing.

That’s not a drafting mistake. In Belarus, whether a restrictive covenant is worth the paper it’s printed on comes down to one question most foreign employers never think to ask: is the employer a resident of the High-Tech Park? Answer that, and the rest of this article falls into place.

Let’s walk through what actually holds up, what doesn’t, and what to use instead.

First, four things people lump together

«Non-compete» gets used as shorthand for four separate instruments, and in Belarus they don’t share a fate. Keeping them apart is most of the work:

• Non-compete — the ex-employee can’t join or start a competitor for some period after leaving.
• Client non-solicitation — they can’t approach your customers.
• Employee non-solicitation (anti-poaching) — they can’t lure your staff away.
• Confidentiality / trade secrets — they can’t use or disclose your protected information.

These sit on very different legal footing. Treat them as one clause and you’ll over-rely on the weakest of the four.

The default rule: outside the Park, the non-compete barely bites

Belarus is a civil-law country, and its constitution protects freedom of labour — the right to earn a living in your chosen field. A clause that forbids someone from doing exactly that after they leave runs straight into that principle.

The practical result is that a standard post-employment non-compete is subject to strict limits and, for most employers, is very hard to enforce. This isn’t unique to Belarus; civil-law jurisdictions that constitutionally protect the right to work tend to treat these clauses the same way, as global surveys of restrictive covenants across markets consistently show.

Confidentiality and trade-secret obligations are a different story. Those are generally enforceable during and after employment, provided the protected information is clearly defined and the obligation is properly scoped. So the plain-English version of the default rule is this: your NDA travels to Belarus. Your non-compete mostly doesn’t.

The exception that changes everything: the High-Tech Park

In 2017, Belarus did something unusual. Decree No. 8 — the presidential decree that built the modern digital-economy regime — imported a set of English-law-style tools and made them available specifically to Park residents. Among them: a real, workable non-compete.

Here’s how it works inside the Park:

HTP non-compete, in short:

• Duration. Enforceable for up to one year after employment ends.
• You have to pay for it. The former employee is owed compensation of at least one-third of their average monthly salary, paid for each month they comply. No compensation, no enforceability.
• Anti-poaching is allowed. Residents can agree penalties for enticing staff away — the employee-non-solicitation tool the general regime lacks.
• Penalties have teeth. Contractual penalties can be set above the usual statutory ceilings, and courts are constrained from cutting them down unless they’re clearly excessive.

Global employment guides that track what’s enforceable market by market describe the same one-year cap and one-third-of-salary compensation for the Park — a useful sanity check, though not a substitute for local counsel.

One honest caveat worth flagging to your lawyer: this regime rests on a presidential decree, and there’s a genuine subtlety in Belarusian law about how decrees interact with statutes. It’s not a reason to distrust the regime — it’s a reason to have a Belarusian lawyer confirm the current mechanics against your specific contract rather than working from a checklist. More on that in the FAQ, and it’s exactly the kind of thing our HR and compliance consulting exists to catch before it becomes a problem.

Non-solicitation: two clauses, not one

Client non-solicitation and employee non-solicitation get written into the same paragraph all the time, and they shouldn’t be. They protect different things and they don’t stand on the same ground.

Employee non-solicitation — the anti-poaching agreement — has an express home inside the HTP regime, as above. Outside the Park it’s on much thinner ice, along with the non-compete.

Client non-solicitation is more situational everywhere. Its strength depends heavily on how it’s drafted, how narrowly it’s scoped, and how it interacts with your confidentiality terms. In practice, a tightly written confidentiality clause protecting your customer data often does more reliable work than a broad «don’t touch our clients» covenant — because the confidentiality obligation is the one that reliably holds up.

The quick reference

Same instruments, two columns — inside the Park and out. This is the one to keep:

Instrument	Outside HTP	Inside HTP
Post-employment non-compete	Effectively unenforceable	Up to 1 year, if you pay for it
Employee non-solicitation	Very limited	Expressly permitted
Client non-solicitation	Weak, situational	Stronger, drafting-dependent
Confidentiality / trade secrets	Generally enforceable	Generally enforceable
IP assignment	Enforceable	Enforceable
Non-compete compensation	n/a	≥ 1/3 avg monthly salary, per month
Max non-compete duration	n/a	1 year
Contractual penalties	Statutory limits apply	Can exceed limits; hard to reduce

What to actually rely on

If the headline clause mostly won’t hold, where does real protection come from? From the tools that survive regardless of Park status — the ones you build deliberately rather than paste in from a US template.

1. Airtight confidentiality and trade-secret terms. This is the workhorse. Define the protected information precisely and the obligation holds up during and after employment.
2. Clean IP assignment. Make sure everything the person creates belongs to you, unambiguously, from day one.
3. Notice periods and garden leave. Time on the bench is time not spent at a competitor, and it’s structured into the contract rather than fought over afterward.
4. Deferred compensation and vesting. Money that lands later gives people a voluntary reason to leave on good terms and keep their obligations.
5. The right employment vehicle. A covenant is only as good as the contract it lives in and the entity that can enforce it.

And where a genuine non-compete is warranted — a senior person with real competitive exposure — do it the way that works: inside the Park, with the compensation the regime requires, rather than relying on a clause that reads well and does nothing. If you don’t have a Belarusian entity, an Employer of Record is the cleanest way to put people on contracts that are actually built to hold — the EOR carries local-law compliance rather than leaving you to guess at it. For project-based needs, outstaffing can achieve the same thing without a permanent hire.

The part nobody puts in the intro

Even a valid HTP non-compete quietly assumes two things: that the person is still in Belarus, and that any dispute plays out there. Over the past few years, a large share of specialists relocated abroad. If your former employee is now in another country, you may be trying to enforce a Belarusian judgment against someone a court there can’t easily reach — often more trouble than it’s worth.

Which brings the whole thing back to a simple idea: protection you can enforce beats protection that only reads well. That usually means less energy on clause wording and more on how the employment is structured in the first place — the contract, the vehicle, the incentives, the IP. Get those right and the non-compete becomes a backstop, not your only line of defence.

FAQ

Are non-compete clauses enforceable in Belarus?

By default, no — not in a way most foreign employers expect. A post-employment non-compete that stops someone from working in their field collides with the constitutional right to work and is very hard to enforce. The major exception is the High-Tech Park, where a specific regime allows them.

What makes a non-compete valid inside the High-Tech Park?

Two things above all: a cap of one year, and compensation. The former employee must be paid at least one-third of their average monthly salary for each month they comply. Skip the payment and the clause isn’t enforceable, even inside the Park.

Do I have to pay someone during a non-compete?

Inside the HTP, yes — that’s the deal the regime is built on. Outside it, the question is mostly academic, because the non-compete itself won’t hold up regardless.

Is a non-solicitation clause enforceable in Belarus?

It depends which kind. Employee non-solicitation (anti-poaching) has an express basis inside the HTP. Client non-solicitation is more situational and drafting-dependent everywhere. In both cases, a strong confidentiality clause often does more reliable work.

Does my US or UK non-compete work if I hire in Belarus?

Assume it doesn’t, as written. A covenant drafted for a common-law jurisdiction doesn’t automatically translate. If you need real post-employment restrictions, they have to be built for the HTP regime — or replaced with protections that hold up regardless.

What protects me if the non-compete doesn’t?

Confidentiality and trade-secret terms, IP assignment, notice periods and garden leave, deferred compensation and vesting, and choosing an employment structure that can actually enforce what you sign. These carry most of the real weight.

Is this legal advice?

No. This is general information for planning purposes, written by a recruitment partner, not a law firm. Belarusian labour and HTP rules are specific and they change — confirm the current position with qualified local counsel before you draft or rely on any clause.

The bottom line

In Belarus, the clause you lean on at home does the least work, and the protections that hold up are the ones you put in place on purpose: confidentiality, IP, structure, and — where it’s truly needed — a proper HTP non-compete you’ve actually paid for. Getting that mix right before the contract goes out is far cheaper than discovering the gap after someone’s already walked. If you’re hiring here, that’s also where specialist IT recruitment in Belarus and the right employment setup earn their keep.

Tell us the role and the risk, and we’ll tell you what will actually hold up — and how to structure it — before you send the offer. Get in touch.