Stringers
himovo/movo · himovo

Scrapped a homegrown engine after two years and switched to DeepSeek Harness: MOVO's 600 stars were built post by post

What it is An enterprise shell that sits on top of DeepSeek Harness: account permissions, enterprise knowledge base, Skill and MCP management, auditing, and one-command Docker private deployment. The community edition is open source, with a closed-source desktop client and a paid enterprise edition.

Why it took off DSH is the biggest traffic pool in the Chinese dev community this half-year. It was first to claim the "DSH enterprise layer" position, and the product was ported over by a veteran team. They then posted across forums, newsletters and funding write-ups, and kept 10 to 30 stars a day by bumping threads with every release.

CHow you can follow Don't build another DSH enterprise layer. When the next platform-level open-source project blows up, teams that already have something ready should grab the "X enterprise layer / private deployment" position in the first two months, copy its promotion checklist, and focus on forum bumps and releases.

Grade C: the position is already held by MOVO and KnowWork. The engineering scope is the whole platform, and even a funded company that covered every channel only reached 600-plus stars, with the risk of DSH officially adding multi-user support hanging over it. The niche strategy and promotion checklist are worth studying, but copying them wholesale isn't worth it. What's being whispered in small circles
Data (updated daily) · Repo created 2026-09-01 · 756 stars · 7 days +92
GitHub · stars
20040060080010-0910-1910-3011-0911-20756
Data 2026-10-09 → 2026-11-20 (43 days, 41 observations). Points before 10-28 come from deeply / archive backfill, not every day has one

A small team building enterprise AI assistants scrapped the Agent engine it had built in-house for two years and never dared release, and switched to DeepSeek's newly open-sourced DSH. In early September it open-sourced the product and got over 600 stars in 71 days. It never went viral, but it has steadily added 10 to 30 stars a day, backed by a checklist that hit almost every domestic open-source promotion channel. Below: what it is, where the stars came from, who's competing, and whether you should follow suit.

A founder's "we give up" post

On 2026 Sep 20, a user called NobleHawk64 on linux.do posted under the "open source promotion" tag: "Open source | We built an enterprise Agent platform, MOVO, on DeepSeek Harness." He introduced himself as "a MOVO developer and also a founder," who had been building AI assistants for businesses. The most candid part of the post reads as follows:

The project started in 2025, and back then... we still chose to build our own Agent Runtime. ... I myself think the Runtime part in particular wasn't done well, and the future ecosystem isn't something a small team can build, so we kept delaying the release. Then in 8 this year, DeepSeek released Harness, and we felt we were on the right track... so we gave up our homegrown Agent Runtime and swapped the underlying engine for DeepSeek Harness.

He also wrote: "This month we finally open-sourced MOVO, though it hasn't been especially hot."

By November the post had 2,325 views, 46 replies and 107 likes (from the linux.do post API). The replies show who was reading: "Our company has a similar product vision and we're taking it seriously as a reference," "We're doing similar work recently too," "Friendly reminder, don't forget to meet the requirements for China's IT innovation (xinchuang) program." Someone joked "WorkBuddy still gets there in 10 seconds," and the author replied: WorkBuddy is the entry point, while MOVO does the layer behind it (knowledge, permissions, governance and private deployment), "you can think of it as an Agentic Control Plane."

What it is: the "enterprise shell" around DSH

DSH (DeepSeek Harness) is an Agent runtime that DeepSeek open-sourced 2026-08-13. It hit 50k stars within 24 hours and now has 278k, making it one of the fastest-growing repos on GitHub. But on its own it's a single-user tool: a runtime plus a web interface. The DSH discussion board has long had people asking for multi-user support, for example "isolate sessions per user after SSO" and "support a multi-user DSH Server plugin."

