Who provides Drupal development in Estonia and how do you choose the right partner?
🎧 Listen to every article back to back
Estonia has several development partners with strong Drupal experience, but they are not directly interchangeable. Building a large new digital platform, maintaining an existing Drupal website and taking over a legacy project require different kinds of teams. The first step in choosing the right partner is to define the problem you actually need to solve.
Who provides Drupal development in Estonia?
Drupal development in Estonia is provided by both larger full-service software companies and smaller specialist teams. Based on public service pages, references, Drupal.org profiles and public procurement records from recent years, visible providers include ADM Interactive, Trinidad Wiseman, Web Expert, Krabu Grupp and Krabu Tech, Mearra, Limegrow, Revelan and WebPro.
This is not a ranking or an exhaustive list. A company name alone does not tell you whether it is the right fit for a particular Drupal project. One partner may be strong at analysis, design and development of a large new digital platform, while another focuses on maintaining an existing system, taking over legacy projects or working with complex integrations.
The first question should therefore not be “who is the best Drupal developer in Estonia?” but “what kind of Drupal partner does our situation require?”
Which Drupal companies are visible in Estonia?
ADM Interactive
ADM Interactive (opens in a new tab) is one of the larger Estonian development companies that communicates its Drupal specialisation particularly clearly. According to ADM, the company has more than 15 years of Drupal experience, has built more than 100 Drupal applications and has more than 20 specialists working with Drupal on a daily basis.
ADM also publishes concrete Drupal references and evidence of participation in the Drupal ecosystem. A 2026 case study about digiriik.eesti.ee, for example, describes the technical renewal of an older Drupal platform in cooperation with Estonia's Centre of Registers and Information Systems and the Ministry of Justice and Digital Affairs.
This type of profile matters when a project needs a larger team and a broader set of competencies in addition to Drupal development.
Trinidad Wiseman
Trinidad Wiseman (opens in a new tab), or TWN, has a dedicated Drupal service and public references including the Bank of Estonia's external website and ERGO Baltic's web solution.
In 2025, TWN wrote that developers in its Rakvere team specialising in Drupal had an average of 14 years of Drupal experience. Its Drupal offering covers websites, self-service environments, portals and custom solutions, while the wider company also has competencies in analysis, UX, UI, accessibility and software development.
TWN is therefore an example of a provider where Drupal capability forms part of a broader digital-service development organisation.
Web Expert
Web Expert (opens in a new tab) describes itself as a Drupal and Symfony expert and provides an end-to-end development process covering analysis, project management, development and support.
One of its strongest public Drupal references is the City of Tallinn website. According to Web Expert, Tallinn.ee was built on Drupal 9 and the project involved a large volume of information, multiple user groups, external integrations, data migration, maintenance and hosting. Its portfolio also includes other Drupal solutions for large organisations.
Web Expert, ADM, and the joint team of Krabu Grupp and Krabu Tech were also among the successful bidders in the Estonian Centre of Registers and Information Systems' 2024 procurement for Drupal website development and maintenance.
Krabu Grupp and Krabu Tech
Krabu does not highlight Drupal in its public marketing as prominently as ADM or TWN, but its public procurement track record provides a strong signal of Drupal capability.
In the Centre of Registers and Information Systems procurement “Drupal website development and maintenance”, the joint bid by Krabu Grupp and Krabu Tech was selected alongside Web Expert, ADM Interactive and the then Wisercat Estonia. The purpose of the procurement was to establish a framework agreement for Drupal development and maintenance.
Evidence like this is useful when evaluating a partner because it does not rely solely on the company's own marketing copy.
Mearra
Mearra (opens in a new tab), formerly known as Wunder, is an internationally oriented Drupal service provider whose Drupal.org profile lists an office in Estonia. Drupal.org identifies Mearra as a Drupal Certified Partner, with services including development, migration, integrations, audits, security reviews, performance optimisation, support and upgrades.
Its Estonian Drupal roots include Mekaia, which joined Wunder Group in 2016 and continued as Wunder Estonia. Mekaia's historical Drupal.org profile shows both module development and participation in Estonian Drupal translation work.
Mearra illustrates why partner evaluation should sometimes consider the Drupal capability of the wider international group, not only the local legal entity.
Limegrow
Limegrow (opens in a new tab) is a smaller development company whose public service description specifically highlights long-standing Drupal experience, development of content-heavy Drupal websites and long-term maintenance of Drupal and WordPress solutions.
Limegrow's portfolio (opens in a new tab) includes Elron, where the work is described as Drupal Development, WordPress migration and UX/UI. The company also provides CMS updates, technical support, security work and backups.
This is an important reminder that choosing a Drupal partner in Estonia is not limited to the largest software houses. A smaller team can be a suitable option when the need is long-term development and maintenance and its working model fits the organisation.
Revelan
Revelan (opens in a new tab) is a smaller Estonian development company whose public service material clearly lists Drupal among its technologies. The company highlights both Drupal development and upgrades of existing solutions, including a Drupal 7 to Drupal 10 migration.
Revelan is another example of a smaller specialist provider worth considering when the project does not require the multidisciplinary team of a large software house. As with any smaller partner, ask who will actually work on the project, how continuity is ensured and how maintenance and response times are organised.
WebPro
Compared with larger software houses, WebPro is a smaller Drupal-focused partner. Our focus is primarily on maintenance, continued development, upgrades and migrations, and taking over projects from another development partner.
That also means WebPro does not have to be the right choice for every Drupal project. If the goal is to build a very large digital service from scratch with a large analysis, design and development team, a larger full-service provider may be a better fit.
If an organisation already has a Drupal website that needs to be maintained, upgraded, fixed and developed for years, different qualities become more important: whether the partner is willing to take over someone else's code, can assess technical debt, applies security updates in a controlled way and can run the system in a test environment before making production changes.
WebPro's work is therefore centred on Drupal maintenance, upgrades, project takeovers, audits and continued development.
Large Drupal agency or smaller specialist?
Company size is not a quality metric in itself. It mainly affects the type of working model and range of competencies available within one provider.
A larger partner may make sense when a project simultaneously needs:
- business and systems analysis;
- service design and UX/UI;
- a large development team;
- several parallel workstreams;
- complex DevOps or cloud architecture;
- extensive testing and project management.
A smaller specialist Drupal partner may be a better fit when:
- the Drupal system already exists;
- you need regular maintenance and continued development;
- work arrives in smaller or medium-sized development packages;
- you want direct access to technical specialists;
- an existing project needs to be taken over from another provider;
- you need specific Drupal, PHP, Composer or integration expertise.
Do not choose based only on employee count. What matters more is whether the partner's normal way of working matches the actual state and needs of your project.
How can you check whether a company really knows Drupal?
The simplest approach is to ask for evidence that can be evaluated without relying on a sales presentation.
Look at Drupal projects from recent years
A Drupal 7 reference from ten years ago demonstrates historical experience, but it does not by itself prove current Drupal 10, 11 or 12 capability.
Ask which supported Drupal versions the company currently works with and which projects it has developed or upgraded in recent years.
Ask how development and deployment work
A professionally managed Drupal project should have a clear approach to Git, Composer, configuration management, development and testing environments, and backups.
Ask how changes move from development to production, how dependencies are managed and how rollback is handled when something goes wrong.
Check whether the partner can take over an existing system
Building a new project and taking over a Drupal system that has been developed for ten years are different skills.
For an existing project, the developer must be able to assess custom modules, Composer dependencies, configuration, the database, file handling, integrations, cron jobs, servers and deployment. If source code or documentation is incomplete, risks need to be mapped before new development begins.
In this situation, it makes sense to start with a Drupal project takeover and partner change assessment or a more detailed audit.
Discuss maintenance before development, not after it
A Drupal website is not finished when it goes live. Drupal Core, modules, PHP and other dependencies receive updates and security fixes.
Before choosing a partner, ask:
- who monitors security updates;
- where updates are tested;
- how backup and recovery work;
- who responds to a critical incident;
- how major version upgrades are planned;
- what happens to the project if the partnership ends.
If responsibility remains unclear, it will eventually become the client's problem.
What should you ask a Drupal development partner before signing a contract?
A good first meeting does not need to be a technical exam. Questions that reveal how the company actually works are enough.
- Which similar Drupal projects have you delivered in the last three years? Ask about the type of project, not only well-known client logos.
- Who will work on our project day to day? The sales team and the actual delivery team may be different.
- Do you take over Drupal projects built by other developers? This matters when the system already exists.
- How do you use Git, Composer and Drupal configuration management? The answer indicates whether development is repeatable and transferable.
- How do you test Core and module updates? Production should not be the first testing environment.
- How is maintenance organised after development? Ask about security updates, response times, backups and monitoring.
- How do you document custom solutions and integrations? This is especially important for APIs, SSO, ERP, CRM and other external systems.
- What happens if we want to change partners later? The domain, source code, Git repository, server, documentation and accounts should remain under the client's control.
Does a Drupal.org profile prove developer quality?
Drupal.org contribution is a useful signal, but it is not the only selection criterion.
Maintaining modules, contributing fixes to Core, receiving security advisory credits and maintaining long-term activity can demonstrate engagement with the Drupal ecosystem. At the same time, a highly capable client-project developer may do most work in private repositories and have little public Drupal.org activity.
Look at the combination: recent projects, team experience, technical working practices, maintenance capability and, where relevant, Drupal.org contribution.
Does winning a public procurement prove Drupal competence?
Public procurement can provide an independent signal, but it should not be treated as a universal quality badge.
For example, in the Estonian Centre of Registers and Information Systems' 2024 procurement for Drupal website development and maintenance, Web Expert, ADM Interactive, Krabu Grupp and Krabu Tech, and Wisercat Estonia were selected as successful bidders. The procurement aimed to establish a framework agreement for Drupal development and maintenance.
This shows that those companies met the requirements of that particular procurement. It does not automatically determine which one is the best fit for your project, because your requirements, workload and collaboration model may be different.
Should you choose a partner based on hourly rate?
Choosing a Drupal partner solely by hourly rate is rarely useful.
A lower hourly rate can result in a lower total cost when the work is organised well. A more experienced developer with a higher hourly rate may also solve a problem much faster. The real cost is affected by analysis, testing, project management, documentation, DevOps, bug fixing and the amount of work that later has to be redone.
When comparing proposals, ask not only for the hourly rate but also what the rate includes and how the workload is estimated.
What if we already have a Drupal website and want to change partners?
Do not start by ordering new features. First make sure the new partner can safely take over the system.
At minimum, you need:
- the Git repository and actual source code;
- Composer files and dependencies;
- Drupal administrator access;
- server and database access;
- the location of files and backups;
- a description of testing and production environments;
- the deployment process;
- access to external services and APIs;
- an overview of custom modules;
- a list of known issues and technical debt.
For the same reason, WebPro's project takeover service starts with checking access and the technical state of the system rather than immediately developing new functionality.
If the system's condition is unclear, a Drupal audit can be a sensible first step before commissioning larger development work.
How should you choose the right Drupal partner?
Define the type of project first and choose the company second.
If you are building a large new digital service from scratch, evaluate the partner's analysis, design, architecture and team capabilities. If you already have a Drupal system, look at maintenance, takeover experience, upgrades and the ability to work with someone else's code. If the project involves many integrations, ask for concrete examples involving APIs, authentication and connections to other information systems.
Then compare two to four partners using the same starting information. Ask them the same questions and, in addition to price, assess how well they understand the risks in your system.
WebPro focuses on long-term maintenance, upgrades, continued development and taking over existing Drupal projects. If that describes your situation, the first useful step may be a technical assessment or audit rather than immediately signing a development contract.
Frequently asked questions
Who provides Drupal development in Estonia?
Companies with publicly verifiable Drupal experience include ADM Interactive, Trinidad Wiseman, Web Expert, Krabu Grupp and Krabu Tech, Mearra, Limegrow, Revelan and WebPro. The list is not exhaustive and the companies have different profiles. Evaluate a partner based on the needs of the specific project, recent references and working practices.
Which is the best Drupal development company in Estonia?
There is no single provider that fits every type of project. A large greenfield development, maintenance of an existing website, a public-sector project and the takeover of an old Drupal system require different teams. Compare companies according to how closely their recent experience matches your project type.
Does a Drupal partner need to be based in Estonia?
Not necessarily. Drupal development can be delivered by an international team, although an Estonian partner can simplify communication, local procurement, contracts and Estonian-language support. Responsibility, competence, response times and project transferability matter more than office location.
Is a smaller Drupal company riskier than a large agency?
Not automatically. A smaller team may have less staff redundancy, but can offer more direct communication and deeper specialisation. A larger company will usually offer a broader range of competencies and greater ability to replace people within the project. In either case, ask who will actually deliver the work and how continuity is ensured.
How can I check a Drupal developer's technical competence?
Review recent Drupal projects and ask about Git, Composer, configuration management, testing environments, automated testing, security updates and deployment. For an existing project, also ask how custom code and technical debt are assessed. A visually impressive website alone does not prove good Drupal architecture.
Should the same company provide both development and maintenance?
It can be convenient, but it is not mandatory. What matters is that the result of development is documented and transferable, and that responsibility for maintenance is clearly agreed. If maintenance will be handled by another company, involve that company before the project ends rather than after the first security issue appears.
When should we conduct a Drupal audit before choosing a partner?
An audit is useful when the true state of an existing system is unknown — for example, when documentation is missing, updates have been neglected, the amount of custom code is unclear or the previous developer will no longer continue. An audit gives candidate partners more comparable starting information and reduces the risk of each bidder estimating a completely different scope of work.
Need Drupal help?
Send the website URL and a short context. We will tell you whether the sensible next step is an audit, maintenance, an upgrade or a migration.