# Skyeye ERP Pro: a partial open source ERP with a commercial code base behind it > The erp-pro repository is the open trunk of the SkyEye manufacturing platform, a Spring Cloud Alibaba suite with dozens of business modules, a zero-code designer and a large AI feature set. The important detail is in the README: the open repository does not contain all the code, and the full business source is available only through a paid membership. **weizhiqiang1995/erp-pro** — Skyeye云零代码，采用Springboot + UNI-APP + Ant Design Vue的框架的快速开发平台。包含50多种电子流程，CRM、PM、ERP、MES、ADM、OA、EHR、AI、项目、商城、财务、多班次考勤、薪资、招聘、云售后、论坛、问卷、报表设计、工作流、Saas等功能。打造全网首套零代码、功能最全、价格最优惠的智能制造行业供应链一体化管理软件。 - Repository: https://github.com/weizhiqiang1995/erp-pro - Stars: 652 · Forks: 173 - Language: Java - License: MIT - Published: 2026-10-21 · Updated: 2026-10-21 · Language: en - Canonical page: https://hysenlabs.com/projects/weizhiqiang1995-erp-pro ## The open repository is not the whole product The most important sentence in this README is in the section about source code and commercial versions, and it changes what adopting this project means. The README states plainly that the open source repository does not contain all the code, and that the full business source code is obtained by taking out a Skyeye membership. Membership source is described as supporting study and research, thesis projects and commercial secondary development, and the project supports local private deployment with all functions unrestricted in use. There is a second dimension to the arrangement. The project belongs to the Dromara open source community, where the open trunk continues to be iterated, and a commercial complete-source membership service is offered alongside it. Membership buyers are also told they can remove the original project's copyright and author marks from a self-developed derivative product. So the repository is a genuine open source artefact with a real community and a real trunk, and it is also the marketing surface for a paid product whose fuller code is elsewhere. Both things are true, and a technical decision has to account for both. The repository metadata says the licence is MIT and the LICENSE file sits at the root, and the primary language is Java. The default branch is company_server, and the last push was on 2026-10-15 with no GitHub releases, so there is no tagged version to pin. ## A Spring Cloud Alibaba estate with five services The environment table is where a reader learns what this thing actually requires, and it is a real microservices deployment rather than a single jar. The base runtime is JDK 1.8. Alongside it the stack expects Nacos 2.3.0 as registry and configuration centre on port 8848, RocketMQ 4.9.2 as the distributed message queue on 9876, Redis 5.0 or 6.x as cache on 6379, and MySQL 5.7 or later as the business database on 3308, which is an unusual choice of default port that you will meet again in the configuration. The rest of the component list in the technology table is equally concrete. Spring Cloud Alibaba 2.1.0.RELEASE is the microservice base, Sentinel 2.1.0.RELEASE handles traffic circuit breaking and service fault tolerance, XXL-Job 2.3.0 provides distributed scheduled tasks, Activiti 6.8.0 is the workflow engine, Mybatis-Plus 3.5.7 is the ORM layer, Druid 1.2.23 is the connection pool, and Hutool and Lombok handle utilities and code simplification. The front end is split by device. On the PC side it is Vue 3 with Vite 5 and Ant Design Vue 4. On mobile it is uni-app on Vue 3, compiled from one codebase to Android, iOS, mini programs and H5. Two observations for an evaluator. First, a JDK 1.8 baseline with Spring Cloud Alibaba 2.1.0 places this stack in a particular era, which is consistent with the version of Nacos and RocketMQ listed, and it constrains which JVM and container images you can use. Second, the sheer number of required services means a first run is not a single command: you are standing up a registry, a broker, a cache, a database and the application tiers before anything renders. ## Twenty services in the repository root The top-level directory listing is the clearest view of the product decomposition, and it is a good map of what a buyer of the full source is getting. The business modules are named after their function: skyeye-erp for the inventory and supply chain side, skyeye-crm for customer management, skyeye-adm for administration, skyeye-project for project management, skyeye-shop for the storefront and orders, skyeye-tms for transport, skyeye-school, skyeye-wall, skyeye-report for reporting, skyeye-monitor for monitoring, and skyeye-auto for the automated testing platform. There is also skyeye-flowable for the workflow side, matching the Activiti entry in the technology table. The platform services sit alongside them. skyeye-portal is the entry point, skyeye-zuul is the gateway, skyeye-seata provides distributed transaction handling, skyeye-seal-service is the sealing service, skyeye-choose-topic and skyeye-promote are auxiliary services, skyeye-base-images holds shared images, skyeye-doc is the documentation component, and xxl-job-2.3.0 is the scheduled task scheduler vendored at the exact version named in the dependency table. Vendoring xxl-job at a pinned version inside the repository is a small decision with a large consequence. It tells you the project is assembled for a known environment rather than a floating dependency set, which makes a deployment reproducible and an upgrade an explicit piece of work. For a reader deciding whether to look deeper, the practical entry point is skyeye-erp and skyeye-flowable, since those map to the two features the README describes most concretely, the ERP module and the unified approval engine. ## Five visual designers instead of generated CRUD The low-code and zero-code positioning is the part of the product that is not standard enterprise resource planning, and the core advantage section names the mechanism: built-in visual designers for forms, layout, workflow, code and printing. Five designers is a coherent design. A form designer defines the data entry screens, a layout designer arranges the workspace, a workflow designer wires the approval and business process, a code designer covers the parts that need custom logic, and a print template designer produces the documents. The README also describes a business object model with attribute, layout, operation, flow, print template, state and lifecycle management, plus import and export, which is the layer underneath the designers. The feature tree in the README shows the breadth of what ships in the platform configuration. The homepage has a dashboard designer. The default desktop carries system settings such as resource icons, base and platform information, app menu management, database backup and restore, team templates, form components, data templates, background and lock screen image settings, theme settings, menu management, front-end service configuration, administrative divisions, role management, desktop management and code management. Alongside those are organisation management with company, department, position and an org chart, payment channel and payment application management, survey management, file management with file configuration, knowledge review, announcements, light applications, editor material management, and a forum with tag management, sensitive word management and report review. There is a 3D editor and a data dictionary covering platform tenant with strong isolation, plus a smart store module for coupons, store management, store staff allocation and store goods management. The design claim in the README is that no native CRUD code needs to be written and that forms, flows and print templates are built by dragging. Whether that holds for a given business is exactly the question to test with the demo. ## The AI features are two separate things The AI portion of the README is easier to understand once you notice it covers two unrelated areas, and the second one is not about business software at all. The first area is AI inside the platform. There is an AI knowledge base that syncs private data, slices and segments it, supports selective sync, file association and scheduled sync, and backs project-level retrieval and question answering. There is AI chat, which answers project questions using that knowledge base. There is an AI layout designer, described as giving low-code intelligent generation, automatic optimisation and natural language interaction. And there is AI form filling, where a document, image or piece of text is uploaded and the fields are extracted automatically, so a business user can produce a document from material without typing it in. The second area is an automated testing platform, described as a research collaboration and quality platform organised around requirements, versions, modules and defects. It supports interactive requirement splitting, one-sentence bug filing, filing a ticket from a screenshot, and coordination between front-end and back-end test tasks, with the interface organised by business scenario, version linkage, default environments and non-issue determination. The table that follows lists the specific generative tasks: generating a requirement document structure from a sentence, generating smoke test steps from a requirement plus a module API directory, generating a defect from text and a screenshot, generating assertions from a trial run and writing them back into the step, parsing step parameters from an interface definition or context, and analysing a failed execution to produce a bug draft. The distinction matters commercially. The platform features are the ERP product. The testing platform is a separate product line aimed at development teams, and it is the part of this repository most likely to be evaluated on its own terms. ## Where the code, the documentation and the price live The README is unusually explicit about where everything else is, and it is worth following those links before forming a view of the project. The documentation and media live outside GitHub. There is a secondary development documentation site, a product architecture flow chart hosted on a kdocs document, and four Bilibili collections covering secondary development tutorials, operation tutorials, a hands-on zero-code designer session, and more videos to come. The pricing page and the official portal are also on an external host, along with the documentation site. A demo site is linked from the feature overview. The community channel is Bilibili plus a public account, and the README states the author commits to long-term after-sales support. The quick experience section describes a paid trial at 50 yuan a slot, obtained through the contact details given, and it says that one account can experience most of the system. That structure tells you how to evaluate it. The most informative step for a technical decision is not reading the module tree but running the demo, because a zero-code platform either feels fast to a business user in ten minutes or it does not, and no feature list settles that question. Two practical cautions. The external documentation and pricing sites are hosted on an IP-based address rather than a domain, which is a fragile arrangement for a resource a team may need to reference for years. And the open repository has no GitHub releases, so there is no version to pin or diff against; you are tracking a moving branch, in this case company_server, whose last push was on 2026-10-15. ## Conclusion erp-pro fits a developer who wants to study, teach from or extend a Chinese manufacturing ERP with a zero-code design layer, and who is comfortable with a partial open source model where the trunk is public and the complete business source sits behind a membership. It is the wrong choice for an organisation that needs every module under a single permissive licence today, since the README states the open repository does not contain all the code, and it is the wrong choice if you need a supported release cadence, because the repository has no GitHub releases. Before evaluating further, read the pricing and portal pages the README links, confirm the module set you need is in the open trunk rather than the paid source, and check the environment table, since the stack expects JDK 1.8, MySQL 5.7 or later on port 3308, Redis on 6379, Nacos on 8848 and RocketMQ on 9876. ## FAQ ### Does the erp-pro repository contain the full Skyeye source code? No. The README states that the open source repository does not contain all the code, and that the full business source is obtained through a Skyeye membership, which supports study, thesis projects and commercial secondary development. The project is also open to local private deployment. ### What services does Skyeye ERP require to run? The environment table lists JDK 1.8, Nacos 2.3.0 on port 8848 as registry and configuration centre, RocketMQ 4.9.2 on 9876, Redis 5.0 or 6.0 on 6379 and MySQL 5.7 or later on 3308. The technology table adds Spring Cloud Alibaba, Sentinel, XXL-Job, Activiti, Mybatis-Plus and Druid. ### What does the zero-code designer in Skyeye actually cover? The core advantages section names five visual designers: forms, layout, workflow, code and printing. The feature list adds a dashboard designer, business object management for attributes, layout, operations, flow, print templates, state and lifecycle, and organisation, role, menu, payment channel and knowledge management. ### What is the licence of the erp-pro repository? The repository is under the MIT Licence, with the LICENSE file at the root, and the project belongs to the Dromara open source community. The README also states that commercial members who build their own derivative product may remove the original project's copyright and author marks. ## Sources - [Issues](https://github.com/weizhiqiang1995/erp-pro/issues) - [License: MIT](https://github.com/weizhiqiang1995/erp-pro/blob/company_server/LICENSE) - [README](https://github.com/weizhiqiang1995/erp-pro/blob/company_server/README.md) - [weizhiqiang1995/erp-pro on GitHub](https://github.com/weizhiqiang1995/erp-pro) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/weizhiqiang1995-erp-pro