Why WeebPal

About WeebPal: Drupal and Web Development Since 2012

We build, upgrade and maintain Drupal sites and web applications for agencies, under their name, and for companies and organisations, including moves off Drupal 7 and WordPress. We also deploy our platforms for training, restaurant ordering and bookings.

An engineer reads it and replies within one business day.

  • Full source code from the first commit
  • Price fixed once the architecture is agreed
  • Warranty: one year by default, up to three

Finalist, Splash Awards Asia 2024: EverLMS in the Education category and WE Mega Menu in the Open Source category (list of finalists on TheDropTimes).

What we do

White-label Drupal for agencies, builds and migrations for companies, and platforms we run

  • Agencies that need Drupal engineers under their own name

    We build in your repository and tracker, look after your clients' live sites under your brand, reserve engineers for you by the month, or join your tender as a named subcontractor. A mutual NDA comes first, non-solicitation runs both ways and the warranty is held by your agency.

    Nothing we deliver under an agency's name appears on this site. Agencies that give us Drupal work have reviewed us by name, among them Ingenuity Solution in the United States and Sazae in Australia.

    Partner programme
  • Companies and organisations: new builds, migrations, upgrades and support

    We design and build websites, portals, intranets, web applications and Drupal Commerce stores. We move sites off Drupal 7, WordPress, Joomla or a bespoke CMS with their content, users and files, and upgrade Drupal 10 sites to 11 and 12. We also maintain live sites, including ones another team built, after a takeover audit.

    Running today: CreAct's CAB and iCAB application for a consultancy in the UAE and Switzerland, and Apex Embroidery Designs' store, moved off Drupal 7.

    What we build
  • Platforms we build and run, for training, restaurant ordering and bookings

    EverLMS runs training, MenuNerds restaurant ordering, MineRooms hotels, MineCourt court bookings and MineTickets tickets and appointments. We deploy one on your domain with your roles and content set up, and adapt it where you need more; what already runs is not charged as if it were written again, and you receive the running system and its source code. Agencies deliver the same platforms to their clients with us, under the agency's name.

    Running today: EverLMS for JFC's staff training and MenuNerds for a restaurant franchise, both in Australia, and MineCourt for badminton venues in Ho Chi Minh City.

    Our platforms

Milestones

What we have built, year by year

Each client system named here is still running, and each links to its case study or platform page.

  1. 2012: WeebPal is founded

    Zircon, the first thing we publish on Drupal.org, goes up that March and later becomes the first free Drupal 8 theme there.

  2. 2012 to 2017: Free themes for the Drupal community

    Business, portfolio, blog and e-commerce themes for Drupal 7 and 8, released free and kept today as reference.

    Free Drupal themes
  3. 2017: sprep.org redesigned

    We redesign SPREP's main site and rebuild its Drupal theme; SPREP brings the second redesign back to us in 2024.

    SPREP case study
  4. 2021: Apex Embroidery Designs leaves Drupal 7

    We design the store and rebuild it on Drupal, carrying its catalogue and data over from Drupal 7.

    Apex Embroidery Designs case study
  5. 2023: H&N Corporation

    One Drupal site for H&N's services between Australia and Vietnam, with visa and passport applications made online behind a customer account.

    H&N Corporation case study
  6. 2024: CreAct's CAB and iCAB application

    For a strategy consultancy in the UAE and Switzerland, we build a web application on Drupal from scratch, with each client company given its own permissions.

    CreAct case study
  7. 2026: JFC on EverLMS

    JFC's safety, compliance and operations training for staff and contractors in Australia goes live on EverLMS, deployed and customised by us.

    JFC case study
  8. 2026: MenuNerds for a restaurant franchise

    MenuNerds goes into production for a restaurant franchise in Australia, each store on its own subdomain and guests ordering by QR code at the table.

    MenuNerds

Our commitments

What you can hold us to

Each of these has its own page, which sets out what it covers and where it stops.

  • A prototype before you sign

    For a new build or one of our platforms, the first thing you see is a design, a clickable prototype or a working demo on real code, made at no charge before anything is signed.

    How we work
  • A price fixed once the architecture is agreed

    Scope and cost are committed against an architecture you have seen, and they move only if you change the scope.

    Project sizes, Micro to Strategic
  • The source code is yours

    Custom work is yours from the first commit: the repository, custom modules, theme and deployment configuration.

    Source code ownership
  • A warranty of one to three years

    One year by default on every development project, up to three by agreement, with defects fixed by the team that built the system.

    Warranty terms
  • Response targets we publish

    A first response in 4 hours for critical issues, 1 business day for high priority and 3 business days for normal. Support runs in business hours; cover outside them is an option, priced separately.

    Support and maintenance
  • Code you can read before you hire us

    Our modules are published on Drupal.org, where anyone can read the code and the issue queues; the current WE Mega Menu release runs on Drupal 10.3, 11 and 12.

    Our open-source work

Where we are

Ho Chi Minh City, on Indochina Time

The clients in our case studies and reviews are in Australia, the United States, Europe, the Middle East and the Pacific.

Get in touch

Questions

Questions we get asked

Who will we talk to?

An engineer. Every enquiry is read by an engineer, and the first call about a project is with one; the team page sets out who does what.

Do you only work with Drupal?

Drupal is the core of what we build. Our web development service also takes work outside Drupal, and front-end frameworks such as Vue.js or React are used where a project needs them, as supporting technology rather than a separate line of work.

Why Drupal?

Because a large share of any enterprise platform is users, roles, permissions, audit history, translation and an administrative interface, and Drupal has those tested, maintained and open. Starting from a bare framework means rebuilding them and owning the bugs. It is also open source, which is what makes handing you the whole thing possible.

Do you build mobile apps?

Only as part of a web system we build, where a native app is genuinely warranted: offline use, push notifications or hardware the browser cannot reach. We build it in Flutter against the same API, and we do not take standalone app work.

What does the warranty actually cover?

Defects in what we delivered on a development project, measured against what was agreed, and the Drupal core and contributed security releases applied during the term. It is not a support contract and does not cover a change of requirement; the warranty page sets out the boundary in full.

See it working before you commit

Before a build is signed, we make a working prototype at no charge, so you decide against something real.