Building a website for your e-Residency company. What an Estonian OÜ owner needs to know — 2026 guide

Why the website matters more for an e-Residency company

An e-Residency website is the public face of a company that has no office, no shopfront and often no employee in the country where it is registered. For an Estonian OÜ run from abroad, the site is simultaneously your sales page, your compliance document and the evidence a bank, a payment provider or a first customer uses to decide whether you are a real business.

The scale of this cohort is easy to underestimate. Estonia’s e-Residency programme has passed 142,000 e-residents and 43,000+ Estonian companies founded by them (official programme dashboard, 2026). In 2025 alone e-residents registered 5,556 new companies — 15% above the previous record — and 13,828 people joined the programme, a 20% year-on-year jump. The direct fiscal effect of the programme in 2025 was €124.9 million.

Which also means competition. Tens of thousands of consultancies, agencies, SaaS products and freelance studios share the same Estonian registry code format and the same “remote-first EU company” story. What separates them, in a customer’s eyes and in a compliance officer’s, is almost always the website.

The rest of this guide covers the parts that are specific to an Estonian company — the ones a global website builder will never mention and a purely local Estonian agency rarely thinks about, because their clients live here. If you want the broader picture of scope, process and technology first, start at our website development page and come back.

The domain: .ee, .com, or both

The first question almost every new e-resident asks is whether they are even allowed to have a .ee domain. They are.

The .ee zone is administered by the Estonian Internet Foundation and is open to individuals and legal entities from any country — Estonian residency is not a condition. Registration always goes through an accredited registrar, never through the foundation directly. Three practical points that trip people up:

• The application must be signed. An Estonian ID card or Mobile-ID works — and your e-Residency digital ID is exactly that. This is one of the moments the card genuinely saves you a courier and a scanner.
• Every domain needs an administrative and a technical contact. The administrative contact is a natural person: either someone with the right of representation of the company (you, as board member) or someone authorised in writing. The technical contact is usually your hosting provider or developer.
• Only Estonian-alphabet characters are allowed, plus digits and hyphens — no accents from outside that set. The Estonian ones (õ, ä, ö, ü, š, ž) are permitted and cost the same as plain domains — worth registering defensively if your brand contains them.

Whether you should use .ee is a different question, and the honest answer depends entirely on your customers. Search engines use the searcher’s location as one ranking signal, so a .ee address gets a small structural advantage for searches made from Estonia. If you sell to Estonian businesses or consumers, that matters. If your customers are in Germany, the UK or the US — which describes the majority of e-Residency companies — a .com or a strong brandable domain communicates far better, and a .ee bought defensively and redirected to it costs almost nothing.

What you should not do is build your entire brand on a free subdomain from a website builder. It reads as temporary to customers and, as the next section explains, to compliance teams.

Hosting and speed: why the EU is the sane default

No Estonian law obliges you to host inside Estonia. GDPR does care where personal data goes, and keeping servers and backups inside the EU removes an entire category of transfer paperwork — the simplest form of compliance is the one you never have to document.

The more immediate argument is physics. If your buyers are in Europe, every request to a US server crosses an ocean twice. A server in Tallinn, Helsinki or Frankfurt typically cuts hundreds of milliseconds off the first response, and page speed feeds directly into Core Web Vitals, search rankings and conversion rate. For a company whose entire storefront is a website, that is not a technical detail.

Practical guidance for an Estonian OÜ:

• Pick an EU region — Tallinn or Helsinki if your market is the Baltics and Nordics, Frankfurt or Amsterdam for pan-European reach.
• Get an invoice with your company name and registry code on it. Hosting paid from a personal card, invoiced to a private person, is an accounting annoyance you will rediscover every quarter.
• Use a CDN if you sell globally, but keep the origin in the EU so the data-protection story stays simple.
• Check the data processing agreement. Any serious EU host publishes one; if you cannot find it, that tells you something.

The website and bank onboarding: the part nobody warns you about

No Estonian law says a company must have a website to open a bank account. But every bank and fintech that serves Estonian companies — LHV, Swedbank, Wise, Paysera and the rest — runs a “know your business” check before approving an account, and for a company operated from abroad the website is the single most convenient piece of evidence they have.