MOVO fills exactly that gap. The one-line summary in its README: "DSH runs the Agent; MOVO brings the Agent into enterprise production." Specifically:

  • Accounts, departments and role positions: control who can use which model, which Skill and which document;
  • Enterprise and personal knowledge bases, with RAG and cited sources;
  • Unified management of Skills and MCP tools; external Skills can be installed and then shared inside the company;
  • Audit logs, quotas, and a private Docker deployment of 12 services with a single ./movo up command. Users in China add --mirror cn to pull images from the Beijing mirror, so pulls don't stall.

It deliberately skips drag-and-drop workflows like Dify's. The author's reasoning: "Most enterprise users find configuring those too cumbersome." Processes are written out as Skills, and execution is handed to DSH.

It's open source, but with commercial strings attached. The license is Apache 2.0 plus restrictions: no multi-tenant SaaS, no removing the logo, no rebranding. The browser Agent and the code-writing Agent require a closed-source desktop client. In September 23 they also launched a paid enterprise edition, with fine-grained permissions and "run insights" kept there. The community edition is a funnel for the enterprise edition.

It shipped as a complete product, not a demo, because the team moved the knowledge base, permissions and desktop client it had built over years of enterprise assistant work onto DSH as a whole. It has 142 forks, 22% of its stars, similar to comparable self-hosted platforms (GitHub, 11-11: FastGPT 24.6%, Dify 15.8%, MaxKB 13.9%), which shows people really are pulling it down and deploying it themselves.

Where the stars came from: a promotion checklist

TimelineChannelResults
09-07Posted in the DSH official repo discussions: "We replaced our custom Agent runtime with DeepSeek Harness"2 likes, 3 comments
09-08Tencent Cloud developer community articleUnknown
09-1536 36Kr: "MOVO agent wins Hina Asia & SIG investment"; same day, HelloGitHub and Ruan Yifeng's weekly picksBoth submissions were still not featured as of November
09-17V2EX7 replies
09-20linux.do open-source promotion post; the README carries a linux.do badge per community rules2,325 views; the author bumps the thread with every new release
10-08Posted on NodeLoc, where the author self-reported 226 stars at the time
10-24Submitted to GitHubDailyNot featured
11-06, 11-07Dealroom, aionradar and other English-language sites rewrite 36 funding storiesTiming overlaps with the small peaks on 11-10 and 11-11; causality unverified

In addition, a batch of AI directory sites and aggregators like DeepWiki have listed it on their own, and the README twice asks people to star it ("Got MOVO running? Please click Star"). Searches on X, Hacker News and Reddit turn up nothing.

The star growth peaks match these actions (daily star records): 10-24 submission to GitHubDaily, 10-25 and 10-26 the author replying repeatedly on linux.do, followed by 10-27 with +26 and 10-28 with +35, the highest single day so far; 10-30 release of v0.2.6 gained +29 that day; 11-02 a reply announcing a new version, and 11-03 gained +24. From 09-04 to 10-30 there were 14 releases in total, and it's still committing code almost every day as of November.

Steady growth, but not fast

10-21 was 316 stars, 11-01 was 475,11-11, and 627 is now (live GitHub count 637). Over the last 7 days it added 110; in the 7 days before that, 96. The curve is a straight slope, with no day in the hundreds and no time on trending.

Within the DSH ecosystem this is a modest number: in the same ecosystem, a small plugin like the Bilibili "fish-raising" one passed 900 stars in 20 days off a single video. MOVO has a company, a funding write-up, a whole channel checklist and releases almost daily over two-plus months, and it got 600-plus stars. The reason is simple too: the people who want to build their own enterprise Agent platform are developers and the people at small companies who handle this, a circle that's already narrow. They show up as "serious references," not as casual star-clickers.

Who's competing

