Our Expertise

We have been in the business for the past 21 years, and have the expertise, experience, wisdom and knowledge to handle any ICT and Telecom Projects in Bhutan, we have completed 100+ Government Projects in Software and Applications, and in Thousands for Infrastructure and Supplies.

Proven ICT Excellence

Delivering over a decade of digital transformation across Bhutan. eDruk has led ICT modernization for government agencies, private enterprises, and national-scale initiatives. Our expertise spans software engineering, cloud infrastructure, cybersecurity, and smart digital ecosystems—built with reliability, innovation, and Bhutan-centric design at the core

100+ Software Solutions Delivered

A trusted development partner for mission-critical applications. With more than 100 custom software systems built—ranging from enterprise MIS, booking platforms, mobile apps, AI-powered tools, to financial gateways—eDruk has a proven record of delivering scalable, secure, and user-friendly solutions tailored to Bhutan’s digital needs.

End-to-End Digital Infrastructure Services

From equipment sourcing to deployment, maintenance, and lifecycle support. Our complete digital value chain ensures customers never struggle with incompatible hardware, unreliable software, or broken processes. eDruk provides seamless ICT integration—including networking, servers, cloud environments, IoT solutions, and cybersecurity—so businesses operate without disruption.

AI, IoT & Data Intelligence Innovation

Driving Bhutan’s next generation of smart technology. We design and deploy intelligent systems powered by AI, machine learning, and IoT devices. From automation and smart monitoring to analytics dashboards and predictive insights, eDruk empowers organizations to make smarter, faster, data-driven decisions.

Secure, Reliable, and Compliant Systems

Enterprise-grade security for an evolving digital landscape. Our solutions incorporate multi-layered security, encrypted communication, access control, and industry-standard best practices. Whether safeguarding financial data or protecting government systems, eDruk ensures maximum uptime, resilience, and operational peace of mind.

Digital Growth & Innovation Partner

Helping organizations scale with modern tools, marketing, and technology. Beyond software, eDruk supports digital adoption through social media strategy, SEO, digital branding, campaign automation, and strategic transformation consulting. We help businesses grow online, engage customers, and unlock new revenue opportunities.

Get A Free Consultation
Available 24/7
Our AI Chatbot

99% Satisfed Clients

Client 0 Client 1 Client 2 Client 3

News

Updates, News and Announcements from eDruk

News

Connecting Your Business Systems: 7 Things to Know About Integration and APIs

Many Bhutanese organisations now run several separate systems: an accounting package, a billing or point-of-sale tool, a website, spreadsheets for stock or HR, and sometimes a mobile app. Each one works well on its own, but staff often copy the same information from one system into another by hand. That double entry takes time and creates mistakes. Connecting your systems, usually through APIs (Application Programming Interfaces), lets data flow between them automatically. Here are seven things to think about before you start.

1. Map where your data lives today

List every system your team uses and what information each one holds: customers, orders, invoices, stock, staff records. Then note where the same data is typed in more than once. This simple map shows where integration would save the most effort and where errors usually creep in.

2. Start with one painful process

Trying to connect everything at once makes projects slow and risky. Pick one process that clearly wastes time, such as sending website orders into your billing system or updating stock after each sale. A small, well-defined first step is easier to test and shows value early.

3. Check what your existing software can offer

Some software already provides an API, import and export options, or built-in connectors. Others are closed and hard to link. Ask your vendors what integration options exist, whether there are extra licence costs, and what documentation is available. The answer often decides whether a direct connection, a scheduled file transfer or a small custom tool is the right approach.

4. Decide which system is the “source of truth”

When two systems hold the same information, you need to agree which one is correct if they disagree. For example, customer details might be owned by your billing system, while product prices are owned by your inventory system. Clear rules prevent records from overwriting each other and keep reports consistent.

5. Plan for security and access

Integrations use accounts, keys or tokens to talk to each other. Treat these like passwords: give each connection only the access it needs, store keys securely, and change them when staff or vendors change. Use encrypted connections (HTTPS) whenever data travels over the internet, especially for personal or financial information.

6. Think about what happens when something fails

Networks drop, servers restart and software gets updated. A good integration records what it sent and received, retries safely when a connection fails, and alerts someone when it cannot recover. Without this, missing orders or invoices may go unnoticed for days. Agree who will watch these alerts and how problems will be fixed.

7. Test with real scenarios and document it

Before going live, test with realistic examples: a normal order, a cancelled order, a duplicate, a missing field. Check that the results match on both sides. Then write down how the integration works, which systems it touches and who to contact. This makes future upgrades and staff changes much smoother.

Getting started

Connecting your systems does not have to be a large project. A clear map of your data, one well-chosen first process and attention to security and error handling can remove a lot of manual work and improve the accuracy of your records.

eDruk Private Limited has been developing software in Bhutan since 2004, including web and mobile applications and technical consultation. If you would like to discuss how your existing systems could work together, contact us at edruk@edruk.com.bt, call +975 2 332277, or visit www.edruk.com.bt.

News

Testing New Software Before Go-Live: 7 Steps for User Acceptance Testing

New software is often judged on the day it goes live. If staff cannot find a screen, a report shows the wrong totals, or a form rejects a perfectly valid CID number, confidence drops quickly, and it takes far longer to win back than it would have taken to catch the problem early. User acceptance testing (UAT) is the step where the people who will actually use a system check that it works for their real, everyday tasks before it is switched on for everyone.