This is the most common unpleasant surprise for new e-residents. The company is registered in a day, and then the account application stalls in additional questions for weeks. Compliance is trying to answer a short list of questions, and a good site answers all of them before they are asked:

1. What exactly do you sell? A concrete description of services or products, not “we deliver digital solutions for modern business”. Vagueness reads as a red flag, because shell companies are vague.
2. Who are the customers and where are they? Named markets, industries or client types. This maps directly onto the risk profile the bank is building.
3. Is the legal entity on the site the same one on the application? The registered name, the registry code and the address in the footer must match the commercial register exactly. A mismatch turns a five-minute check into a case.
4. Is there a real way to reach you? A working email on your own domain — [email protected] rather than a Gmail address on a site that already has a domain of its own — plus a contact form and, ideally, a phone number.
5. Does the business have any connection to Estonia or the EU? Not a legal requirement, but Estonian banks in particular weigh it. If you have EU customers, EU suppliers or an Estonian accountant, saying so on the site does no harm.

The practical consequence: build the website before you apply, not after. A finished five-page site with real content is worth more in an onboarding review than a beautiful unfinished one, and far more than a “coming soon” page. It also works in the other direction — payment providers, marketplaces and larger B2B clients run their own version of the same check.

What Estonian and EU law actually require on the page

The mandatory part is short, and skipping it is the easiest own goal in the whole project. Under Estonian and EU e-commerce rules, a business offering services online must make its identity easy to find:

• Registered company name, exactly as in the commercial register (e.g. “Näide OÜ”).
• Commercial register code — the eight-digit registry number.
• Registered address in Estonia, including your service-provider or virtual office address if that is your legal seat.
• A working email address and a practical contact route.
• VAT number, if the company is VAT-registered.

The footer plus a contact page is the conventional home for all of it, and it doubles as the compliance evidence from the previous section.

VAT, OSS and what belongs on the site

Estonia’s standard VAT rate is 24% (raised from 22% on 1 July 2025). Registration becomes obligatory once taxable turnover passes €40,000 in a calendar year, and you can register voluntarily below that. If you sell digital services or goods to consumers in other EU countries, the €10,000 cross-border threshold pulls you into the destination country’s VAT rate — and the OSS scheme lets you declare all of it through a single Estonian filing instead of registering in each member state.

What this means for the website is simple but frequently botched: if you sell to consumers, prices must be shown including VAT, and the applicable rate depends on the buyer’s country. A checkout that charges every EU consumer a flat Estonian 24% is quietly wrong. If you sell B2B inside the EU, build in VAT-number validation so the reverse-charge mechanism applies correctly. Publish your VAT number as soon as you have one — B2B buyers look for it.

GDPR, cookies and accessibility

Your Estonian company is an EU company, so GDPR applies in full regardless of where you personally live. The website-level obligations are modest: a genuine privacy policy naming the controller (your OÜ, with registry code), a cookie banner that actually blocks non-essential scripts until consent — analytics and ad pixels fire before consent on a surprising share of small sites — and a lawful basis for every form on the page.

One newer item worth knowing: the European Accessibility Act has applied since 28 June 2025 and covers e-commerce and consumer-facing digital services sold into the EU. Micro-enterprises providing services — under 10 staff and under €2 million turnover, which covers most e-Residency companies — are exempt from the service obligations, but the exemption is not permanent insurance. If you plan to grow, building to WCAG 2.1 AA from the start is far cheaper than retrofitting.

Accepting payments as an Estonian company

Your payment stack shapes the website, so decide it early rather than bolting it on. For an Estonian OÜ there are three realistic layers:

• Stripe — the default for international card payments and subscriptions. It supports Estonian companies, but with a catch e-residents hit constantly: eligibility follows the personal residency of the account owner, which must be in a Stripe-supported country. Your Estonian OÜ alone is not enough if you personally live outside that list.
• Montonio and Maksekeskus — the local layer. These provide Baltic bank links (Swedbank, SEB, LHV, Coop), Estonian pay-later options and, in Montonio’s case, parcel-machine shipping. If you sell to Estonian consumers, this is non-negotiable: locals expect a bank link, not a card form. Both work with Estonian legal entities, including e-Residency companies, provided there is genuine business activity and a SEPA account at an EU bank.
• Invoicing and SEPA — for B2B services, still the most common route, and the one with the lowest fees. Here the website’s job is simply to make the company details and VAT number effortless to find.