ProjectScaleHow it differs from MOVO
DSH core278k starsSingle user only. If the official project adds multi-user and permissions itself, MOVO's position gets eaten directly
knowflow-ai/KnowWork130 star(11-10)10-21 started its repo, calling itself "an enterprise-grade private Agent platform built on DeepSeek Harness": permissions, sandbox, approval and audit all included, under the more permissive Apache-2.0 license. The positioning is nearly identical, 7 weeks late
Tencent Cloud ADP's DSH pluginbig techRuns on Tencent Cloud's knowledge base and Hunyuan models, not a self-hosted open-source stack
Dify / FastGPT / MaxKB161k / 30k / 23k starsLong-established enterprise Agent platform, self-built runtime, doesn't use DSH
Open WebUI / LobeHub158k / 85k starsMulti-user AI workspace, doesn't use DSH
iPolloWork, HarnessRouter7.4k / 4.3k starOne is a workbench that plugs into multiple engines, the other a gateway that connects various harnesses. Neither focuses on the DSH enterprise layer

"Enterprise Agent platform" was already crowded. "DSH-native enterprise layer" was barely taken when MOVO launched in September, and it was the first to put that phrase out there; searches for "DSH enterprise" or "DSH private deployment" tend to surface it. But the spot is easy to copy: KnowWork followed 7 weeks later.

If it were you

Bottom line: C. Building a "DSH enterprise layer" isn't worth it. The spot already has MOVO and KnowWork, the engineering is a whole platform, and even a team with a company, funding and coverage across channels only got 600-plus stars, with DSH's official multi-user work hanging over it. What's worth learning is the positioning and the promotion checklist.

Who it's for: small teams that already have a half-built product (an enterprise assistant, knowledge base, admin permissions) and want to swap the foundation for a hot open-source runtime and relaunch it; or people who need a list of Chinese channels to push their project.

Who it's not for: a solo developer starting from scratch who wants stars from projects like this. Enterprise platforms earn stars slowly, and their users are serious evaluators who don't pour in from one post. For stars, a small, fun plugin that big accounts link to pays off much better.

How to do it: don't compete with MOVO on DSH. When the next platform-level open-source project blows up, spend the first two months claiming the "X enterprise layer / private deployment layer / multi-user edition" phrase, but only if you already have something you can move over. On day one it should be a complete product that runs with one command, not a demo. If you pick a different lane, go after what MOVO left undone: for example, it never added domestic-hardware (xinchuang) adaptation (someone on linux.do flagged this), or you could use a fully permissive license with no closed-source desktop client, to attract developers who don't want to be tied to a commercial edition.

How to get users: copy its list: the platform's official forum, Tencent Cloud developer community, V2EX, linux.do (tag posts as open-source promotion per the rules, add a badge, post screenshots of AI-written content), NodeLoc, plus submit to HelloGitHub, Ruan Yifeng's weekly and GitHubDaily. After that, bump the original thread with every release and answer each question one by one. MOVO's experience: its weekly submissions got no pickup over two months. What actually lined up with star growth was forum bumps and releases.

Deadline: for DSH, the window for "the first enterprise layer" has already closed. For the next platform, the window is roughly the first two months after it takes off, before the official project adds multi-user itself.

Signs I got this wrong: ① MOVO or KnowWork gets a burst of several hundred stars a day before year-end, or DSH officially declines multi-user and leaves the enterprise layer to the community. That would mean the spot is bigger than it looks and worth reassessing. ② KnowWork catches up to MOVO only through its more permissive license, which would mean this category competes on license and openness rather than promotion, leaving room for late entrants. ③ Conversely, if DSH's official team ships its own multi-user version early in 2027, this whole "DSH enterprise layer" category shrinks, and studying the tactics is all that's left.

---

Data and sources: GitHub repo page, README, releases, forks and daily star records (as of 11-11; GitHub live 637 stars); linux.do thread linux.do/t/topic/2925052 (thread API, original post and replies); 36 36Kr 09-15 funding article; HelloGitHub #3703, Ruan Yifeng weekly #11701, GitHubDaily #1280 submission issues; original posts on V2EX, NodeLoc, Tencent Cloud developer community; DSH discussion #5842, #3389, #4884; competitor stars from GitHub (11-10, 11-11). Team background is the author's self-description in posts; the company entity is unverified. Where we wrote "unverified", we found no direct evidence.

