Wukong CRM 15 packages a Chinese CRM system as a Docker Compose install

The repository ships a product, not a library

Wukong CRM 15 is described as a comprehensive customer relationship management system covering the whole business process from lead acquisition to payment collection, and the description says it gives enterprises intelligent and efficient management tools. The repository, though, is small, and the top-level entries tell you what it actually contains: a DB directory, a docker directory, a static directory with an image, a README and a Chinese README, and two licence files.

That layout is the whole proposition. There is no application source tree here, because this release is packaged for deployment rather than for reading. The docker directory holds the compose setup, the DB directory holds the database, and the static directory holds assets. The primary language of the repository is recorded as Shell, which is consistent with a repository whose main job is a startup script and a compose file.

The relationship to the hosted product is stated in the README. This release is aligned with the online SaaS version in terms of interface, display and user experience, and the point of that alignment is that you can log in and see the same thing you would see as a customer of the hosted service, immediately after the download.

The install is a compose file and a database directory

The quick start section of the README is short, which is the point of a one-click release. Before running the installation commands you need Docker and Docker Compose installed, and the README links to the official documentation for both. For macOS and Windows it recommends downloading and installing directly from the Docker official website. For Linux it gives a one line installer script.

With those in place the actual deployment is three commands from the repository root:

cd Wukong_CRM_15
cd docker
docker compose up -d

The detached flag is the significant detail, since it is what makes the install a background operation rather than something that occupies a terminal, and the compose file is the only thing that has to be in the docker directory for the stack to come up.

What the compose file brings up is not described in the README beyond the database being present in the repository, and the sample data mentioned in the feature list is what a new installation will show. The README also points at the Wukong Forum for more detailed installation tutorials, with a link to a specific forum thread, which is where the details the README leaves out are expected to live.

The feature claims, and what the README actually substantiates

The core value section lists six claims, and it is worth separating the ones a reader can check from the ones that are assertions.

The checkable one is the coverage of the business process, from lead generation through to payment collection. That is a scope claim rather than a technical one, and it is the reason the product is a CRM rather than a contacts list. The second is the one-click deployment claim, which the compose file supports. The fourth is global user support through multi-language capabilities and internationalisation, which is consistent with the fact that the README itself exists in English and Chinese, and the fifth is that sample data and supporting documentation are provided so new users can master the operations quickly.

The third and sixth are softer. The intelligent management claim is presented as a consequence of practical digital management capabilities, and the co-construction claim is an invitation to join the open source community group, with a Discord invite and a WeChat group with a QR code for people who prefer it.

None of these are verifiable from the repository, and a reader should treat the feature list as a vendor summary. The parts of the README that carry real information for an adopter are the installation steps, the directory layout and the licence files.

Two README files and two licence files

The first line of the README is a language chooser, offering English and Simplified Chinese, and the two files are named README.md and README_CN.md. The English one links to the edit page for the Chinese file, which suggests the Chinese version is the maintained original and the English one is a translation, and that is the natural reading of a project whose home community is Chinese.

The same pattern appears in the licensing. There is a LICENSE and a LICENSE_CN, and the repository's licence field is recorded as a custom licence that GitHub cannot classify, with the LICENSE file named as the reference. A pair of licence files with a Chinese version alongside an English one is a pattern worth reading closely rather than assuming, because the two documents can differ in wording even when they are nominally the same licence, and the vendor's own sites are the other source of truth.

This is the one place in the repository where a potential adopter should slow down and read the documents rather than the README. A CRM holds customer and contact data, and how you are allowed to use and distribute the software that holds it is a question with commercial consequences that a summary paragraph cannot answer.

The company behind the project, and its scale claims

The README spends a good part of its opening on the vendor, and the claims there are worth reading as claims. Wukong CRM is described as a well recognised open source management solution in China, with a cumulative user count of over 10 million and open source system downloads surpassing 2 million. The stated user base spans design and manufacturing, services, finance and government agencies, and the README lists strategic partnerships with Alibaba, Tencent, OPPO, Aerospace Information and China Central Television.

The company narrative follows: founded around high technology, with technology as its core and after-sales service as its support, guided by a stated spirit of stability and development, pragmatism and innovation, providing professional services to tens of thousands of enterprises domestically and internationally.

None of that is verifiable from a repository, and a reader should notice what the numbers actually measure. Users of the product and downloads of the open source system are different populations, and neither is the same as an active deployment of this particular release. The same applies to the partnerships, which are relationships with the company rather than endorsements of this repository.

The official websites given are wukongcrm.com and wukong.org, and the community forum is bbs.72crm.com, which is where the installation detail and the user discussion live.

Where the community and the documentation actually are

Support for this project is organised around a Discord server, a WeChat group with a QR code in the static directory, and the Wukong Forum. The README gives the Discord invite directly and points at the forum for installation tutorials and community discussions.

The split matters for anyone outside China. The WeChat group is the primary channel for a project of this origin, and WeChat is not reachable for everyone, which is exactly why the Discord invite is given separately at the top of the community section. A reader who cannot use WeChat and does not want to spend time in a Discord server is left with the forum and with the English README.

The forum is the practical source of truth for anything the README summarises rather than states, particularly the installation thread it links, the one titled with a numeric identifier in the URL. The repository itself carries no issue tracker content, no changelog beyond the release tags, and no contributor guide, which is a thin documentation surface for a system with this much configuration surface.

Where this is the wrong choice

The clearest case is a team that needs a hosted service rather than a self-hosted one. This repository exists because the product is also sold as a SaaS version, and the alignment the README describes is with that hosted product. If what you want is a vendor to run it, use the vendor's offering, because the open source edition gives you the deployment and not the support contract.

The second case is an engineering team that needs to integrate the CRM with an existing stack. What is in the repository is a runnable product, not a documented API, a client library or a set of webhooks. Integrating means reading the application, and the application source is not here.

The third is a team with strict data residency or compliance requirements and no appetite for a product whose documentation and community are primarily Chinese, and whose licence comes as a pair of documents with a custom classification. The README is a translation, so the details that matter most for a deployment are likely to be in the Chinese document or the forum.

The fourth is the timing. There is one release tag, v15.0.1 from 2025-10-20, and the last push to the repository was on 2026-07-03, so the packaging is being touched while the version has not moved in about a year. A one-click deployment that is not re-versioned as the underlying product changes is a different proposition from the hosted product it mirrors.

Editorial conclusion

Wukong CRM 15 fits a team that wants a complete CRM product running on its own infrastructure without a sales process, and that is comfortable with a system whose documentation and community are primarily Chinese, since the English README is a translation rather than the source. It is the wrong choice if you need to integrate deeply with an existing stack, because the repository ships the product rather than an API surface, and the wrong choice if you need a hosted multi-tenant service, which the vendor sells separately. Before you install it, check three things: that Docker and Docker Compose are available on the host, since the whole deployment is a compose file, that the licence in the repository permits your use, because it is recorded as a custom licence with a separate Chinese version, and that the sample data directory is what you want in a fresh install rather than your own data. The last push was on 2026-07-03 and the current release is v15.0.1 from 2025-10-20.

Frequently asked questions

Official sources

1. Issues
2. Project website
3. README
4. Releases
5. WuKongOpenSource/Wukong_CRM_15 on GitHub