The frequent mistake is treating this as an either/or. A company selling into both Estonia and the wider EU usually needs a local gateway for bank links and Stripe for international cards. If your project is a shop rather than a service business, our step-by-step guide to starting an online store goes into the platform, shipping and VAT mechanics in far more depth, and e-commerce development covers how we build them.

Languages and being found — including by AI

Estonia has three commercially relevant languages, and the right answer is rarely “all of them”:

• English only — correct for the majority of e-Residency companies. If your customers are in Berlin, London or San Francisco, an Estonian version is decoration.
• English + Estonian — the moment you want Estonian B2B clients, public-sector work or local partners. Estonian buyers search in Estonian, and a machine-translated Estonian page is worse than none: it signals that nobody here actually stands behind the company.
• Add Russian if you sell to consumers in Estonia. Roughly a quarter of the country’s residents speak Russian as a first language and search in it.

Whatever you choose, implement it properly: separate indexable URLs per language (/, /en/, /ru/), hreflang tags linking the versions, and human translation of at least the pages that sell. A language switcher that dumps every visitor onto the homepage is a small thing that costs real traffic.

One more visibility channel now matters as much as Google for this audience. E-residents are unusually heavy users of AI assistants — a large share of “I have an Estonian company, where do I get X?” research now starts in ChatGPT or Perplexity rather than a search box. Being cited in those answers depends on a different set of levers: an answer-first page structure, concrete citable facts, schema markup, and AI crawlers not being blocked in your robots.txt. We unpack the whole method in our guide to generative engine optimization, and treat it as part of SEO services rather than a separate fashion.

Budget benchmarks and a launch checklist

Market benchmarks for 2026 — ranges you can sanity-check quotes against, not a price list:

• Self-built template site: a few hundred euros a year in subscriptions. Fine for validating an idea; visibly a template to anyone reviewing you.
• Freelancer or small studio, small business site: roughly €1,000–3,000. Usually a template refined to your brand, one language, basic SEO.
• Agency-built custom site: typically starting around €4,000–7,000 and rising with languages, integrations, page count and content production. This is where multilingual, fast, properly structured sites live.
• Running costs: .ee domain roughly €10–20 a year, EU hosting €5–30 a month, plus whatever your payment provider takes per transaction.

Two costs that are systematically underestimated: content — text, photos, case studies, in every language you launch — and maintenance. A site nobody has touched for two years actively damages trust, and for a remotely-run company trust is the entire product.

Choosing who builds it

A short version of a longer topic. Search for “web development estonia” and you will find three kinds of supplier: global marketplaces (cheap, no local context), Estonian agencies (local knowledge, higher rates) and independent freelancers (variable). For an e-Residency company the deciding factor is rarely price — it is whether the supplier has actually dealt with .ee registration, Estonian payment gateways, VAT display rules and multilingual setups before. Ask for two examples of Estonian company sites they have shipped, and ask who owns the domain and hosting accounts when the project ends. The answer should always be: you.

Launch checklist

1. Domain registered in the company’s name, not a contractor’s, with auto-renew on.
2. EU hosting, HTTPS everywhere, invoices issued to the OÜ.
3. Clear description of what you sell, to whom, in which markets.
4. Footer with registered name, registry code, address, email — matching the register exactly.
5. VAT number published once registered; consumer prices shown including VAT.
6. Privacy policy naming your OÜ as controller; cookie consent that genuinely blocks before consent.
7. Email on your own domain, plus a contact form that has been tested end to end.
8. Payment stack live and test-transacted — local gateway, Stripe, or both.
9. Languages decided, human-translated, with correct hreflang.
10. Analytics installed, Search Console verified, AI crawlers not blocked in robots.txt.
11. Core Web Vitals in the green on mobile, not just desktop.
12. An owner named for updates — content, prices and legal pages drift.

Work through that list and your Estonian company reads as what it is: a real business that happens to be run from somewhere else. If you would rather not assemble it yourself, iweb.ee has been building sites for Estonian companies — including plenty owned from abroad — from Tallinn since 2014.

This article is a general overview, not legal or tax advice: rules and thresholds change and your situation may differ. Check the current legislation, or ask your accountant, before acting on any of it.

FAQ — questions e-residents actually ask