Whether you are launching a new web application, a mobile app, an internal records system or an upgrade to an existing one, these seven steps help Bhutanese organisations test with purpose.

1. Agree what “ready” means

Before testing begins, write down what the system must do for you to accept it. Base this on the original brief or requirements: the key tasks, the reports management needs, and any rules the system must follow. A short, agreed list of acceptance criteria avoids arguments later about whether something is a defect or a new request.

2. Choose testers who do the work

The best testers are the staff who will use the system daily: the accounts assistant, the front-desk officer, the field supervisor. Include at least one person from each role, and give them protected time. Testing squeezed between other duties tends to be rushed and shallow.

3. Write simple test scenarios

Turn everyday work into step-by-step scenarios. For example: “Register a new applicant, upload a document, approve it, and print the letter.” Each scenario should state the expected result. Include the awkward cases too: long Dzongkhag and gewog names, missing fields, duplicate entries, cancelled transactions and month-end reports.

4. Test with realistic data in a safe copy

Use a separate test environment, not the live system. Fill it with realistic sample records so screens and reports behave as they will in practice. If you use copies of real records, limit who can access them and remove personal details where possible. Try the system on the devices and connections your staff really use, including older laptops, phones and slower internet links in district offices.

5. Record issues clearly

A note that says “it doesn’t work” is hard to fix. For each issue, record what you were doing, what you expected, what happened instead, and a screenshot if possible. Keep everything in one shared list or tracker, and give each issue a priority: must fix before go-live, should fix soon, or nice to have later.

6. Retest fixes, and check nothing else broke

When the development team reports a fix, the person who found the issue should confirm it. It also helps to rerun a few core scenarios after each round of changes, because a fix in one place can occasionally affect another. Plan for at least two rounds of testing rather than one.

7. Sign off and plan the go-live

When the agreed criteria are met and no “must fix” issues remain open, record a formal sign-off by the responsible manager. Then plan the switch-over: when it will happen, how existing data will be moved, who staff should call for help in the first weeks, and how you would roll back if something serious appears. Known minor issues can go into the support and maintenance plan.

Testing is part of the project, not an extra

Good testing does not need expensive tools. It needs clear criteria, the right people, honest feedback and enough time in the schedule. Building UAT into the project plan from the start makes go-live calmer for everyone and gives staff a system they already trust.

Talk to eDruk

Since 2004, eDruk Private Limited has developed software, web and mobile applications and ICT systems for organisations in Bhutan. If you are planning a new system and would like help preparing acceptance criteria, test scenarios or a go-live plan, or you would like us to build the solution with you, get in touch.

News

Two-Step Verification for Your Office: 7 Steps to Protect Business Accounts

Most account break-ins in small and medium organisations do not involve clever hacking. They start with a password that was reused, guessed or typed into a fake login page. Two-step verification (also called multi-factor authentication, or MFA) adds a second check, so a stolen password alone is not enough to get in. Here are seven practical steps for Bhutanese offices that want to switch it on without disrupting daily work.

1. Start with the accounts that matter most

You do not have to protect everything on day one. Begin with business email, accounts that control your domain name and website, cloud storage, banking and payment portals, and administrator accounts for servers, routers and software. If one of these is taken over, the damage spreads quickly to everything else.

2. Choose the right second step

There are several kinds of second factor. An authenticator app on a phone generates a short code that changes every few seconds and works even without mobile data. A hardware security key plugs into a USB port or taps a phone and is very resistant to phishing. SMS codes are better than nothing, but they depend on mobile coverage and can be intercepted, so treat them as a fallback rather than the first choice for important accounts.

3. Prepare backup options before you need them

Phones get lost, broken or replaced. When you turn on two-step verification, save the backup or recovery codes the service offers and store them somewhere safe, such as a locked drawer or a password manager, not in the same email account they protect. Where possible, register a second method so one lost device does not lock a staff member out.

4. Use a password manager alongside it

Two-step verification works best with strong, unique passwords. A reputable password manager lets each person keep a different long password for every service without memorising them all. It also helps against phishing, because it will not fill in a password on a look-alike website.

5. Roll it out in stages and explain why

Staff accept a new login step more easily when they understand the reason. Announce the change, give a short demonstration, and enable it for a small group first, such as management and finance, before the whole office. Pick a quiet week rather than a deadline period, and have someone available to help with setup.

6. Watch for prompt fatigue and fake requests

Some attackers send repeated login approval prompts hoping someone will tap “approve” just to make them stop. Teach staff a simple rule: if you did not just try to sign in, never approve the request, and report it. A surprise prompt usually means someone else has the password, so it should be changed straight away.

7. Keep it up to date as people and devices change

When staff join, leave or change phones, their second factors need updating too. Include two-step verification in your onboarding and offboarding checklists, remove old devices from accounts, and review administrator accounts every few months to make sure each one is still needed and still protected.

A small step with a big effect

Two-step verification takes a few minutes per account to set up, yet it closes one of the most common ways into an organisation’s email, files and systems. Combined with good passwords, regular backups and staff awareness, it gives your office a much stronger foundation.

Need help getting started?

eDruk Private Limited has been providing software, networking and technical consultation in Bhutan since 2004. If you would like help planning account security, setting up business email safely or reviewing how your systems are protected, get in touch with our team.

Email: edruk@edruk.com.bt
Phone: +975 2 332277
Website: https://www.edruk.com.bt