# yudao-ui-admin-vben: a full admin console with four UI libraries > This repository is the admin front end for the Yudao platform, rebuilt on vue-vben-admin 5.7 with Vue 3, Vite 8 and TypeScript, and it ships the same product against Ant Design Vue, Element Plus, Naive UI and TDesign. The business surface is enormous, covering tenants, workflows, payments and a long list of vertical systems. **yudaocode/yudao-ui-admin-vben** — ruoyi-vue-pro-vben 芋道管理后台，基于 vben5.0 最新版本，最新的 vue3 vite6 ant-design-vue typescript 语法进行重构开发，支持 springboot3 springcloud 版本 - Repository: https://github.com/yudaocode/yudao-ui-admin-vben - Website: http://doc.iocoder.cn - Stars: 902 · Forks: 365 - Language: Vue - License: MIT - Published: 2026-10-20 · Updated: 2026-10-20 · Language: en - Canonical page: https://hysenlabs.com/projects/yudaocode-yudao-ui-admin-vben ## One admin console, four component libraries The repository is the admin front end for the Yudao platform, and its description explains the lineage plainly: it is the ruoyi-vue-pro-vben admin, rebuilt on the latest vben 5.0 release using Vue 3, Vite 6, ant-design-vue and TypeScript, with Spring Boot 3 and Spring Cloud support on the backend side. What sets it apart is that the component library is not a decision the user makes. The platform supports Ant Design Vue, Element Plus, Naive UI and TDesign, described as multiple free and open source admin templates. The demonstration links in the readme give one live deployment per variant, a Vue 3 plus element-plus build, a Vue 3 plus vben5 with ant-design-vue build, and a Vue 2 plus element-ui build. Shipping one product against four component libraries is an unusual commitment. It means the pages have to be written against an abstraction, and it means the team maintains four visual skins of the same workflows. The payoff is that a customer who has standardised on Element Plus or Naive UI can adopt the admin without a visual mismatch. The cost is real and it lands on every screen. Anything that touches a component API has to be written four times or abstracted, and the moment a new feature needs a behaviour that differs between libraries, the abstraction has to grow a branch. The technical stack table shows the versions in use: Vue 3.5.35, Vite 8.0.10, TypeScript 6.0.3, Tailwind CSS 4.3.0, Pinia 3.0.4 replacing Vuex, vue-router 5.1.0, vue-i18n 11.4.4, vueuse 14.3.0, Iconify 5.0.1, TinyMCE 7.3.0 for rich text, Echarts 6.1.0 for charts, axios 1.16.1 for HTTP, dayjs 1.11.21, vee-validate 4.15.1 for form validation and zod 3.25.76 for data validation. The combination of zod and vee-validate is worth noting. Zod describes the shape of data and vee-validate drives the form, so the schema can be shared between the two. ## The monorepo runs one app per UI library The package manifest makes the shape explicit. The package name is vben-admin-monorepo at version 5.7.0, it is private, and the build script is a turbo build with a raised heap limit. ```json "build": "cross-env NODE_OPTIONS=--max-old-space-size=8192 turbo build", "build:antd": "pnpm run build --filter=@vben/web-antd", "build:ele": "pnpm run build --filter=@vben/web-ele", ``` So there is a package per variant, named with a scope. The antd script builds @vben/web-antd, the ele script builds @vben/web-ele, and there are matching ones for naive and tdesign, plus a build:antdv-next variant for the newer ant-design-vue, a build:docs for the documentation site, and a build:docker that runs a shell script for building a local Docker image. The 8192 megabyte heap setting is not incidental. Building several variants of a large admin application in parallel is what pushes the default Node heap, and the fact that it is set globally rather than per script tells you how heavy this build is. The scripts around it show a project with real engineering discipline. There is a check target that chains a circular dependency check, a dependency check, a type check and a spell check, and the individual checks use vsh for circular and dependency analysis, turbo for typechecking and cspell for the spell check across TypeScript files, READMEs and changeset entries. There is a changeset script for release notes, a clean script that runs a node file, and a commit script using czg for conventional commits. That changeset workflow matters for a template project, because a fork of it will need to describe its own changes relative to upstream. The top level entries back this up: a .changeset/ directory, lefthook.yml for git hooks, oxlint.config.ts and oxfmt.config.ts for linting and formatting, eslint.config.mjs, stylelint.config.mjs, cspell.json, a .browserslistrc, a .node-version file, turbo.json for the pipeline configuration, apps/, packages/ and internal/ directories, and a vben-admin.code-workspace file for editor setup. ## The business surface is where the weight actually sits The feature listing is where this stops being a template and becomes a platform, and it is worth reading in two halves. The first half is the generic system management layer. There is user management, role management with menu permission assignment and data scope division by organisation, menu management covering operation and button level permissions, department management with tree structures, post management, and then the multi-tenancy features, tenant management for SaaS scenarios, tenant packages for customising per-tenant permissions, and application management for SSO with multiple OAuth2 authorisation methods. Also dictionary management for fixed reference data, SMS management wired to Alibaba Cloud and Tencent Cloud, email management with templates and send logs, in-app messaging, operation logs generated with Swagger integration, login logs including anomalies, error code management editable online without restarting the service, notification announcements, sensitive word filtering with tag grouping, and region management mapping IP addresses to cities. The second half is the business modules, listed as on demand: an e-commerce mall, ERP for enterprise resource planning, WMS warehouse management, CRM, CMS, MES for manufacturing execution, HRM for human resources, FMS for finance, PMS for project management, office automation, an AI large model platform, an IoT system, an instant messaging system, a mobile client and a data screen for reporting. The infrastructure section sits alongside and is equally substantial. Code generation for Java, Vue, SQL and unit tests with CRUD download, automatic RESTful API documentation from Swagger, database documentation generated with Screw in Word, HTML and Markdown, a drag-and-drop form builder, dynamic configuration loading in Spring Boot, scheduled tasks with execution logs, a file service storing to S3 providers, local disk, FTP or the database, WebSocket examples, API access and exception logs, MySQL connection pool monitoring to find SQL bottlenecks, Redis usage monitoring, a Redis based message queue with streams for clustered consumption and pub/sub for broadcast, Java application monitoring via Spring Boot Admin, distributed tracing and a log centre through SkyWalking, distributed locks, idempotency and rate limiting through Redis, a lightweight remote log service, and unit test scaffolding on JUnit with Mockito. The workflow section alone lists more than twenty capabilities, from two designers, one simplified and BPMN based, through countersigning, or-signing, sequential approval, carbon copy, rejection, transfer, delegation, adding and removing approvers, withdrawal, termination, per-node form permissions, timeout approval, automatic reminders, parent and child processes, and four kinds of branching. ## The declared no commercial version promise, and what it means The readme opens with a statement in bold that is worth translating carefully. It declares that there will be no commercial version now or in the future, and that all the code is open source. What follows is personal: the author describes working in Shanghai at a top three company by day and contributing to open source at night, and asks for stars in return. The licence field on the repository says MIT, and the LICENSE file is at the root. This is not legal advice, but MIT is a permissive licence with attribution requirements and no copyleft obligations, which for a template that people fork and modify is the right choice. There is also a note about outsourcing work, with a link for custom development requests and a request not to contact them for project questions. That is a sensible boundary to set for a volunteer maintainer, and it tells you something useful about the shape of the project: it is maintained by one person in their spare time, with commercial work routed elsewhere. That has an implication for anyone adopting it. The platform documentation is at doc.iocoder.cn, the quick start guide and video tutorials are linked from the readme, and the backend is documented separately at doc.iocoder.cn for the Spring Boot monolith architecture and cloud.iocoder.cn for the Spring Cloud microservice version. The frontend and the backend are separate projects that this repository points at. That is not unusual for a platform, but it does mean that adopting the admin front end alone means wiring it to a backend you also have to obtain, and the two are versioned separately. ## Conclusion yudao-ui-admin-vben suits a team building a Chinese market admin product that needs tenants, dynamic route permissions, a workflow engine and a code generator already assembled rather than built from scratch. It does not suit a project that wants a lightweight admin shell, because the platform layer, the workflow engine and the vertical modules are all in the same repository, and it does not suit a team with no appetite for the Vue and Element Plus conventions the codebase assumes. Before adopting it, run the four UI variants against your own design requirements, because the component library choice is baked into the pages rather than being a theme you can swap later. ## FAQ ### What is yudao-ui-admin-vben? It is the admin front end for the Yudao platform, rebuilt on the latest vue-vben-admin 5.0 release using Vue 3, Vite and TypeScript, with a companion Spring Boot and Spring Cloud backend. It ships the same admin product against Ant Design Vue, Element Plus, Naive UI and TDesign. ### Which UI component libraries does yudao-ui-admin-vben support? Ant Design Vue at 4.2.6, Element Plus at 2.14.1, Naive UI at 2.44.1 and TDesign at 1.20.0, with separate build scripts and separate app packages for each variant, so the same pages are shipped against four different component libraries. ### What does yudao-ui-admin-vben include beyond generic admin screens? Multi-tenancy with tenant packages and SSO application management, a workflow engine with two designers and around twenty approval capabilities, a payment module covering Alipay and WeChat channels, data reporting, and business modules on demand including mall, ERP, WMS, CRM, CMS, MES, HRM, FMS, PMS, OA, an AI platform, IoT, instant messaging and a mobile client. ### What licence does yudao-ui-admin-vben use? MIT, with a LICENSE file in the repository root. The readme also declares that there will be no commercial version now or in the future and that all code is open source, while noting that the author works on the project in their spare time and routes commercial enquiries elsewhere. ### What tools does the yudao-ui-admin-vben monorepo use for quality checks? Turbo drives the build and type checks, vsh runs the circular dependency and dependency checks, cspell lints TypeScript files, READMEs and changeset entries, and oxlint and oxfmt handle linting and formatting. Release notes are managed with changesets, and the build raises the Node heap to 8192 megabytes because the parallel variant builds are heavy. ## Sources - [Issues](https://github.com/yudaocode/yudao-ui-admin-vben/issues) - [License: MIT](https://github.com/yudaocode/yudao-ui-admin-vben/blob/master/LICENSE) - [README](https://github.com/yudaocode/yudao-ui-admin-vben/blob/master/README.md) - [Releases](https://github.com/yudaocode/yudao-ui-admin-vben/releases) - [yudaocode/yudao-ui-admin-vben on GitHub](https://github.com/yudaocode/yudao-ui-admin-vben) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/yudaocode-yudao-ui-admin-vben