GitHub repo ↗

Research notes: competitor table, acquisition evidence, full research report
Competitors
NameWhereLaunchedScaleHow it differs from this one
DeepSeek Harness coreOpen source2026-08-13278k starOnly the runtime and a single-user Web UI. The community keeps asking for multi-user (discussions #3389, #4884). If the official project adds it, MOVO's spot gets eaten.
KnowWork(knowflow-ai)Open source2026-10-21130 starNearly identical positioning, Apache-2.0 license, per-session Docker sandboxes. 7 weeks late and smaller in scale.
Tencent Cloud ADP DSH plugin / Claw modeBig-company features2026-08 to 09Tencent CloudRuns on cloud knowledge base and Hunyuan models, not self-hosted open source
Tencent WorkBuddyBig-company featuresNot verifiedUsers say its market share is high; unverifiedEmployee-facing Agent entry point. MOVO says it's building the governance layer behind that entry point
DifyOpen source2023-04160.9k starLow-code workflows, self-built runtime. MOVO uses Skills instead of workflows and hands execution to DSH
MaxKBOpen source2023-0923.1k star"Open-source enterprise-grade agent platform", started as knowledge-base Q&A, self-built runtime
FastGPTOpen source2023-0230.0k starKnowledge base plus workflows, self-built runtime
Open WebUI / LobeHub / OnyxOpen source2023158k / 84.9k / 33k starMulti-user AI chat workspace with RAG and permissions, but doesn't use the DSH runtime
iPolloWorkOpen source2025-087.4k starAn enterprise Agent workbench that plugs multiple engines (Codex / DSH etc.) into one interface. Local-first, not focused on DSH
HarnessRouterOpen source2026-08-094.3k starA gateway that connects various harnesses in one place. Doesn't do enterprise knowledge or governance
Where users come from
  • Verified Platform event: bound to DeepSeek Harness: title, description, topic (dsh-plugin) and README all tie it to DSH. DSH open-sourced 08-13, now at 278k stars; the dsh.deepseek404.com plugin directory lists it
  • Verified DSH official repo discussions: team member juncheng-zheng posted discussion #5842,2, 09-07 likes and 3 comments
  • Verified Chinese developer forums: Tencent Cloud community 09-08, V2EX 09-17, linux.do 09-20 (2,325 views / 46 replies, author bumped the thread with every release), locdd, NodeLoc 10-08
  • Verified Open-source newsletter / list submissions: HelloGitHub #3703, Ruan Yifeng weekly #11701 (both 09-15), GitHubDaily #1280 (10-24), submitted by the same team member; whether they were accepted is unverified
  • Verified funding PR: 36 36Kr 09-15 "MOVO agent gets investment from HSG Asia SIG"; 11-06, 11-07 Dealroom, aionradar, AI for Business Institute transcribed
  • Verified Aggregator sites / SEO long tail: PyShine, futuretools, nav-ai, JOTO AI, kblip, DeepWiki, GitDiagram
  • Verified README star asks: the README asks for stars twice and carries a linux.do badge
  • Inferred X / HN / Reddit: x-radar shows 90 posts in 0 days; no related HN or Reddit threads

Why himovo/movo (MOVO community edition) took off

In one line: MOVO is a small company that spent years building an enterprise AI assistant (AskBot / Guoran Zhihui, per the team lead's own account). It has launched the "DeepSeek Harness (DSH) enterprise layer": on top of the DSH runtime it adds account and org management, permissions, enterprise knowledge base / RAG, Skill and MCP management, audit, and one-click private deployment via Docker. It scrapped the Agent runtime it had built over two years and switched to DSH, which is open-sourced by 2026-08-13. The community edition went open source in early September. Its stars didn't come organically. They came from a standard Chinese open-source promotion playbook: posting to the DSH official forum, Tencent Cloud Community, 36 Kr financing write-up, HelloGitHub, Ruan Yifeng's weekly, GitHubDaily, V2EX, linux.do and NodeLoc, with nothing skipped. They then kept bumping the linux.do thread with each new version release. 71 days in, it had 627 stars, adding 10 to 30 a day steadily. That's a small number in the DSH ecosystem, where comparable plugins routinely reach thousands to tens of thousands of stars.

1. Data

  • Repo created 2026-09-01, made public around 09-07. An article by 36 09-15 said "about a week after the community edition opened, as of 2026-09-15."
  • Star trend: the author self-reported 226 stars in a NodeLoc post on 10-08; the data card shows 10-21 316 → 11-01 475 → 11-11 627. Last 7 days +110, the 7 days before that +96, last 30 days +380, single-day peak +35 (10-28). It never hit trending, and a repo under 60 days old wouldn't qualify anyway.
  • 142 forks to 147 people, fork/star about 22%. Comparable self-hosted enterprise platforms in our repo database: Dify 15.8%, FastGPT 24.6%, MaxKB 13.9%, RAGFlow 12% (github repo_profile, 2026-11-11). Projects people pull down to deploy themselves usually have higher fork ratios, so 22% isn't unusual. The fork accounts look mostly like real domestic developers (GitHub forks API: 49 in September, 71 in October, 27 in November).
  • We couldn't read the stargazer breakdown because our GitHub API token has no access (GitHub API 403), so we can't check accounts one by one. The star curve shows steady, linear growth with no spike of hundreds in a single day, which looks organic.
  • The small star peaks line up with promotion actions: 10-24 submission to GitHubDaily; 10-25 and 10-26 the author kept replying and bumping on linux.do, followed by 10-27 +26 and 10-28 +35; 10-30 v0.2.6 release day +29; 11-02 a linux.do bump announcing v0.2.6, 11-03 +24; 11-06 and 11-07 English aggregators like Dealroom and aionradar reposted the 36Kr funding article, 36, 11-10 and 11-11 +29 and +27 respectively (the latter pair only overlaps in time; causation unverified).
  • Ships often: 09-04 v0.1.1 to 10-30 v0.2.6, 14 releases on GitHub in total, and still committing code as of 11-11.

2. Competitors

ProductWhereLaunchedScaleHow it differs from MOVO
DeepSeek Harness coreOpen source / big tech2026-08-13278k stars (github repo)It's just a single-user Web UI added to the runtime. The community keeps asking for multi-user: discussion #3389 "per-user session isolation after SSO", #4884 "support multi-user DSH Server plugin". If the official project adds multi-user itself, MOVO's spot gets eaten directly.
KnowWork(knowflow-ai)Open source2026-10-21130 stars, 23 forksNearly identical positioning: "enterprise-grade private Agent platform built on DeepSeek Harness", with RBAC, sandbox, approval, audit and usage stats all covered, and under the more permissive Apache-2.0 license. 7 weeks late, a follower.
Tencent Cloud ADP (DSH plugin + ADP 4.0 Claw mode)Big-company features2026-08 to 09Tencent CloudConnects to DSH using cloud knowledge base, Hunyuan models and container isolation. Not self-hosted open source
Tencent WorkBuddybig techNot verifiedA linux.do user says its "market share is very high"Employee-facing Agent entry point. The MOVO author responded that they're building the governance layer behind the entry point (Agentic Control Plane)
DifyOpen source2023-04160.9k starLow-code workflows plus RAG, self-built runtime. MOVO deliberately skips low-code WorkFlow, describes processes with Skills and hands execution to DSH
MaxKBOpen source2023-0923.1k star"Open-source enterprise-grade agent platform", started as knowledge-base Q&A, self-built runtime
FastGPTOpen source2023-0230.0k starKnowledge base plus workflows, self-built runtime
Open WebUI / LobeHub / OnyxOpen source2023158k / 84.9k / 33k starMulti-user AI chat / workspace with RAG and permissions, but doesn't connect to the DSH runtime
iPolloWorkOpen source2025-087.4k starEnterprise Agent workbench that plugs Codex / DSH and other engines into one interface. Local-first, not focused on DSH
HarnessRouterOpen source2026-08-094.3k stara self-hosted gateway that unifies harnesses from multiple vendors (Apache-2.0). Leans toward routing; no enterprise knowledge or governance layer
nexusdeskOpen source2026-09-23198 starA self-hosted Agent platform built on the Harness idea, focused on customer service
DSH private-deployment vendors like ZhonghaizhiOther2026Not verifiedSells DSH private deployment and custom dev services, no product of its own

Verdict: the "enterprise Agent platform" space is already crowded (Dify, MaxKB, and FastGPT each have tens of thousands of stars). Almost nobody was building a DSH-native enterprise layer when it launched in September. MOVO was first to claim the term, and KnowWork followed in October.

3. Growth tactics (evidence)

  1. Riding the platform hype: DSH 08-13 went open source and hit 24k stars in 50 hours, now at 278k, one of the fastest-growing repos in GitHub history. MOVO's title, description, topic (dsh-plugin), and the first line of its README are all tied to "DeepSeek Harness." The DSH plugin directory site dsh.deepseek404.com also listed it.
  2. DSH official repo discussions: 09-07 team member juncheng-zheng posted in deepseek-ai/deepseek-harness "We replaced our custom Agent runtime with DeepSeek Harness — building MOVO as the enterprise layer", 2 likes and 3 comments, middling response.
  3. Seeding Chinese developer communities:
    • Tencent Cloud Developer Community article (09-08)
    • V2EX (09-17,7 replies)
    • A linux.do "open source promotion" thread (09-20,2,325 views, 46 floors, 107 likes, via the linux.do JSON API). The author, NobleHawk64, posted an announcement reply for each release (09-21, 09-23, 11-02), answered user questions one by one, and kept bumping the thread. The README also carries a linux.do badge, as the linux.do promotion rules require.
    • Reposted by locdd (09-20), NodeLoc (10-08)
  4. Newsletter and list submissions: the same team member, 09-15, submitted to HelloGitHub #3703 and Ruan Yifeng's weekly #11701,10-24 on the same day, then to GitHubDaily #1280. All three are still open. There is no evidence any were included.
  5. Funding PR: 36 published "MOVO Agent Gets Investment from Hinaya Asia SIG" on 09-15 Kr, telling the story of "DSH runs it, MOVO adds the enterprise layer." 11-06 and 11-07 Dealroom, AI for Business Institute, aionradar, and other English sites rewrote it.
  6. Long-tail content sites auto-indexing it: PyShine (10-05), nav-ai, JOTO AI think tank (09-28), futuretools, kblip, DeepWiki, GitDiagram, githubsignals. Most of these are aggregators scraping on their own, and they bring in some search traffic.
  7. Asking for stars in the README: once at the top, and again after the quickstart ("Got MOVO running? Please click Star").
  8. Channels we couldn't find: in the x-radar corpus, searches for "himovo" and "MOVO DeepSeek Harness" returned 90 results over 0 days. HN (Algolia) and Reddit had no related posts. We found nothing on TikTok or Xiaohongshu.

4. Why it took off

  • Timing: DSH is the biggest traffic pool in the Chinese developer scene in the second half of 2026. MOVO was the first to put "DSH enterprise layer" into words, so searching DSH plus enterprise or private deployment easily surfaces it. Tencent Cloud ADP, 36 Kr, and Zhihu discussions of "can DSH go into enterprise production" were effectively doing market education for it.
  • A ready-made product: it isn't a demo built from scratch. The team moved the accumulated work from years of their AskBot enterprise assistant (knowledge base, RAG, org permissions, desktop client) onto DSH as a whole. So it shipped on day one as a full-featured product with 12 services, started with a single ./movo up. It also has a domestic ACR mirror, so users in China can pull images without trouble. The high fork ratio shows people are actually pulling it down and deploying it.
  • Someone is buying distribution at scale: a company team backed by SIG can run paid placements across 36 PR outlets, several weekly newsletters and multiple forums at once, and the author keeps replying and bumping the threads. This is resource-driven distribution, not one developer's single post going viral.
  • Real demand, but not mass demand: most linux.do replies say things like "my company has a similar vision, a serious reference" or "enterprise control is a hard requirement." The people arriving are developers and small companies who want to self-build an enterprise Agent platform. The circle is narrow, so stars grow slowly and linearly without ever spiking.

5. Differentiation

  • DSH-native: it doesn't build its own runtime. It uses DSH's Skills, Tools, MCP, sub-agents, and plugin ecosystem directly, and only builds the control plane on top (identity, knowledge, permissions, audit, quotas, upgrade management). That's the biggest difference from Dify, MaxKB, and FastGPT.
  • Skills instead of low-code workflows: it deliberately skips drag-and-drop workflows, describes processes with Skills, and hands execution to DSH.
  • Open source, with a commercial door left open: the MOVO Community License is Apache 2.0 plus restrictions. It bans multi-tenant SaaS, removing the logo, and OEM rebranding. The browser agent and code agent require the closed-source MOVO Desktop. There is also a paid enterprise edition (fine-grained permissions, operational insights), and the community edition exists to funnel users toward it.

Is the differentiation why it took off? Partly. Being DSH-native gave it DSH's traffic, which is the main reason it got seen. But being DSH-native is not hard to copy: KnowWork built the same thing 7 weeks later under the looser Apache-2.0 license. Its sustained growth owes more to company-backed promotion and frequent releases. Functionally, it has no real lead over the established enterprise platforms.

6. Visibility and copycats

  • Visibility: it's circulating in small circles. The Chinese developer communities linux.do, V2EX, and Tencent Cloud Community have all written about it. 36 Kr ran a funding story, and English aggregators rewrote it. X big accounts, HN, and Reddit have not covered it. Revenue is not public, and neither is commercial pricing.
  • Copycats: knowflow-ai/KnowWork (2026-10-21,130 stars, same positioning, Apache-2.0; there are also promotional posts about it on CSDN). The bigger threat is DSH's official team or Tencent ADP adding multi-user and enterprise governance themselves.

7. Takeaways

  • When a new platform-level open source project blows up, claiming the "enterprise layer / private deployment layer for X" niche within the first two months lets you ride the platform's search and discussion traffic.
  • Repackage the accumulated work of an existing product on a new runtime, and ship a complete product on the open source day, not a demo.
  • The standard playbook for open source promotion in China: cover the platform's official forums, Tencent Cloud Community, V2EX, linux.do (use the open source promotion tag and badge as the rules require), NodeLoc, HelloGitHub, Ruan Yifeng's weekly, and GitHubDaily in one sweep. Then publish a funding PR, and after that, bump the original threads with every release.
  • Community edition plus closed-source desktop plus paid enterprise edition, with the license banning SaaS and rebranding to protect monetization.

8. Uncertain

  • The stargazer breakdown isn't accessible, so we can't verify account quality or where each wave of stars came from. The causes of the 11-10 and 11-11 spikes are unverified.
  • Whether the newsletter submissions (HelloGitHub, Ruan Yifeng, GitHubDaily) were included is unverified. All three issues are still open.
  • We don't know whether the enterprise edition has any paying customers or what it costs. The investment amount from Hinaya Asia SIG was not disclosed.
  • "AskBot / 果然智汇" was matched using 36 Kr36 coverage and the team lead's self-description on linux.do. There's no direct evidence that this is the company behind it.
  • The scale of Tencent WorkBuddy is unverified.

Sources

This article was written by AI from public data and the data we collect daily. Numbers are sourced, and inferences are labeled.