Luban H5 is an open-source, GPL-3.0 licensed drag-and-drop builder that generates mobile H5 pages, built on Vue 2.0 and described by its maintainers as a mini Webflow for mobile pages, for developers and teams who want to self-host the design and publishing workflow that hosted platforms such as Eqxiu, Maka, and Baidu H5 provide.
What it is
Luban H5 (鲁班 H5) is a visual construction system for mobile web pages. A user drags components onto a canvas and the platform generates a page, which places it in the page-builder and design-tool category alongside Webflow, but scoped to mobile H5 output rather than desktop sites. It is written in JavaScript on top of Vue 2.0, with Ant Design appearing among its topics, and it is released under the GPL-3.0 licence. The repository carries 6,240 stars, 1,280 forks, and 109 open issues, with its most recent push in January 2026. Documentation exists in both Chinese and English, and a Gitee mirror serves users in mainland China.
The problem it solves is the hosted mobile page builder. Commercial platforms in that space keep the editor, the component library, and the published pages on the vendor's own infrastructure, which means the operator does not own the stack. Luban H5 replaces that arrangement with a self-hosted equivalent consisting of an editor front end and an API backend that the operator runs. The official backend API is built on Strapi.js and lives in the repository under the back-end/h5-api path, while two Java integrations are also published: SpringBoot2-JPA and SpringBoot2-Mybatis. The specific thing being replaced is therefore the hosted campaign-page and landing-page service, not a general-purpose content management system.
Key capabilities
- Drag-and-drop editor that generates mobile H5 pages directly, matching the page-builder, page-editor, page-maker, and page-generator topics on the repository.
- Vue 2.0 front-end architecture with Ant Design in the stack, per the listed topics and the README technical stack section.
- Official backend API implemented with Strapi.js, published in the repository at back-end/h5-api.
- Alternative Java backend integrations, SpringBoot2-JPA and SpringBoot2-Mybatis, for teams that cannot adopt a Node-based API.
- Official component library including the lbp-slide carousel and the lbc-button button.
- Supporting components for image libraries and for text alignment, the latter published as lbs-text-align.
- Custom component development through the vue-cli-plugin-lbhc scaffold, which ships with a wiki-based tutorial, plus a public roadmap tracked in GitHub Projects.
Who uses it and how
- Teams that need campaign and landing pages on infrastructure they control deploy the editor together with the Strapi.js backend instead of renting a hosted builder.
- Front-end developers extend the component set by writing custom components against the vue-cli-plugin-lbhc scaffold and the accompanying tutorial.
- Backend teams standardised on Java adopt one of the two SpringBoot integrations rather than the Strapi.js API, keeping the editor front end unchanged.
- Chinese-language teams are well served, since the Chinese documentation is the primary reference, a Gitee mirror hosts the source, and community support runs through Gitter, GitHub Discussions, and a Tencent forum.
- The project has accumulated 1,280 forks, which indicates a community large enough that the custom-component path is a realistic way to add capability rather than a theoretical one.
Getting started
Start from the GitHub repository or the Gitee mirror, then follow the Chinese or English getting-started documentation hosted at the project's documentation site, pairing the editor with the official Strapi.js backend API or one of the SpringBoot integrations. A hosted demo is available for evaluation at the project homepage.
How it compares
Against the hosted platforms the README names as equivalents, Eqxiu, Maka, and Baidu H5, the decisive difference is that Luban H5 is GPL-3.0 licensed source code rather than a closed service. Because the editor and its Strapi.js or SpringBoot backend can both be deployed on the operator's own servers, the pages, components, and assets remain under the operator's control, and there is no per-page or per-account fee model to reason about. The trade is operational: the hosted platforms remove the need to run anything, while Luban H5 hands that responsibility, and licence obligations, to the adopter.
When to use it — and when not to
Choose Luban H5 when the mobile page builder must be self-hosted and the team can operate both the Vue front end and a backend service, since Strapi.js or one of the SpringBoot integrations has to be deployed and maintained alongside it. Do not choose it if the requirement is a fully managed service with no operations burden, if the codebase must remain closed source, or if a current-generation front-end stack is mandatory, because the editor is built on Vue 2.0. The README and tagline are still marked as work in progress and the custom component tutorial is likewise flagged WIP, so the documentation is thinner than the 6,240-star count might suggest, and the 109 open issues indicate an active but unfinished backlog.
