{"id":5944,"date":"2026-09-01T19:44:43","date_gmt":"2026-09-01T16:44:43","guid":{"rendered":"https:\/\/eor.by\/?p=5944"},"modified":"2026-09-07T18:03:26","modified_gmt":"2026-09-07T15:03:26","slug":"non-compete-belarus-what-actually-works","status":"publish","type":"post","link":"https:\/\/eor.by\/ru\/non-compete-belarus-what-actually-works\/","title":{"rendered":"\u0421\u043e\u0433\u043b\u0430\u0448\u0435\u043d\u0438\u0435 \u043e \u043d\u0435\u043a\u043e\u043d\u043a\u0443\u0440\u0435\u043d\u0446\u0438\u0438 \u0432 \u0411\u0435\u043b\u0430\u0440\u0443\u0441\u0438: \u0447\u0442\u043e \u0438\u043d\u043e\u0441\u0442\u0440\u0430\u043d\u043d\u044b\u0439 \u0440\u0430\u0431\u043e\u0442\u043e\u0434\u0430\u0442\u0435\u043b\u044c \u0434\u0435\u0439\u0441\u0442\u0432\u0438\u0442\u0435\u043b\u044c\u043d\u043e \u043c\u043e\u0436\u0435\u0442 \u043f\u0440\u0438\u043c\u0435\u043d\u0438\u0442\u044c, \u043f\u043e\u043c\u0438\u043c\u043e NDA"},"content":{"rendered":"\n

Here\u2019s the phone call. A senior engineer on your Belarusian team has just handed in notice \u2014 and next Monday they start at your closest competitor. You pull up the employment contract. There it is: a two-year non-compete, signed on the first day. You forward it to your lawyer. Your lawyer sighs.<\/p>\n\n

This piece is about what that sigh means, and what to do about it. The honest answer is more useful than the reassuring one: the standard Western-style non-compete you pasted into your Belarusian contract almost certainly won\u2019t hold up. But that isn\u2019t the end of the story \u2014 it\u2019s the beginning of it. You actually have more tools than you think. They\u2019re just not the ones you were reaching for.<\/p>\n\n

The general rule: outside the High-Tech Park, non-competes barely work<\/strong><\/h2>\n\n

Start with the honest headline. In most of Belarus, a post-employment non-compete clause is close to unenforceable. This isn\u2019t a technicality \u2014 it\u2019s a constitutional principle. The Belarusian Constitution guarantees the right to work, the Labor Code doesn\u2019t provide a framework for employer-imposed post-employment restrictions, and courts have historically been reluctant to bar a former employee from earning a living in their profession.<\/p>\n\n

That doesn\u2019t make the clause illegal to include \u2014 it just makes it inert. Third-party HR guides put it bluntly<\/a>: outside the Hi-Tech Park regime, non-compete agreements are legally unenforceable in Belarus. Where courts do consider such restrictions, they weigh them strictly against factors like duration, geographic and functional scope, compensation, and whether they unduly restrict the employee\u2019s right to work \u2014 and most standard Western drafts fail at least one of those tests.<\/p>\n\n

The trap to watch for: many foreign employers assume that because the pen touched paper, the restriction is real. It isn\u2019t. If your protection strategy rests entirely on the words «non-compete» in a signed contract, you\u2019re protected on paper and exposed in reality. The good news is that the actual protection you need is available \u2014 just built differently.<\/p>\n\n

The Hi-Tech Park exception: where non-competes actually work<\/strong><\/h2>\n\n

Residents of the High-Tech Park regime<\/a> operate under a different set of rules \u2014 introduced under Presidential Decree No. 8 in 2017 \u2014 which unlocks a legal toolkit that isn\u2019t available to employers elsewhere in the country. This includes proper post-employment non-compete agreements, non-poaching agreements between employers, and a range of corporate instruments familiar to any founder who has raised money in London or Delaware.<\/p>\n\n

The specifics on non-competes matter, because they\u2019re what turns the clause from theatre into a real restriction. Inside the HTP, a non-compete is enforceable for up to one year after employment ends<\/a>, and the employer must pay the former employee compensation for each month of compliance \u2014 at a minimum, one-third of that employee\u2019s average monthly salary from their final year of work. Skip the compensation and the clause reverts to decorative. Get the compensation right, and you have a restriction that Belarusian courts will actually enforce.<\/p>\n\n

This changes the calculus of HTP residency in an interesting way. The tax benefits are the headline reason companies structure through the Park, but the enforcement toolkit is a quieter, and for some businesses more valuable, second reason. If you\u2019re protecting genuinely differentiated IP or client relationships, the difference between «we can enforce» and «we can\u2019t» is worth more than a few percentage points on the corporate tax rate.<\/p>\n\n

\"\"<\/figure>\n\n

What actually works \u2014 inside and outside HTP<\/strong><\/h2>\n\n

Here\u2019s where most articles on this topic stop. Ours doesn\u2019t, because the more useful question isn\u2019t «does the non-compete work?» but «what does?» The answer, in Belarus, is a stack of complementary tools, most of which are enforceable regardless of HTP status.<\/p>\n\n

Confidentiality and NDA obligations<\/strong><\/h3>\n\n

The workhorse of any protection stack. Confidentiality clauses are generally enforceable in Belarus<\/a>, provided the scope of protected information and the duration of the obligation (during and after employment) are clearly defined. A well-drafted NDA is a stronger practical protection than a shaky non-compete: it doesn\u2019t stop the person moving to a competitor, but it puts a defined leash on what they can take with them.<\/p>\n\n

The commercial-secret regime<\/strong><\/h3>\n\n

Sitting alongside general confidentiality is a separate statutory regime for commercial secrets \u2014 information the employer has formally designated as such and protected through restricted access and documented handling. This is often a stronger basis for legal action than an NDA alone, because it comes with its own cause of action and remedies. The practical requirement: you have to have actually treated the information as a secret, not just called it one in a contract.<\/p>\n\n

IP assignment<\/strong><\/h3>\n\n

The default rule catches out most foreign employers: without explicit contractual assignment, code an employee writes belongs to the employee, not to you. This is such a common trap that it\u2019s worth its own article \u2014 which is exactly what our piece on IP ownership in Belarus<\/a> covers in detail. For the purposes of the protection stack, treat proper IP assignment as the non-negotiable baseline every other layer sits on top of.<\/p>\n\n

Duty of loyalty during employment<\/strong><\/h3>\n\n

A quieter but useful protection: while employed, a worker has a duty of loyalty to their employer that operates by default under Belarusian law. They can\u2019t simultaneously work for a direct competitor, and they can\u2019t use their position to divert business or opportunities to themselves. This doesn\u2019t restrict them after they leave \u2014 but it does mean that «moonlighting» or preparing to compete while still on the payroll is a live cause of action.<\/p>\n\n

Non-solicitation of clients<\/strong><\/h3>\n\n

Different from a full non-compete, and treated differently by courts. A well-drafted clause preventing a departing employee from actively soliciting your customers for a defined period sits on firmer ground than a blanket bar on working in the industry \u2014 because it protects a specific business relationship rather than restricting the employee\u2019s trade generally. Precision in drafting matters: define «client,» define «solicit,» keep the duration reasonable.<\/p>\n\n

Non-poaching of colleagues<\/strong><\/h3>\n\n

Outside HTP, weak. Inside HTP, expressly available. If your concern is a departing team lead who might take three of their reports with them, this is a real HTP-only advantage worth structuring for.<\/p>\n\n

Contractual penalties for breach<\/strong><\/h3>\n\n

Belarusian contracts can include a penalty (liquidated damages) for breach of the protective provisions. This is often more practical than proving actual damages in an IP or trade-secret case, which is notoriously hard. The catch: penalties have to be proportionate to the breach. As is standard across many European jurisdictions<\/a>, a court will reduce a disproportionate penalty. Design them as recovery mechanisms, not punishment.<\/p>\n\n

The reference table<\/strong><\/h2>\n\n

If you remember anything from this article, make it this table. It’s a quick overview of the entire toolbox.<\/p>\n\n

Post-employment non-compete<\/td>Effectively unenforceable<\/td>Yes, up to 1 year<\/td>Explicit compensation \u2014 at least a third of monthly salary, per month of restriction<\/td><\/tr>
Non-solicitation of employees (non-poaching)<\/td>Weak; treated with scepticism<\/td>Yes, expressly permitted<\/td>Clear scope, defined period, and mutual agreement between employers where applicable<\/td><\/tr>
Non-solicitation of clients<\/td>Partial \u2014 courts more open than for full non-compete<\/td>Same<\/td>Precise definition of «client,» reasonable duration, no blanket bar on the employee\u2019s trade<\/td><\/tr>
Confidentiality \/ NDA<\/td>Yes \u2014 works well<\/td>Yes<\/td>Defined scope of confidential information, clear post-employment duration, protected commercial-secret regime where applicable<\/td><\/tr>
Commercial-secret protection<\/td>Yes \u2014 statutory regime<\/td>Yes<\/td>Formal designation of information as commercial secret, restricted access, documented handling<\/td><\/tr>
IP assignment<\/td>Yes \u2014 with explicit clauses<\/td>Yes<\/td>Explicit written assignment; without it, the code stays with the author<\/td><\/tr>
Duty of loyalty during employment<\/td>Yes \u2014 default rule<\/td>Yes<\/td>Applies by operation of law; explicit contract wording strengthens the case<\/td><\/tr>
Contractual penalty for breach<\/td>Possible if reasonable<\/td>Yes<\/td>Amount proportionate to the breach; disproportionate penalties will be reduced by the court<\/td><\/tr><\/tbody><\/table><\/figure>\n\n

«Enforceability» is a working shorthand. Every clause depends on precise drafting and the specific facts of the case; the notes in the last column are the minimum conditions for a serious chance of enforcement, not a guarantee.<\/em><\/p>\n\n

The layered strategy that actually protects your business<\/strong><\/h2>\n\n

Any one of these tools taken on its own leaves gaps. Stacked together, they close most of the real-world scenarios that keep founders up at night \u2014 an engineer walking to a competitor with your codebase in their head, a salesperson taking their client relationships with them, a technical lead leaving with half the team in tow.<\/p>\n\n

The protection stack \u2014 what to actually build into your contracts<\/strong><\/p>\n\n