Who we are
WeebPal builds enterprise software on Drupal and has done since 2012. We work for governments, universities and companies who need a platform that will still be theirs in ten years, which is why every client engagement ships with the full source code, a price fixed once the architecture is agreed, and a warranty of one year by default, up to three. We are an engineering firm rather than an agency: the people who design a system are the people who build it and the people who fix it afterwards.
The company is headquartered in Ho Chi Minh City, Vietnam, and it is independent: no holding company, no investor deciding which platform we recommend, and no reseller agreement that pays us to prefer one vendor over another.
It is organised around delivery rather than accounts. There is a production team building and maintaining the platforms, a quality team that owns automated testing and static analysis, a design team, a systems team running infrastructure and deployment, an AI team, a support team, project management, and a research group.
What we are known for outside client work is Drupal itself. We maintain WE Mega Menu, a navigation module in use on thousands of Drupal sites, along with Component Builder and a library of free themes. That work is published at open source, and it is a reasonable way to judge how we write code before you hire us to write any for you.
How we work
The commitments behind every engagement
You see working software before you commit
An engagement does not begin with a specification document; it begins with a prototype running on your own content. Requirements written in prose are agreed by people who each picture something different. A prototype is corrected by people looking at the same thing. Only once it matches what you meant do we design the architecture and break the build into sprints, each ending in a demonstration you review.
The price is fixed once the architecture is agreed
Scoping happens in a paid discovery phase, because doing it properly is real work and doing it for free means doing it badly. After that the cost is committed against an architecture we stand behind, and it does not move unless you change what is in scope. Payment is milestone-based, and go-live is one of the milestones. The bands are published at pricing.
You own the source code
Every client build ships with the full source code from day one. Host it where you like, hire anyone you like to continue it, and pay us nothing to keep running it. Why we take that position, including what it costs us, is at source code ownership. Agency partners who license one of our platforms are the one exception, and those terms are agreed before they commit, never after.
What happens after handover
A project is done when it is running in production and your team can operate it, not when it is handed over. Every development project carries a warranty of one year by default, up to three by agreement, covering defects in what we delivered against what was agreed. The scope and the boundaries are written out at warranty policy, including what it does not cover, because a warranty that has never had its edges described is a marketing line rather than a commitment.
The same team that built a system supports it. Where a client wants ongoing care beyond defects (security advisories applied, monitoring, performance work, small changes), that is a maintenance engagement, priced monthly and separate from the warranty. We are clear about which is which, because conflating them is how clients end up paying twice for one thing and nothing for another.
Clients
Who we build for
Our clients cluster in places where software has to last and be handed over rather than replaced every few years. The projects we can publish are in the portfolio, and what clients have said about the work, with named people and organisations, is at reviews.
-
Government and public sector
Government and public sectorCitizen-facing portals, multi-step applications, document handling and regional programmes. Published work includes SPREP, the Pacific Islands Roundtable, PRISMSS, ERSRI and Fort Bend County.
-
Education
Education and e-learningUniversity sites and learning platforms, including Toyo University and UTS ResHub.
-
Corporate and enterprise
Corporate and enterpriseInternal portals and operational platforms, including Petronas Lubricants and Plasseraud IP.
-
Hospitality, sports and commerce
All sectorsBooking, venue and commerce platforms, the booking ones often built on our own platforms.
Products, not just projects
Alongside client work we build and run our own platforms. The ones we publish are EverLMS for learning management, MineRooms for hotel and property management, MineCourt for court and venue booking, MenuNerds for restaurant ordering, and OpenConstruction for construction job costing. They are listed at platforms.
They exist because a client whose requirement is mostly a solved problem should not pay to have it built again: starting from a platform already in production shortens delivery without thinning the scope. Maintaining our own systems in production also keeps us honest about the cost of decisions we would otherwise only recommend to other people.
Agencies can license these platforms and take them to their own market under their own name, with the majority share theirs. That is the partner programme.
How to reach us
WeebPal, Ho Chi Minh City, Vietnam. Our working day is Indochina Time, UTC+7: a shared day with Australia and New Zealand, and hours of overlap with Europe and the UK every afternoon.
- Email: [email protected]
- Phone: +84 938 893 995
- Open source: github.com/weebpal and our modules and themes
- LinkedIn: linkedin.com/company/weebpal
If you are evaluating us, the fastest honest test is to ask for a demo. We build a working prototype on your own content and you decide against something real rather than against a slide.
Questions
Questions we get asked
- How long has WeebPal been going?
Since 2012. The company has been building on Drupal for its whole existence, which is why the work spans Drupal 7 through Drupal 11 and the version upgrades between them.
- Where are you based?
Ho Chi Minh City, Vietnam, working on Indochina Time, UTC+7. Clients range from the Pacific and Japan to Europe and the United States.
- Do we really own the source code?
Yes, from day one, on every client build. You can host it anywhere and hire anyone to continue it. The one exception is an agency licensing one of our platforms, where the licence terms are agreed before signing rather than after.
- What does the warranty actually cover?
Defects in what we delivered on a development project, measured against what was agreed: one year by default, up to three by agreement. It is not a support contract and it does not cover a change of requirement; the warranty policy page sets out the boundary in full.
- Are you an agency or a software company?
An engineering firm that also runs its own products. We do not sell media, advertising or retained marketing; we build systems and then keep them running. The people who design a system are the people who build it and the people who fix it afterwards.
- 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.