If you’re looking at Belarus as a place to build a tech operation, the High-Tech Park (HTP) regime is almost certainly part of the conversation. The tax benefits — 0% profit tax, 0% VAT on qualifying activity, a capped FSZN base — are the headline. But before any of that math runs, there’s a question that decides everything: does your business actually qualify?
HTP is a defined legal regime with a specific list of approved activities, structural requirements that must not go beyond what you do, and a Supervisory Board that approves or rejects applications. Companies whose business plans don’t clearly map to the list get turned down regularly, and rebuilding after a rejection is expensive.
This post walks through what qualifies, what doesn’t, and how to assess your own fit before you commit to the process.
The Belarus High-Tech Park is a special legal regime — not a physical location, despite the name. Companies that become residents conduct their operations from anywhere in Belarus while benefiting from HTP’s tax framework and regulatory advantages. The regime is administered by an HTP administration with a supervisory board that reviews applications and ongoing compliance.
It was created by Presidential Decree No. 12 in 2005 and expanded materially by Decree No. 8 in 2017, which broadened the activity catalog and introduced specific legal infrastructure for blockchain and cryptocurrency operations.
Resident companies access:
In exchange, residents pay 1% of revenue quarterly to the HTP administration as an administrative contribution, undergo annual audits, and remain bound to the activity catalog throughout residency. The benefits are substantial. Detailed mechanics around accounting and ongoing compliance for HTP companies are covered separately; this post is about whether your business qualifies in the first place.
The HTP regulatory framework defines a specific list of activities residents can perform. The list has expanded over the years and currently covers more than 40 categories, but they group into recognizable families.
The complete and current list is maintained by the HTP administration. The categories below summarize the major families with concrete examples of what typically fits.
Software development. Custom software, SaaS products, mobile applications, computer games, embedded software, firmware. This is the largest single category by resident count and the cleanest fit for most foreign-founded companies entering Belarus.
System integration and IT services. Implementation, technical support, maintenance, and training in connection with software the resident develops or licenses. Note that pure consulting unconnected to software development typically doesn’t qualify here.
R&D in IT and high-tech fields. Fundamental and applied research, experimental development in natural and technical sciences, computer modeling, robotics. R&D companies without a clear commercialization path face more scrutiny than those with defined deliverables.
Cybersecurity. Security audits, penetration testing, security software products, incident response infrastructure. Both product and service models qualify if the security work is the core activity.
Data processing, hosting, and cloud services. Data centers, infrastructure-as-a-service, platform-as-a-service, certain forms of edge computing.
AI and machine learning. Training and deploying models, building inference infrastructure, AI-driven products. Increasingly common as a primary or secondary activity for new residents.
Blockchain, distributed ledger, and cryptocurrency operations. Belarus was an early mover on the legal framework here, and HTP has specific provisions for cryptocurrency exchanges, mining operations, token sales, and custody services. Detailed rules apply, but the core activities are within scope.
Internet of Things. Both hardware-software integration projects and pure software platforms for IoT applications.
Education technology. Online learning platforms, edtech products, training infrastructure.
Medical IT and biotech adjacencies. Software for medical devices, healthcare data systems, certain biotech R&D activities. The biotech component needs specific framing because pure pharmaceuticals research is treated differently.
Aerospace, defense, and industrial control. Within constraints around dual-use technology and export control.
Marketing technology, AR/VR, and similar. AdTech platforms, augmented and virtual reality products, related technical infrastructure.
Other categories introduced over recent years include unmanned aerial vehicles, financial technology (fintech with a clear technology core), and a number of adjacencies that get added periodically as the framework evolves. The official HTP framework documentation covers the full enumeration.
What doesn’t qualify. The honest version of this conversation requires the negative space:
The pattern in these exclusions: HTP qualifies businesses where the technology is the product, not where technology supports a non-tech operation. Founders sometimes realize during this exercise that what they actually run is a professional services firm with software tooling — not an HTP candidate. That’s a useful realization to have before the application, not after.
Qualifying activity is necessary but not sufficient. The supervisory board evaluates several other dimensions.
The business project document. Applicants submit a detailed business project — essentially a structured business plan with HTP-specific sections. It covers planned activities, target markets, revenue projections, workforce plans, technology components, and competitive positioning. Generic or template-style projects get rejected; specific, defensible, well-documented projects get approved. Foreign founders often underestimate this document. It’s the heaviest single lift in the application and the most common point of failure.
Ownership and corporate structure. The applicant must be a Belarusian legal entity properly incorporated before applying. Foreign ownership is fully permitted and common; many HTP residents are wholly owned by US, UK, EU, UAE, or CIS holdings. Non-Belarusian individuals can be founders. There’s no minimum local ownership requirement. What matters is that the entity is properly constituted and the ownership structure is transparent in the application.
Financial substance. The supervisory board doesn’t approve shells. Strong applications show real planned activity: defined headcount expectations, credible revenue forecasts, identifiable target markets. A company with zero employees and a “we’ll figure it out after approval” plan faces tougher review than one with engineers already on payroll. Building credible headcount before the application strengthens the case materially — and gives the project document something concrete to point to.
Reputation and compliance history. Founders with prior failed Belarusian entities, unresolved tax disputes, or significant regulatory issues face additional scrutiny. International founders are not automatically disqualified by foreign jurisdictions, but anything material in the public record should be addressed in the application rather than left for the board to discover.
Activity mapping. The business project must explicitly map the planned activities to specific catalog categories. A project that vaguely describes “SaaS development” makes the reviewer’s job harder than one that cites the specific catalog entry and explains why the planned work fits. Strong applications make the reviewer’s job easy; weak ones rely on the reviewer to infer the fit.
These structural requirements explain why approval rates vary so widely. Companies that prepare seriously have high approval rates. Companies that treat the application as paperwork get rejected at much higher rates and often don’t understand why.
The full path from decision to residency typically runs 3–6 months. The major steps:
The Ministry of Economy’s HTP framework sets the regulatory boundaries; the HTP administration handles the operational review and supervisory board decisions.
Foreign owners often underestimate two things. First, a business project is a serious document. Professional preparation, not mere template filling, directly impacts the likelihood of approval. Second, timing matters more than it seems. If an investor requires residency status as a condition for closing a deal or if a contract with a client requires an appropriate tax structure, the submission deadlines should be built into the transaction schedule from the outset. Submitting an application after deadline pressure arises jeopardizes the entire structure.
For most foreign founders, the practical path is to engage a provider experienced with HTP applications early, scope the application with them, and run preparation in parallel with other entity-setup activities.
HTP is a powerful tool for the right company and an expensive distraction for the wrong one. Cases where the answer is “no” even if technically eligible:
Very small operations — under 3–5 employees with modest revenue. Compliance overhead can exceed tax savings. An EOR arrangement without a Belarusian entity is often cleaner at this stage.
Mixed-activity businesses — where non-qualifying activity is a meaningful share of operations. The segregation rules add complexity that may not pay off.
Companies needing pivot flexibility — HTP residents are bound to the catalog. Material pivots outside the catalog require de-residency or restructuring.
Pre-revenue startups with no near-term profit — the 0% profit tax matters when there’s profit. Pre-revenue companies get less from HTP than they expect; the burden of compliance overhead can outweigh the benefit during the early stage.
Companies whose tax bill would be modest regardless — looking at Belarus tax rates in regional context shows that even non-HTP positions in Belarus aren’t punishing; the HTP delta matters most for profitable scaleups.
The takeaway: HTP is a serious tool for the right company, not a default play for any tech business in Belarus.
Yes. Foreign ownership — including 100% foreign ownership — is fully permitted. Many HTP residents are wholly owned by US, UK, EU, UAE, or CIS parent companies. The entity itself must be a Belarusian legal entity, but its ownership can be anywhere.
Pure consulting unconnected to software products, traditional outsourced services unrelated to high-tech innovation, retail and e-commerce primarily reselling rather than platform-building, marketing agencies without proprietary technology, financial services without a fintech core, and most “tech-enabled” service businesses where technology supports a non-tech operation.
Three to six months end-to-end, including incorporation if needed. The supervisory board review itself typically runs 4–8 weeks after submission; preparing the business project is usually the longest single step.
It depends on commitment level and team size. Below 3–5 employees, an EOR usually makes more sense; above that, the HTP entity pays back faster. The structural difference between PEO and EOR arrangements is also relevant if you’re choosing between operating models — PEO assumes you already have a Belarusian entity (HTP-resident or otherwise), while EOR works without one.
Existing companies can apply, provided their planned activities map to the HTP catalog and their financial and reputational history supports approval. Some existing companies need to restructure or refocus before applying; others can transition directly.
HTP residents must operate within their approved catalog scope. If activities expand into a new catalog category, the residency can be amended through a supplementary application. If activities move outside the catalog entirely, residency may need to be relinquished or the business restructured.
The cap applies to FSZN contributions made by the HTP-resident employer for its employees, provided the employee consents in writing to the cap base being used for their calculations. Detailed mechanics of IT payroll taxation in Belarus cover the practical application, including bonus timing and edge cases that affect the math.
Yes. Holding structures with US, UK, Cypriot, Dutch, UAE, or other parent entities are common. The Belarusian entity is the HTP resident; the parent structure sits above. There’s no requirement for a specific holding jurisdiction.
At minimum: company overview, planned activities with specific catalog mapping, target markets, projected revenue and expense forecasts over a multi-year horizon, planned workforce and structure, technology approach, and competitive positioning. Strong projects also include risk analysis, milestones, and clear measurable goals tied to the planned activities.
Belarus’s HTP is among the most established and broadest in scope across the post-Soviet region. Regional tax and IT-employer comparisons show how Belarusian IT taxation interacts with neighboring frameworks. Each regime has its own emphasis; HTP’s particular strengths are the breadth of activity catalog, the depth of legal infrastructure for blockchain operations, and the maturity of supporting professional services.
Before investing time and money in joining the HTP, the most effective step is a 30-minute consultation with a company experienced in assisting with HTP accession, preparing all the necessary documentation, and navigating the entire process. Submit a brief description of your business model and target activities, and you’ll receive a quick response. No obligations required.
Dear Clients! We are pleased to announce the completion of a recruiting project (3 QA) for a German IT company with an office in Belarus. Due to the existence of a confidentiality agreement, we cannot write the name of the brand under which our Client operates. However, as before, we can tell some details of […]
The conversation usually starts the same way. A senior engineer asks for a one-on-one, closes the door, and says they’ve been talking to another company. Sometimes there’s a written offer attached. Sometimes there isn’t. Either way, the next forty-eight hours will decide whether you keep one of the people your team can’t easily replace — […]
Most international groups that own a Belarusian subsidiary aren’t physically in Minsk. The headquarters sits in London, New York, Dubai, Singapore, or Berlin. The CFO checks in over Slack, the board reviews quarterly numbers in a dashboard, and the only people on the ground are the engineering team, an accountant, and whichever statutory officers the […]
