DEV Community: Justin3go

DeepSeek Harness Two Weeks In: Hype, Backlash, and What Shipped

Justin3go — Tue, 25 Aug 2026 14:21:45 +0000

Two weeks after DeepSeek open-sourced DeepSeek Harness (dsh) on 2026-08-13, the story has moved on from launch-day star counts. The last five days brought three shipped releases, a public fight over whether the star count is even trustworthy, and a visible split between developers who think "everything is a plugin" is the right foundation and those who think it's overengineered for daily coding. This is a follow-up to our first-week roundup — same sourced format, this time covering 2026-08-16 through 2026-08-21, a window almost nobody else online has written up in this much detail.

What actually shipped: three releases in five days

Unlike the model side, dsh's own release cadence has been quiet on official channels — every version below was first spotted by third parties, not announced from DeepSeek's account. The npm latest/next tag now points at 0.1.1-rc.1, the first release to leave the 0.1.0 series.

Version	Date	Headline change
`v0.1.0-rc.7`	08-17	Plugins can register their own settings cards; Codex/Claude Code subagent tasks wired into the Job Panel; `Code mode` renamed `PTC mode`
`v0.1.0-rc.8`	08-19	Native image requests for `/goal` and `/plan`; Claude Code/Codex subagents installable as Profile Bundles with non-interactive permission mode; breaking: `settings.plugin.item` slots now require `options.key`
`v0.1.1-rc.1`	08-21	Adds the `DeepSeek-V4-Flash-Vision-Exp` model adapter; fixes a Bubblewrap sandbox bypass via `/proc/<pid>/root`; multiline `ask_user_question` support

That's roughly one release every two days. The docs site changed shape too: any published route now serves a raw Markdown twin at the same path plus .md, backed by a generated llms.txt index — a straightforward optimization for agents that read documentation directly. Separately, docs deploys stopped shipping on every push to master and now only publish from a tagged release, closing a window where unreleased content could appear on the public, unauthenticated docs site before the corresponding npm package. Both changes are visible in the deepseek-harness repository's commit history for the week.

If you're planning to upgrade past rc.6, the breaking options.key change and a reported npm install OOM on low-memory machines are worth knowing about before you run it — see our upgrade guide for the full checklist. The OOM workaround reported in the community is:

NODE_OPTIONS=--max-old-space-size=6144 npx @deepseek-ai/dsh@0.1.1-rc.1 web

The star count nobody fully trusts anymore

GitHub's API puts the repo at 178,538 stars as of August 21, 2026 — the number we use throughout this site. But the loudest Reddit thread of the week wasn't really about dsh's features at all. A 511-vote r/tech_x post claiming "100K+ GitHub stars in just 2 days" drew 119 comments, and most of them argued about whether the growth is real: multiple commenters called it gamed ("90% of these are prob bought/gamed"), one described being pitched a star-selling service at $0.01/star, and only a handful of replies engaged with dsh itself at all (one noted OpenCode V2 is adding dsh-style features; another pointed out third-party harness reasonix already has 30,000+ stars of its own).

That skepticism doesn't mean the growth is fake — it means star count alone is now a weak signal for this repo specifically, and worth treating as attention, not validation, when you see it cited elsewhere.

From launch party to "started getting yelled at"

The clearest summary of the mood shift came from @xmglab on X, who wrote — in a widely shared thread — that dsh had "started getting yelled at" (开始挨骂) in its second week. The core disagreement is the "everything is a plugin" architecture: models, tools, Skills, sessions, the sandbox, and the agent loop are all swappable. One camp reads this as deliberate infrastructure for a future where agents need that flexibility; the other reads it as unnecessary complexity for what is, for most people, just writing code. Star growth hadn't visibly slowed as of 08-21, but the tone of discussion clearly had.

Plugin compatibility complaints fed the same narrative. @VersunPan on X described being a "deepseek harness victim +1," citing inconsistent plugin quality and breaking changes between versions, and recommended waiting for a stable third-party distribution rather than tracking the official repo directly — drawing an explicit comparison to running Linux versus a packaged distro like Ubuntu.

Hacker News tells a quieter version of the same story. The original launch thread sits at 744 points and roughly 299 comments, both essentially unchanged since 08-16 — it has received no new comments in the past week. Every new dsh-related submission since then has been a low-effort Show HN for a small plugin or a competing plugin directory, none scoring above single digits. The conversation simply didn't come back to the front page.

What real users report after actually running it

Two Reddit threads gave the most detailed firsthand accounts. r/DeepSeek's "Deepseek Harness is on whole different level" (242 votes) praised the UI and "code mode" specifically, and reported dsh doesn't stall waiting on user input and catches its own errors mid-task — but flagged subagents as buggy, chalked up to the pre-release stage. r/DeepSeek's "My First Impressions" (99 votes) took the opposite framing: slow, heavy on tokens, and confusing to configure — the author reported that Skills placed under .agents didn't auto-load and the docs didn't explain why.

Praise (sourced)	Complaints (sourced)
UI and "code mode" called out as strong (r/DeepSeek, 242 votes)	Subagents error out often, pre-release quality (r/DeepSeek, 242 votes)
Doesn't stall on user input, self-corrects mid-task (r/DeepSeek, 242 votes)	Slow and token-hungry vs. expectations (r/DeepSeek, 99 votes)
16-hour local run, 20M+ tokens on `llama.cpp`, no failures reported by `u/cviperr33` (r/LocalLLaMA, 101 votes)	WSL instability reported, forced a switch to a third-party harness by `u/Armanlex` (r/LocalLLaMA, 320 votes)
Community already self-authoring plugins within days (r/DeepSeek, 99 votes)	Docs unclear on `.agents` Skill auto-loading (r/DeepSeek, 99 votes)

The "lightweight harness" narrative is gaining ground

The most substantive thread of the week, r/LocalLLaMA's "why is feels better" (101 votes), wasn't really about dsh in isolation — it was about a growing preference among self-hosted-model users for harnesses with small system prompts. The top comment argued that mainstream harnesses like OpenCode, Claude Code, and Codex carry "MASSIVE system prompts" that local models can't afford; dsh and the separate "Pi" harness were repeatedly named as the lean alternatives, while one competing orchestration layer was reported to inject roughly 19,000–20,000 tokens of system prompt before a task even starts. Whether that preference generalizes past the local-inference crowd is unclear, but it's a consistent, sourced pattern this week — and it lines up with why plugin-based, install-what-you-need harnesses are drawing interest in the first place.

The ecosystem by the numbers

GitHub's dsh-plugin topic now spans 10,071 repositories, up roughly 3,967 since 08-16 — most of that growth is unverified noise, not real plugins. The awesome-dsh-plugin list, the curated source FindHarness's plugin index draws from, sits at 1,840 entries; npm's keywords:dsh-plugin search returns 2,273 packages. Two dedicated subreddits, r/DeepSeekHarness and r/DeepSeekHarnessPlugin, appeared this week too — a sign the "how do I find a good plugin" problem is real enough that people are building community infrastructure around it, not just around dsh itself.

Some of the strongest new entries from this window: dsh-ios (in-session iOS simulator/device control, 21 agent tools), dsh-plugin-bridge (cross-preset session migration with a benchmarked handoff), and dsh-poison-guard, a plugin-safety scanner that's part of a growing security-tooling response — see our state of DeepSeek Harness security piece for the fuller picture. On the everyday-cost side, dsh-token-anxiety tracks per-task spend against peak/off-peak API pricing windows, a direct response to the token-cost complaints above.

A few things are worth only a line here because we've covered them elsewhere: a third-party plugin marketplace, dsh-hub.cc, claimed 7,000+ indexed and 3,800+ verified plugins in a GitHub Discussion that drew 91 comments — full landscape in DeepSeek Harness plugin marketplaces. The benchmark-credibility argument from launch week has moved from "is DeepSeek lying" toward a methodology debate about how sensitive agent scores are to prompt and tool-schema choices — see why DeepSeek Harness benchmark scores differ. And DeepSeek-V4-Flash-Vision-Exp, the model behind 0.1.1-rc.1's vision support, is officially announced here — see our vision guide for what it actually unlocks in dsh today.

Should you get on board now?

Tinkerers and early adopters: nothing here should change your plans — dsh is still a developer preview, breaking changes ship every few days, and that's the deal you already signed up for. Pin a version in anything you automate.
Teams considering production use: the two-week data doesn't move the needle toward "yes" yet. Plugin compatibility complaints, subagent errors, and a security fix for a real sandbox bypass in the same release all point toward waiting, exactly as dsh's own README already tells you to.
Plugin developers: this is arguably the best window to build. The options.key breaking change from rc.8 is a one-time cost, ecosystem discovery is still an open problem two new subreddits are trying to solve, and the plugin catalog is growing fast enough that a well-documented, well-scoped plugin can stand out — browse /plugins to see what's already covered before you pick a niche.

FAQ

Is DeepSeek Harness still a developer preview two weeks in?

Yes. Every source we reviewed — the README, the release notes, and direct community reports — treats it as pre-1.0 with expected breaking changes, most recently the options.key requirement in rc.8.

What changed between rc.6 and 0.1.1-rc.1 that I should know before upgrading?

A breaking change to settings.plugin.item slots, a new SQLite storage format (back up session data first), native dependencies that now need npm approve-scripts, and a Bubblewrap sandbox fix. Full steps are in our upgrade guide.

Are the reported star counts (178k, 166k, 136k, 95k) all accurate?

They shouldn't be treated as interchangeable. 178,538 (GitHub API, 08-21) is the only figure we've independently verified; the others are self-reported by different accounts on different days and don't agree with each other, which is exactly what a 511-vote Reddit thread spent most of its comments arguing about.

Is the "everything is a plugin" architecture overkill for everyday coding?

It's genuinely disputed. Some developers see it as the right foundation for a future where models, tools, and sandboxes all need to be swappable; others see it as unnecessary complexity for tasks that don't need it. Neither side has settled the argument as of this week.

Should I trust benchmark numbers people cite for dsh?

Verify against your own workload before relying on any single number, official or independent — the current consensus, discussed in more depth in why DeepSeek Harness benchmark scores differ, is that agent benchmark scores are highly sensitive to the exact harness configuration used to produce them.

Next steps

Missed the first week? Start with DeepSeek Harness, One Week In.
Upgrading past rc.6? Read the upgrade guide before you run it.
Curious what the new vision model actually does? See the vision guide.
Weighing the security fixes and open issues? See state of DeepSeek Harness security.
Browse the full, sourced catalog at /plugins or start from Security & Permissions and Vision, Voice & Multimodal.

Originally published at findharness.com.

10 Best Note-Taking Apps in 2026: Free, Private & Cross-Platform Picks

Justin3go — Sun, 23 Aug 2026 15:41:41 +0000

There is no single “best” note-taking app. A student annotating lecture material, a writer maintaining a Markdown archive, and a team building a shared wiki need three different products. The useful question is not “Which app has the most features?” but “Which app creates the least friction for the way I capture, retrieve, and share information?”

For this guide, we reviewed the official product documentation and current plan pages for ten established note-taking apps. We compared what each product publishes about its platforms, free tier, offline behavior, data portability, collaboration, and privacy as of August 23, 2026. We did not invent a universal score: privacy, simplicity, and team structure are different priorities, so the recommendations below are organized by workflow.

The short answer

Best free all-rounder: Microsoft OneNote
Best for the Apple ecosystem: Apple Notes
Best for quick capture: Google Keep
Best for structured team workspaces: Notion
Best local-first knowledge base: Obsidian
Best open-source Evernote replacement: Joplin
Best privacy-first free sync: Notesnook
Best polished Markdown app for Apple users: Bear
Best low-cost cross-platform upgrade: UpNote
Best minimalist cross-platform app: Simplenote

If none of those descriptions immediately sounds like you, start with OneNote or Apple Notes/Google Keep for a week. Move to Notion only when you need databases or team structure; move to Obsidian, Joplin, or Notesnook when ownership, Markdown, offline access, or encryption becomes the deciding factor.

Best note-taking apps compared

App	Best for	Platforms	Free option	Offline model	Key trade-off
Apple Notes	Apple users who want zero setup	Apple devices; iCloud web access	Included	Native local/offline use with iCloud sync	Weak fit outside Apple hardware
OneNote	Students, handwriting, mixed media	Windows, macOS, web, iOS, Android	Yes	Desktop and mobile apps	Notebook structure can feel heavy for plain text
Google Keep	Fast notes, lists, reminders	Web, Android, iOS	Yes	Strongest on mobile; web depends on browser state	Too shallow for large knowledge bases
Notion	Team docs, databases, project knowledge	Web, Windows, macOS, iOS, Android	Yes	Individual pages can be downloaded in apps	More structure and setup than a simple notes app
Obsidian	Local Markdown and connected knowledge	Windows, macOS, Linux, iOS, Android	Core app is free	Local-first	Collaboration and first-party sync are optional paid services
Joplin	Open-source, offline-first notes	Windows, macOS, Linux, iOS, Android	App is free	Offline-first	More configuration and a less polished UI than mainstream rivals
Notesnook	Encrypted notes on every major platform	Web, Windows, macOS, Linux, iOS, Android	Unlimited notes/devices	Local apps work offline	Smaller ecosystem than Notion or Obsidian
Bear	Focused Markdown writing on Apple devices	macOS, iPhone, iPad	Local free tier	Native offline app	Sync and advanced export require Pro; Apple-only
UpNote	Affordable, polished cross-platform notes	Windows, macOS, Linux, iOS, Android	Up to 50 notes	Available offline	Free tier is only a trial-sized library
Simplenote	Plain text with effortless sync	Web, Windows, macOS, Linux, iOS, Android	Completely free	Native apps	Few rich-media and advanced organization features

1. Microsoft OneNote — best free all-rounder

OneNote remains the safest default when you need a real notebook rather than a stack of short text files. Its freeform canvas accepts typed notes, handwriting, drawings, images, files, audio, and clipped web content. Sections and pages map naturally to classes, clients, or projects, and shared notebooks work well for households and small teams already using Microsoft accounts.

The strongest reason to choose OneNote is breadth without an immediate subscription. The OneNote Web Clipper can save articles, page regions, PDFs, and video context directly into a notebook, which makes the app particularly useful for research-heavy work.

Choose OneNote if: you mix handwriting, screenshots, PDFs, and typed notes; you use Windows; or you want a generous free starting point.

Skip it if: you want plain Markdown files, a minimal interface, or a local folder that can be edited by other tools.

2. Apple Notes — best for the Apple ecosystem

Apple Notes wins by being present at the exact moment an Apple user needs it. It opens instantly, syncs through iCloud, scans documents, accepts handwriting and attachments, and now offers enough organization for serious everyday use. Tags and Smart Folders can filter notes by tag, date, checklist state, attachment, mention, and other criteria without forcing every note into a rigid folder tree.

It is also a capable lightweight collaboration tool. Apple’s current guide confirms that users can share notes or folders and collaborate in real time, with edit or view-only permissions. That covers shopping lists, trip planning, family documents, and small project notes without introducing another account or app.

Choose Apple Notes if: your daily devices are an iPhone, iPad, and Mac, and you value capture speed over customization.

Skip it if: Windows, Android, Markdown portability, or a plugin ecosystem matters to you.

3. Google Keep — best for quick capture

Google Keep is closer to a digital wall of sticky notes than a traditional notebook. That is its advantage. Color, labels, pinned notes, checklists, reminders, images, drawings, and voice capture make it excellent for ideas that need to be recorded now and organized lightly later.

Sharing is deliberately simple: Google’s help page says collaborators can edit the text, lists, images, drawings, and audio recordings inside a shared note. For groceries, recurring checklists, content ideas, and short meeting follow-ups, that is often enough.

Choose Google Keep if: you want the fastest path from thought to searchable note, especially on Android or alongside Google services.

Skip it if: you need long-form writing, nested structure, databases, reliable bulk export, or a durable research archive.

4. Notion — best for structured team workspaces

Notion is the best choice here when notes need to become a system. Pages can contain databases, project views, embeds, templates, comments, and permissions, so a collection of notes can evolve into a team wiki, editorial calendar, CRM, or product roadmap without leaving the same workspace.

Its main weakness used to be offline access. In 2026, Notion supports offline pages on all plans in its desktop and mobile apps, although pages must be downloaded individually on the free plan and database downloads have practical limits. Notion also provides workspace export to HTML, Markdown, and CSV, which is valuable even though a complex workspace will not round-trip perfectly into another tool.

Choose Notion if: your notes connect to projects, people, statuses, templates, and shared team processes.

Skip it if: you mainly want instant personal notes, complete local ownership, or a folder of clean Markdown files.

5. Obsidian — best local-first knowledge base

Obsidian stores notes as Markdown files in a local folder, then adds backlinks, graph views, properties, search, canvases, and a large plugin ecosystem on top. That makes it unusually durable: your core notes remain readable even if you stop using the app, and other editors or scripts can work with the same files.

The core app is free for personal, commercial, nonprofit, and educational use. Your files stay on your device; optional Obsidian Sync adds end-to-end encrypted cross-device sync, version history, and shared vaults. The official pricing page separates those services clearly from the free local app.

Choose Obsidian if: you care about local files, Markdown, long-term ownership, backlinks, and extensibility.

Skip it if: you want effortless real-time team editing, a fully managed web workspace, or zero configuration.

6. Joplin — best open-source Evernote replacement

Joplin is a free, open-source, offline-first notes and to-do app. It supports Markdown, notebooks, tags, attachments, full-text search, plugins, themes, and a web clipper. Its official overview also documents import from Evernote and plain Markdown, making it one of the most practical exits from a proprietary archive.

Sync is flexible: you can use Dropbox, OneDrive, Nextcloud, Joplin Cloud, or other supported targets. Joplin supports end-to-end encryption on all applications, but you must enable and configure it correctly. That flexibility is powerful, though it introduces more setup than signing into a mainstream cloud notes app.

Choose Joplin if: you want an open-source, cross-platform Evernote-style notebook with control over sync.

Skip it if: visual polish, seamless collaboration, or a no-configuration experience is your first priority.

7. Notesnook — best privacy-first free sync

Notesnook makes the strongest privacy case among the cloud-synced apps in this list. Its free plan currently includes unlimited notes on unlimited devices with end-to-end encryption enabled by default. The client and server are open source under GPLv3, and the product supports Windows, macOS, Linux, Android, iOS, and the web.

The official download page says desktop and mobile notes remain readable and editable offline, then sync after reconnecting. Its pricing page also promises export on every plan and explains that dropping from a paid plan does not lock or delete your notes.

Choose Notesnook if: encrypted sync, open source, cross-platform access, and a genuinely usable free tier matter more than integrations.

Skip it if: you need mature team databases, a huge plugin marketplace, or the broadest third-party automation ecosystem.

8. Bear — best polished Markdown app for Apple users

Bear combines a calm native interface with Markdown, nested tags, rich attachments, document scanning, and strong export options. It feels lighter than Notion and more guided than Obsidian, which is exactly the appeal for writers who want structure without building a personal knowledge-management system from scratch.

The free version keeps notes locally and supports basic export. Bear Pro adds iCloud sync, encryption for individual notes, OCR search, more themes, and additional export formats. Bear’s official product and pricing page currently lists Mac, iPhone, and iPad only.

Choose Bear if: you write on Apple devices and care about typography, speed, Markdown, and flexible tags.

Skip it if: you use Windows or Android, need free multi-device sync, or collaborate in shared workspaces.

9. UpNote — best low-cost cross-platform upgrade

UpNote occupies the useful middle ground between a basic notes app and an endlessly configurable knowledge base. It offers notebooks, nested organization, backlinks, focus mode, templates, offline access, and apps for Windows, macOS, Linux, iOS, and Android.

The free plan is limited to 50 notes, so it is best treated as a real product trial rather than a permanent library. The official pricing page currently lists Premium at $1.99 per month or $39.99 for lifetime access, with unlimited notes, attachments, tables, note locking, and Markdown/PDF/HTML export. Prices can vary by region and store.

Choose UpNote if: you want a polished cross-platform app and prefer a low-cost lifetime option to another large subscription.

Skip it if: you require open source, end-to-end encrypted sync, real-time team collaboration, or an unlimited free plan.

10. Simplenote — best minimalist cross-platform app

Simplenote is the antidote to feature-heavy note systems. It provides plain notes, tags, search, Markdown, version history, sharing, and automatic sync across web, Windows, macOS, Linux, iOS, and Android. According to its official site, the apps, backups, sync, and sharing are all free.

The constraint is the product: Simplenote is built for text, not elaborate documents. You do not get Notion databases, OneNote’s canvas, or attachment-heavy research notebooks. In return, there is very little to configure and very little that can distract you from writing.

Choose Simplenote if: you want free, fast, searchable text notes everywhere.

Skip it if: images, PDFs, handwriting, tables, databases, or advanced privacy controls are central to your workflow.

How to choose the right notes app

Choose by where your data should live

Pick Obsidian when local Markdown files are the requirement, not a bonus.
Pick Joplin when you want open source plus control over the sync target.
Pick Notesnook when you want cloud convenience with encryption enabled by default.
Pick Notion, OneNote, Apple Notes, or Google Keep when managed cloud sync and easy sharing matter more than file-level control.

Choose by the shape of your notes

Short reminders and lists: Google Keep or Simplenote.
Handwriting, PDFs, and mixed media: OneNote or Apple Notes.
Long-form Markdown and connected ideas: Obsidian, Bear, or Joplin.
Databases, wikis, and team processes: Notion.
A polished conventional notebook across many platforms: UpNote.

Choose by exit cost, not just entry price

A free plan is not automatically a good long-term deal. Before importing years of notes, create a small test notebook and export it. Check whether headings, links, attachments, tags, and folders survive in a format you can actually reuse. Obsidian’s plain Markdown starts with low exit cost; Notion and Joplin offer documented exports; Bear and UpNote reserve some advanced export features for paid tiers.

Our recommendation for most people

Start with the app already closest to your workflow:

Apple-only personal use: Apple Notes.
Windows, students, or mixed-media notebooks: OneNote.
A shared team knowledge system: Notion.
A personal knowledge base you want to own for years: Obsidian.
Private cross-platform notes without paying immediately: Notesnook.

Do not migrate because another app has a prettier graph or a longer feature list. Migrate when your current app fails one of four tests: capture is slow, retrieval is unreliable, sharing is awkward, or you cannot export your own work in a usable format.

Turbo0 tracks a much broader set of established and emerging tools in the Note-taking category, including AI meeting notes, transcription utilities, study tools, and local-first apps. Browse the category when your requirement is more specific than a general-purpose notes app—or submit your own product if it fills a gap this comparison missed.

Methodology and update policy

This comparison uses public information from each product’s official site, documentation, support pages, and current pricing pages, checked on August 23, 2026. “Best” means the strongest fit for the stated workflow, not an objective quality ranking. Pricing, free-plan limits, offline behavior, and platform support can change; follow the linked official source before making a purchase or migrating a large archive.

Originally published at turbo0.com.

How DeepSeek Harness Hits 99% Cache Hit Rates (Explained)

Justin3go — Sat, 22 Aug 2026 14:13:20 +0000

DeepSeek Harness (dsh) isn't cheap because of a pricing trick — it's cheap because two things stack: DeepSeek's own API-level context caching (a prefix-matched KV cache, billed at a fraction of normal input price on a hit) and dsh's session architecture, which happens to be almost perfectly shaped to feed that cache. Neither one alone explains the numbers Reddit keeps posting; together they explain why agent sessions in particular — not chatbots, not one-off completions — are where the savings compound the hardest.

What DeepSeek context caching actually is

Every request to an LLM API starts with a prefill step: the model processes the entire input prompt (system prompt, conversation history, tool schemas, everything) before it generates a single output token. Prefill is compute-heavy, and for a long-running agent session the same tokens — the system prompt, the first 40 messages of history — get reprocessed on every single turn, because each new turn just appends one more user message or tool result to an ever-growing prompt.

DeepSeek's context caching (officially documented at api-docs.deepseek.com/guides/kv_cache) exploits exactly that redundancy. On each request, DeepSeek's API checks how much of the new prompt's prefix — a byte-for-byte match starting from token zero — was already computed and cached from a previous request. Whatever matches is billed at the cached input price instead of the full input price; only the new tail of the prompt (and the output) get billed and computed at normal rates. There's no configuration flag to turn this on — it's automatic, and it's a property of the API, not of dsh itself.

The catch is the word "prefix." Cache hits require the exact same tokens in the exact same order from the start of the prompt. Insert, remove, or reorder anything upstream of a given point, and everything after that point is a cache miss.

Why dsh agent sessions hit 97-99%

That "exact same prefix" requirement is where dsh's architecture becomes relevant, not incidental. A multi-turn agent session is naturally an append-only prefix: each turn just adds the model's previous response, the tool calls it made, and the new user input onto the end of the existing conversation. If nothing upstream changes, every single previous turn is a guaranteed cache hit, and only the newly appended tail needs fresh compute.

dsh's session storage backs this up structurally rather than by accident: sessions are event-sourced logs (see the session-persistence-jsonl / session-persistence-sqlite packages) where history is immutable once written, and the system prompt for a given session stays fixed unless you deliberately change agent mode. That combination — an unchanging system prompt plus a strictly append-only history — is close to the ideal input shape for prefix caching.

The numbers on Reddit back this up, with the usual caveats that they're self-reported and unverified:

On the dsh launch thread (r/LocalLLaMA), several commenters reported roughly 97% cache hit rates running DeepSeek through harness setups in the dsh family — one via the third-party harness reasonix rather than dsh itself — with one person noting a full one-shot SPA build cost them $0.06 total. (reddit.com/r/LocalLLaMA/comments/1vnb66j)
A separate long-session user on r/DeepSeek reported cache hits climbing to 99% after roughly 61.5 million cumulative input tokens in a single dsh session — a large enough sample that the number is unlikely to be a fluke, though it's still one person's report, not an audited benchmark. (reddit.com/r/DeepSeek/comments/1vnpt5n)
On another r/DeepSeek thread, "100% cache hit" turned into a running joke ("you thought your message was unique, but someone already sent it" / "DeepSeek invented time travel") before a detailed community explainer walked through prefill and prefix matching and linked DeepSeek's own KV cache docs — a sign that plenty of users notice the effect long before they understand the mechanism. (reddit.com/r/DeepSeek/comments/1vnfz2l)

None of this is dsh doing anything special to the API — it's dsh not accidentally sabotaging a caching mechanism that rewards long, stable, append-only prompts.

What breaks the cache

The flip side is that anything which mutates the prompt's shared prefix — instead of appending past its end — forces a full or partial re-prefill on the next request. In practice:

Action	Effect on cache
Sending a new message in the same session	No effect — this is the append-only case the cache is built for
Switching agent mode (e.g. `minimal` ↔ standard ↔ PTC)	Changes the system prompt and tool schemas, invalidating the cached prefix from that point
Changing model or provider mid-session	Cache is per-model; switching providers starts fresh
A plugin injecting dynamic content into the prompt (timestamps, live counters, randomized ordering)	Breaks the exact-match requirement on every turn where it fires, even if the rest of history is unchanged
Forking a session	The shared history up to the fork point stays byte-identical, so it should still hit cache normally; divergence only affects turns after the fork
Whether tool-call outputs count toward the cached prefix	Genuinely unclear — DeepSeek's docs don't spell this out explicitly, and it's an open question in community threads rather than a documented behavior; treat it as unverified either way

The practical takeaway is the one already circulating informally: keep your system prompt and plugin set stable for the life of a session, and avoid anything that injects non-deterministic content into early context.

How to check your own cache hit rate

You don't need to guess — dsh's Web UI surfaces the cache hit rate per session directly. It's been there for a while, but the display itself had a rough edge: earlier builds rounded 99.x% figures in a way that lost precision at exactly the range where most long agent sessions land. The v0.1.1-rc.1 release (2026-08-21) specifically improved the display precision for 99.x% cache hit rates, alongside a Bubblewrap sandbox fix and the new DeepSeek-V4-Flash-Vision-Exp model adapter. If you're still on an older 0.1.0-rc.x build, see the upgrade guide for what else changed before you bump the version.

A practical checklist for cutting costs

None of these are official DeepSeek recommendations — they're patterns reported by the community, credited where the source is known:

Watch for time-of-day pricing swings. The author of the dsh-token-anxiety plugin — which tracks per-task cost against peak/valley pricing windows — reported on Reddit that "peak vs valley hours make a HUGE difference" for effective cost. This is a community-reported observation, not something we've independently verified against DeepSeek's pricing page. (reddit.com/r/DeepSeek/comments/1vph1ig)
Reserve Pro for hard problems, use Flash for everything else. Same source: route routine tasks to a cheaper/faster model tier and save the larger model for problems that actually need it.
Go easy on subagents. The same Reddit post specifically warns not to spawn subagents "unless you can strictly control" them — each subagent typically starts its own context, which means its own prefill, undercutting the parent session's accumulated cache advantage. See DeepSeek Harness Subagents for how delegation works before you lean on it heavily.
Keep system prompts and installed plugins lean. A separate, well-upvoted r/LocalLLaMA thread makes the case at length: harnesses with bloated system prompts pay a bigger prefill cost on every single turn, cache or no cache, and a leaner plugin set means less to invalidate when something does change. Browse Usage & Billing plugins if cost tracking itself is what you're after, or the full plugin catalog for everything else.

You can install the token-tracking plugin the same way as any other:

dsh plugin --profile web add github:mov-eax-eax/dsh-token-anxiety

Is dsh free because of this?

Caching lowers your effective per-token cost dramatically, but it doesn't make dsh free — you still need API credits from whichever provider you're using, and dsh itself is free/MIT-licensed software regardless of caching. See Is DeepSeek Harness Free? for the full breakdown, and Which Harness Runs DeepSeek V4 Best? if you're comparing total cost across harnesses rather than just cache behavior within dsh.

FAQ

What is DeepSeek context caching, in one sentence?

It's DeepSeek's API automatically reusing the computed KV cache for any prefix of your prompt that exactly matches a previous request, billing the matched portion at a lower cached-input rate.

Why do dsh sessions specifically get such high hit rates?

Because dsh sessions are append-only event logs with a stable system prompt per mode — the conversation only ever grows at the end, which is the exact shape prefix caching rewards.

Does the 97-99% number apply to every dsh session?

No — it's what's been self-reported for long, stable sessions with a consistent agent mode and plugin set. A session that frequently switches modes, models, or injects dynamic content into early context will see lower hit rates.

Do tool call outputs count toward the cached prefix?

It's not clearly documented either way, and the community hasn't settled it — treat any specific claim about tool-output caching as unverified until DeepSeek's docs address it directly.

Do I need to configure anything to get caching?

No — context caching is automatic on DeepSeek's API side. The only thing you control is whether your prompt shape (system prompt, plugin set, mode) stays stable enough to keep hitting it.

Next steps

Check your own cache hit rate in the dsh Web UI after upgrading to v0.1.1-rc.1 for the improved 99.x% display precision. If subagents are part of your workflow, read DeepSeek Harness Subagents before you scale up delegation and dilute your cache. For a broader cost comparison across harnesses (not just cache mechanics), see Which Harness Runs DeepSeek V4 Best?, and browse cost-tracking plugins under Usage & Billing or the full plugin catalog.

Originally published at findharness.com.

DeepSeek Harness vs Claude Code: Architecture, Plugins, MCP

Justin3go — Fri, 21 Aug 2026 03:01:08 +0000

DeepSeek Harness (dsh) is an MIT-licensed, open-source agent harness built around a single extension mechanism — everything is a Cordis plugin. Claude Code is Anthropic's proprietary coding agent, which separates extensions into skills, commands, hooks, and MCP servers, and ships an official plugin marketplace. They aren't purely rivals, either: dsh can delegate work to Claude Code as a subagent, and it can reuse a Claude Code hooks.json file directly.

This is the fact-based comparison — no fabricated benchmark numbers, no invented pricing — pulled from dsh's own documentation and package structure, and from what's publicly known about Claude Code. That combination of full open licensing, comparable MCP tool naming, and a native subagent bridge into Claude Code itself is why dsh gets framed as an open-source Claude Code alternative rather than just another coding agent; the facts below are what actually back that framing up.

License and architecture, side by side

Dimension	DeepSeek Harness (dsh)	Claude Code
License	MIT, fully open source	Proprietary CLI distributed by Anthropic
Core architecture	Cordis plugin framework — everything (tools, commands, skills, hooks, MCP bridges, model adapters) is the same kind of plugin	Separate mechanisms for skills (`SKILL.md`), commands, hooks (`hooks.json`), and MCP config, plus an official plugin marketplace
Primary interface	Local Web UI (`npx @deepseek-ai/dsh web`, `127.0.0.1:3080`) and a headless CLI mode	Terminal-first CLI, with IDE extensions
Version status	Developer preview (npm `0.1.0-rc.6` as of this writing), no SemVer promise, no GitHub Releases	Established, publicly documented product

The architectural split is the headline difference. In dsh, a hook, a Skill, an MCP server bridge, and a tool are all just plugins registered against the same Cordis Context — there's no separate manifest format for each. Claude Code instead treats skills, commands, hooks, and MCP servers as distinct extension types, each with its own file format, and adds a marketplace layer on top (confirmed by a CLAUDE_CODE_DISABLE_OFFICIAL_MARKETPLACE_AUTOINSTALL test flag that shows up in dsh's own Claude Code subagent test suite — a small but concrete signal that the marketplace and its auto-install behavior are real).

MCP: same tool-naming shape, narrower scope in dsh

Both tools bridge Model Context Protocol servers, and dsh's docs go out of their way to point out the resemblance: dsh names bridged tools mcp__<serverName>__<rawName> — the same server-qualified shape Claude Code and Codex use. If you've configured MCP servers for Claude Code before, the mental model transfers directly.

Where they diverge is scope. dsh's @deepseek-ai/dsh-mcp-client explicitly bridges only MCP Tools — Resources and Prompts are documented as deferred, with no harness-side consumer yet. Claude Code's MCP client is documented to also surface Resources (as @-mentions) and Prompts (as slash commands) in addition to Tools. If an MCP server you rely on leans on Resources or Prompts rather than Tools, that's a real functional gap to check before switching.

A dsh MCP server config looks like this (stdio transport, one plugin instance per server):

- id: mcp-github
  name: '@deepseek-ai/dsh-mcp-client'
  config:
    serverName: github
    transport: stdio
    command: npx
    args: ['-y', '@modelcontextprotocol/server-github']
    env:
      GITHUB_TOKEN: !!js process.env.GITHUB_TOKEN

Editing this line triggers hot-reload — dsh disconnects and reconnects the server without restarting the process. See our MCP setup guide for streamable-http config, reconnection behavior, and timeout limits.

Hooks: dsh can run your existing Claude Code hooks.json

This is one of the more surprising facts in the comparison: dsh ships an official bridge package, dsh-hooks-claude-code, that translates an existing Claude Code hooks.json file into dsh's own extension-point listeners (agent/session-start, tools/pre-execute, and so on). If your team already invested in Claude Code hook scripts, you don't necessarily have to rewrite them to try dsh. A parallel dsh-hooks-codex bridge exists for Codex CLI hooks. See Hooks and slash commands in DeepSeek Harness for how the bridge maps events.

Subagents: dsh can delegate to Claude Code itself

The single most interesting fact for anyone framing this as "which one wins" is that dsh's subagent system natively supports Claude Code as one of its subagent providers (dsh-subagent-claude-code, which drives Claude Code through its official Agent SDK), alongside a Codex provider, an Agent Client Protocol provider, and in-process providers. Subagents can be one-shot or continuable, and one-shot delegation supports outputSchema, depthLimit, toolFilter, and persona — a provider must explicitly declare support for each; unsupported requests fail loudly rather than degrading silently.

Practically, that means dsh isn't strictly a Claude Code alternative — it can be an orchestration layer that calls Claude Code as one of its execution backends, alongside DeepSeek's own models and other subagent types. See DeepSeek Harness subagents for the full provider table.

Skills: not directly interchangeable

dsh's Skill system (ctx.skills, a provider registry merging filesystem and built-in sources) is architecturally its own thing — it isn't the same format as Claude Code's SKILL.md directory convention. A community Discussion (#88) specifically asked whether dsh could reuse "traditional" Skills, and the docs don't currently document direct compatibility. Some community plugins bridge this gap by design — for example, dsh-skillport discovers existing SKILL.md libraries across Claude Code, Codex, Cursor, and Gemini paths and loads them into dsh. That's a community workaround, not an official compatibility guarantee.

Models, sandboxing, and maturity

Model providers: dsh ships native DeepSeek support plus a built-in directory for Anthropic, OpenAI, Bedrock, Vertex, Azure, and Codex-native auth, on top of any OpenAI-compatible custom endpoint. Claude Code is built around Anthropic's Claude models, with publicly documented support for accessing them via Amazon Bedrock and Google Vertex AI as well.
Sandboxing: dsh has three explicit sandbox tiers (read-only, workspace-write, danger-full-access) with platform backends — bwrap/Landlock on Linux, Seatbelt on macOS, an ACL-restricted token approach on Windows — plus an E2B cloud sandbox option. Claude Code uses its own approval-based permission model with configurable auto-approve behavior; the specifics of its sandboxing internals aren't something we're independently verifying here.
Maturity: dsh is explicitly a developer preview — no SemVer commitment, no GitHub Releases page, GitHub Issues disabled in favor of Discussions. Claude Code is a shipping, documented Anthropic product.

Which one should you use?

If you're...	Consider
Already deep in Claude Code, with working `hooks.json` scripts and Claude Code subagent workflows	Try dsh's `dsh-hooks-claude-code` bridge and `dsh-subagent-claude-code` provider — you may not need to choose, since dsh can call Claude Code for you
Building an orchestration layer that needs to call multiple coding-agent backends (Claude Code, Codex, in-process) from one place	dsh's subagent provider registry is designed exactly for this
Want a single first-party product with an official marketplace and one consistent extension format	Claude Code's separated skills/commands/hooks/MCP model is more opinionated and arguably easier to reason about per extension type
Want the extension surface itself to be hackable — write a plugin once, and it can be a tool, a hook listener, or an MCP bridge	dsh's "everything is a plugin" Cordis architecture is the more flexible base to build on
Need a stable, versioned tool for production workflows today	Weigh dsh's developer-preview status (breaking changes expected, no SemVer) carefully against Claude Code's shipping status

Neither replaces the other outright for every workload — the subagent bridge specifically means you can use both at once.

FAQ

Is DeepSeek Harness open source and Claude Code isn't?

Yes. dsh is MIT-licensed and its source is on GitHub. Claude Code is distributed by Anthropic as a proprietary CLI tool.

Can dsh actually run my Claude Code hooks without rewriting them?

The dsh-hooks-claude-code bridge package is designed exactly for this — it translates an existing Claude Code hooks.json into dsh's own extension-point listeners. We haven't independently tested every hook type against it, so verify your specific hooks after installing.

Does dsh support the same MCP servers I already use with Claude Code?

In most cases, yes, if your MCP server exposes Tools — the naming shape (mcp__<serverName>__<rawName>) is the same. If the server relies on MCP Resources or Prompts, dsh's client doesn't bridge those yet.

Can I use Claude Code and dsh together instead of choosing one?

Yes — that's what the dsh-subagent-claude-code provider is for. dsh can delegate a task to Claude Code (via its official Agent SDK) as one of several subagent backends.

Which one has more plugins?

FindHarness currently tracks hundreds of dsh plugins across twelve categories. Claude Code has an official marketplace with its own plugin catalog; we don't track a comparable count for it here.

Next steps

New to dsh entirely? Start with What Is DeepSeek Harness?
Planning an actual migration? Read Migrating from Claude Code to DeepSeek Harness
Want the MCP bridge details in full? See How to Use MCP Servers with DeepSeek Harness
Curious about the Codex side of this same comparison? Read DeepSeek Harness vs OpenAI Codex CLI
Browse the workflow-automation category for multi-agent orchestration plugins like dsh-agent-teams

Originally published at findharness.com.

Where Do Indie Tools Actually Get Their Traffic? Direct, Referral & the Rise of AI

Justin3go — Tue, 18 Aug 2026 15:02:07 +0000

Every listing in the Turbo0 directory that carries Similarweb data also carries a traffic-source breakdown — the split between direct visits, search, social, referral links, email, and paid traffic. In theory, that breakdown should let us answer a simple question: do indie tools grow mostly through search, social buzz, referral links, or people just typing the URL back in?

In practice, our data source only answers part of that question honestly, and we'd rather tell you which part than pretend otherwise.

The data problem, up front

Before any chart: in our Similarweb dataset, the search, social, and paidReferrals fields are zero for every single product that has traffic-source data at all — roughly 3,435 items checked, max observed value 0 across all three fields. That is not a finding that indie tools get no search or social traffic. It is a gap in what our current data tier reports. Treating it as "no product is SEO-driven" would be wrong and we're not going to write that sentence.

What does carry real, nonzero values in this dataset is direct, referrals, and mail. So this article sticks to those three, plus a cross-reference to AI-referral traffic from a separate Similarweb AI-platform feed that isn't affected by the same gap. Everything below is scoped to what we can actually verify.

Within Turbo0's indie pool (5,960 alive listings, capped at 5,000,000 monthly visits so giants don't skew the picture), 3,295 products currently have Similarweb visit-history data. Of those, 454 have a nonzero share in at least one of the four dominance-eligible channels (direct, search, social, referrals) — and because search and social are structurally empty, that 454 splits into exactly two groups: 429 direct-dominant and 25 referrals-dominant products.

TL;DR:

Direct-dominant products (429 of them) have a 30.1% high-growth rate — about 3x the 10.1% baseline across the whole measurable indie pool — and a much higher traffic floor (median 73,559 visits/month vs. 29,821 for referral-dominant products).
Referral-dominant products (only 25) post an even higher high-growth share (36%), but their median growth is actually negative (-16.1%) — a small, volatile group that swings between spikes and drop-offs rather than a stable trend.
AI-referral traffic (ChatGPT, Gemini, Claude, Perplexity sending visits) already touches about 5% of the measurable indie pool — a real, distinct third channel worth watching, covered in depth in our AI referral traffic report.

Direct traffic is the strongest signal we can measure

"Direct" means someone typed the URL, used a bookmark, or opened a saved link — no referring page, no search engine, no social platform in between. It's the traffic Similarweb can't attribute to a channel, which sounds like a weakness until you see what correlates with it.

Median monthly visits and high-growth share for the 429 direct-dominant vs. 25 referrals-dominant products in Turbo0's measurable indie pool.

Direct-dominant products aren't just more numerous — they sit on a higher traffic floor (median 73,559 visits vs. 29,821) and grow at nearly 3x the base rate of the general indie pool (30.1% vs. 10.1% high-growth share). We want to be precise about what that is and isn't: it's a correlation inside a snapshot, not proof that direct traffic causes growth. The more plausible read is that direct dominance is a symptom of something else — a memorable name, a product people bookmark and reopen, a workflow tool used daily rather than discovered once. Growth and "people keep coming back on their own" tend to travel together.

Where direct-dominant products cluster

Category tags of the 429 direct-dominant products (products can carry multiple tags, so counts exceed 429).

Platforms (79), Others (73), Image Editing (69), Image Resources (62), and Video Editing (52) lead the list. That roughly tracks Turbo0's overall category mix — bigger categories produce more entries in any cut of the data — but it also fits the pattern above: these are utility categories people return to repeatedly (a background remover, a screen recorder, a note tool) rather than one-time discovery clicks. A case worth naming: Hootsuite, a Management-tagged tool in our dataset, gets 56% of its traffic directly, sits at roughly 2.7M monthly visits, and is growing about 49% month over month — the kind of profile where brand recall is doing real work.

Hootsuite's homepage — a well-established brand name people type back in directly, consistent with its 56% direct-traffic share.

On a much smaller scale, Notesnook, an open-source note app, has one of the highest direct shares in the entire dataset (67%) alongside steady growth — consistent with a tool people save, not search for.

Notesnook's homepage — a privacy-first notes app people bookmark and reopen daily, matching its 67% direct-traffic share, one of the highest in the dataset.

At the extreme end of the growth curve, ExportTok is direct-dominant (30% direct share) and growing about 332% month over month on roughly 874,000 visits — a reminder that "direct-dominant" spans everything from steady brand recall to a tool that's suddenly gone viral through word of mouth alone.

ExportTok's homepage — a single-purpose TikTok comment exporter, growing 332% month over month while still direct-dominant, the "gone viral through word of mouth" end of the spectrum.

The referral paradox: high hit-rate, negative median

Referral-dominant products tell a messier story, and we're presenting it exactly as messy as it is rather than smoothing it over.

Only 25 products in the entire measurable pool are referral-dominant — meaning inbound links from other sites are their single biggest traffic channel. Within that tiny group, 36% qualify as high-growth, the highest share of any segment we measured, higher even than direct-dominant's 30.1%. If you stopped reading there, you'd conclude referral traffic is the best growth channel.

But the median growth rate for this group is -16.1% — meaning the typical referral-dominant product is currently shrinking, not growing. Both numbers are true at once, and the explanation is sample size and volatility, not a contradiction: with only 25 products, a handful of outliers with launch-day or feature-roundup spikes can pull the high-growth share up sharply, while the typical (median) product in the group is watching a one-time referral spike fade back toward its previous baseline as the referring page moves down the feed. This is consistent with what indie makers usually describe about "launch platform" traffic — a Product Hunt feature, a roundup post, or a directory spike gives a real but temporary lift, and once it rolls off, growth can turn negative even while the segment as a whole still contains some genuine breakout stories. The top categories in this group — Others, Platforms, Image Editing, Growth tools, Management — mirror the direct-dominant list closely, which is more evidence this is a small, noisy slice of the same broader population rather than a structurally different kind of product.

The third leg: AI referral, still small but real

Share of the 3,295-product measurable indie pool touched by each channel signal. Categories overlap — a product can be direct-dominant and still receive some AI-referral traffic.

Separately from the dominance split above, 164 products (4.98% of the measurable pool) receive at least some traffic that Similarweb attributes to an AI platform sending visits — chatgpt.com is by far the largest source (averaging 65% of AI-referred traffic across 144 products), followed by gemini.google.com (24% across 85 products), claude.ai (18% across 67 products), and perplexity.ai (9% across 41 products). Five percent is not a wave yet, but it is a real, measurable channel distinct from the zeroed-out search field, and it's growing fast enough that we wrote a dedicated piece on it — see our AI referral traffic report for the full platform breakdown and which categories benefit most.

What this means if you're building an indie tool

Three practical takeaways, scoped to what the data actually supports:

Optimize for being remembered, not just found. A name people can recall and retype, a favicon they recognize in a crowded bookmark bar, a workflow they return to without re-Googling it — that's what direct dominance looks like from the outside, and it's the one traffic pattern that correlates cleanly with above-baseline growth in this dataset.
Don't build your roadmap around a single launch spike. The referral-dominant group's negative median growth is a reminder that a Product Hunt feature or a roundup mention is a real but temporary boost. Treat it as a distribution event, not a channel — the goal is converting that one-time spike into people who come back directly next month.
Email still shows up as a real, if small, signal — and AI referral is the channel to watch next. Mail carries genuine (if modest) traffic in this same dataset, meaning an owned list is still worth building. And with AI platforms now referring measurable traffic to about 1 in 20 measurable indie products, this is a good moment to check whether your own product shows up when someone asks an AI assistant for a recommendation in your category.

Where this data is thin, and why we're saying so

We'd rather under-claim than over-claim. Specifics worth keeping in mind:

Search, social, and paid-referral traffic are structurally unmeasured in this dataset, not zero in reality. Any product on Turbo0 could be getting meaningful search or social traffic that simply isn't visible to us right now. We're publishing this gap rather than papering over it.
The referrals-dominant group is 25 products. That's too small for the -16.1% median or the 36% high-growth share to be treated as a stable law of the category — both numbers can move a lot with a handful of additions or removals.
"Dominant" means largest share among direct/search/social/referrals, not majority share. A product can be classified as direct-dominant with, say, 30% direct traffic if that's simply larger than its other measured shares.
AI-referral figures come from a separate feed (AI-platform visit attribution) than the direct/referral dominance split, so the ~5% penetration figure and the 429/25 dominance counts are not directly additive — a product can appear in both.
This is a snapshot, not a longitudinal study. Growth percentages, especially on small visit bases, can look dramatic without representing a durable trend.

If any of these boundaries change how you'd use a specific number, that's the intent — we'd rather you know exactly what's solid and what isn't than take a chart at face value. Browse the underlying Turbo0 category directory to see where your own product would land, and if you're not indexed yet, submit it to Turbo0 so the next traffic snapshot has a data point for you too.

Originally published at turbo0.com.

Free vs Freemium vs Paid: What 5,900 Indie Tools Reveal About Pricing and Growth

Justin3go — Tue, 18 Aug 2026 14:55:55 +0000

"Should this be free, freemium, or paid?" is one of the first questions every indie maker asks, and usually the answer is a guess dressed up as a strategy. We track over 6,000 indie products in the Turbo0 directory, and almost 5,900 of them carry a normalized pricing tag — Free, Freemium, or Paid — alongside a Similarweb traffic snapshot. That combination let us ask a more grounded version of the question: across thousands of real listings, which pricing model actually correlates with traffic, and which one is quietly underperforming its reputation?

The headline finding surprised us more than we expected: the pricing model with the highest mean traffic is also the one with the worst typical outcome and the slowest typical growth. That's not a contradiction — it's a statistics lesson hiding inside a business decision, and it's the center of this article.

Methodology: what we counted and what we didn't

Every dataset here comes from Turbo0's indie pool — 5,960 alive listings (confirmed not dead) with monthly visits capped at 5,000,000, so category giants don't drown out indie signal. Pricing tags are normalized (lowercased, alphanumeric-only) and matched against free, freemium, and paid; a listing without a matching tag falls into a small "unlabeled" bucket (85 products) that we exclude from the core comparison because its sample is too thin to trust.

That leaves three groups:

Pricing model	Listings	With visits data	Median visits	Mean visits	Median growth (MoM)	High-growth share	Median DR
Free	2,123	1,151 (54%)	564	28,743	10.64%	10.25%	18
Freemium	2,811	1,640 (58%)	348.5	33,067	15.32%	10.55%	20
Paid	941	497 (53%)	434	66,295	2.92%	8.25%	19

"High-growth share" is the percentage of a group's listings that clear our high-growth bar (≥5,000 monthly visits and ≥20% month-over-month growth). All traffic and growth figures are Similarweb-style estimates from our early-August 2026 snapshot — not first-party analytics — and only the ~54–58% of each group that currently has visit history is represented in the visits/growth numbers. We'll come back to those caveats at the end.

TL;DR on what the data shows:

Paid's headline traffic number is an illusion. A handful of massive outliers inflate the mean 153x above what a typical Paid product actually sees — and the typical Paid product is barely growing.
Freemium is the healthiest model for growth, full stop — highest median growth rate, highest high-growth share, and no need for outlier apologetics.
The right pricing model depends heavily on category — Growth and Management tools lean Paid; Image Editing and Inspiration lean Freemium and Free.

The number that matters most: Paid's 153x mean-to-median gap

Median vs. mean monthly visits per pricing group. The gap between the two bars shows how much outliers are inflating the "average" figure.

Look at the median column first, because it's the number that describes what actually happens to most products. A typical Free tool gets 564 monthly visits. A typical Freemium tool gets 348.5. A typical Paid tool gets 434 — right in between, nothing special.

Now look at the mean. Free's mean (28,743) is about 51x its median. Freemium's mean (33,067) is about 95x its median. Paid's mean (66,295) is a staggering 153x its median.

This is the classic mean-vs-median trap, and it's worth spelling out because it's the most misleading number in pricing conversations. Imagine ten friends in a coffee shop, each earning a normal salary — call it a "median" income. Now Jeff Bezos walks in. The mean income of everyone in that coffee shop just became a nine-figure number, even though nobody's actual paycheck changed. The mean got hijacked by one extreme value; the median didn't move, because it just describes whoever is in the middle.

That's exactly what's happening inside the Paid group. A small number of paid products — likely established SaaS tools that have scaled into six- or seven-figure monthly traffic while staying under our 5-million-visit indie-pool cap — are pulling the mean far above what a normal paid indie product experiences. Strip out the handful of scaled winners, and the typical paid listing looks a lot like a typical free one, just with a paywall in front of it.

We call this the boutique trap: if you launch paid, you are betting on becoming one of the rare outliers that pulls the mean, because the median outcome for Paid products is unremarkable traffic and — as the next section shows — unremarkable growth.

A representative Paid pricing page (not one of the named outliers above) — a time-limited free trial gating into fixed monthly tiers, the structure most Paid indie tools share.

Paid products aren't just smaller, they're growing slower too

Share of each pricing group's listings that qualify as high-growth (≥5,000 monthly visits and ≥20% MoM growth).

Median month-over-month traffic growth rate by pricing group.

If Paid's low median visits were paired with strong growth, you could argue it's simply an earlier-stage cohort that will catch up. The data doesn't support that story. Paid products have the lowest median growth rate (2.92%) of the three groups — roughly a fifth of Freemium's — and the lowest high-growth share (8.25%), meaning a smaller fraction of paid products are breaking out at all.

Freemium, by contrast, posts the best numbers on both axes: 15.32% median growth, more than double Free's and over 5x Paid's, and the highest high-growth share (10.55%). Free sits in between on growth (10.64%) but is close to Freemium on high-growth share (10.25%) — consistent with a "free gets you discovered" dynamic even without a monetization layer attached.

A representative Freemium pricing page (not one of the named outliers above) — a genuine free-forever tier sitting next to paid tiers, the low-friction entry point that correlates with Freemium's stronger growth numbers.

A representative Free-tier homepage — no paywall in front of the core tools, the kind of no-friction entry point behind Free's strong high-growth share.

Put simply: Freemium is the only model here where the median product is meaningfully growing. Free gets people in the door. Paid, for a typical product without an existing brand or scaled distribution, mostly just sits there.

None of this means "never charge money." It means a hard paywall from day one removes the low-friction discovery loop that drives the other two models' growth — and unless you already have the audience, authority, or virality to be one of the outliers pulling that 153x mean, you should expect a slower traffic climb, not a faster one, from going Paid first.

Domain authority isn't the differentiator

One thing that doesn't explain the gap: backlink authority. Median Domain Rating is nearly flat across all three groups — 18 (Free), 20 (Freemium), 19 (Paid). If Paid products were simply younger or less-linked sites, we'd expect a materially lower DR; instead the groups are within two points of each other. Whatever separates Paid's weak median outcome from Freemium's strong one, it isn't a backlink deficit — it's the pricing wall changing who tries the product and how easily it spreads.

Which categories actually suit which pricing model

Pricing isn't chosen in a vacuum — it should match what the category's buyers expect. We cross-tabbed pricing tags against Turbo0's ten largest categories:

Share of Free / Freemium / Paid listings within each of the ten largest categories, sorted by Paid share (highest first).

Category	Free	Freemium	Paid
Growth	23.1%	51.6%	24.7%
Management	25.4%	50.9%	22.7%
Video Editing	16.7%	62.4%	19.3%
Website Creation	42.1%	38.7%	18.0%
Video Resources	23.4%	57.5%	17.6%
Others	48.0%	34.4%	16.1%
Platforms	38.1%	48.0%	13.1%
Image Resources	34.6%	51.9%	11.6%
Image Editing	27.2%	60.9%	9.5%
Inspiration	42.7%	48.3%	7.7%

Two patterns jump out:

Growth and Management tools tolerate paywalls best. These are B2B-flavored categories (marketing tools, project/team management) where buyers are used to recurring software spend and evaluate on ROI rather than needing a free trial to feel confident. Paid share here (22.7–24.7%) is roughly 2–3x the Paid share in Inspiration or Image Editing.
Visual and creative tools cluster hard around Freemium. Image Editing (60.9% Freemium) and Video Editing (62.4% Freemium) are the two most Freemium-heavy categories on Turbo0. These are inherently "try it on my own file first" products — a static screenshot or feature list doesn't sell a filter or an editing effect the way actually using it does.
Inspiration and Website Creation lean Free. Inspiration (42.7% Free) is mostly content/reference-driven, where charging up front makes little sense before you've built an audience. Website Creation (42.1% Free) likely reflects a lot of free-tier builders and generators competing for top-of-funnel users before upselling hosting or export.

If you already know your category, this table is a reasonable prior for what your market expects — and you can sanity-check any specific competitor's approach by browsing Turbo0's category pages and filtering by pricing tag directly on listings.

If we launched a product today, how would we price it?

Pulling the findings above into an actual decision framework:

Default to Freemium unless you have a specific reason not to. It has the best median growth and the best high-growth share in our entire dataset. It's the closest thing to a statistically safe default among the three models.
Don't launch Paid-only unless you already have distribution. The data says a fully paid launch, absent an existing audience, historic SEO, or a viral wedge, tends to land you at the unremarkable median (434 visits, 2.92% growth) rather than the outlier tail that's pulling Paid's mean up.
In B2B/ops categories (Growth, Management), Paid is a legitimate first move. These buyers pay for software by default; a generous free tier may cost you conversion signal without buying you much extra reach.
In visual/creative categories (Image Editing, Video Editing), let people touch the output before you ask for money. A free or freemium tier that lets someone process their own file is close to mandatory competitive table stakes in these categories — 60%+ of listings already do this.
If your category is closer to Inspiration or content-led discovery, start Free and monetize later. Charging up front before you've proven the content/utility loop works tends to suppress the organic spread that content-first products depend on.
Whatever you pick, get it measured. Only about half of each pricing group in our dataset has visit-history data at all — meaning roughly 45–47% of listings have no visible growth trajectory to point to, paid or not. If your product isn't tracked anywhere, you can't tell later whether your pricing call was actually the reason for slow growth. Submit your product to Turbo0 so there's a public trail on this the next time someone runs an analysis like this one.

Data notes and limitations

All traffic, growth, and DR figures are third-party estimates (Similarweb-style traffic, Ahrefs-style Domain Rating) from our early-August 2026 snapshot, not first-party analytics from product owners. Pricing tags are set at listing time and can go stale — a product that switches from Freemium to fully Paid (or drops a paywall entirely) after being indexed won't be reflected here until its listing is updated, so treat these tags as directional snapshots rather than live pricing pages. Visits and growth statistics are computed only over the ~53–58% of each pricing group that currently has Similarweb visit-history data; the remainder isn't missing at random, but we can't characterize its pricing/traffic relationship from what we don't have. The category cross-tab covers Turbo0's ten largest category tags only, and a listing can carry multiple category tags, so category totals don't sum to the full pricing-group counts. We'll revisit this analysis as more listings accumulate traffic history.

Originally published at turbo0.com.

AI Referral Traffic Report: Which Indie Tools Are Getting Visitors from ChatGPT?

Justin3go — Tue, 18 Aug 2026 14:48:38 +0000

"Just ask ChatGPT" has quietly become a discovery channel — somewhere between a search engine and a friend's recommendation. If an AI assistant suggests your product by name when someone asks "what's a good tool for X," that's a visitor you didn't have to win through ads or SEO rankings. The question is how many indie products are actually capturing that channel today, and whether it's worth building for.

We pulled Similarweb's AI-referral breakdown for every product in Turbo0's indie pool — 3,295 listings with usable traffic data, capped at 5,000,000 monthly visits so giants like ChatGPT itself don't skew the picture. Of those, 164 products (4.98%) show any measurable traffic from an AI platform — ChatGPT, Gemini, Claude, Perplexity, Copilot, DeepSeek, or Grok. This article is built entirely on that 164-product dataset, cross-referenced against our separate high-growth dataset (333 products growing 20%+ month-over-month) to see whether AI traffic and growth actually move together.

TL;DR:

AI referral traffic is real but still tiny — only about 5% of measurable indie products get any of it, and for most of those it's under 1% of total visits.
ChatGPT is the AI discovery channel that matters right now. It appears in 144 of 164 products (87.8%) and supplies an average of 65.5% of whatever AI traffic a product gets — Gemini, Claude, and Perplexity are present but each control a smaller slice.
Products that already get AI traffic are roughly twice as likely to also be in high-growth territory (20.1% vs. 9.5% for products with no AI traffic) — though we can't say which one is causing the other.

How small is the window, really?

Before looking at winners, it's worth being honest about the size of the opportunity. Even among the 164 products that show up in an AI assistant's answers at all, most of them barely register.

Distribution of AI traffic share among the 164 products that have any. Half of them sit below 0.4% of total visits; only a handful cross 3%.

The median product in this dataset gets 0.4% of its total traffic from AI assistants; the mean is pulled up to 0.85% by a short tail of outliers. Only 10% of the 164 products cross 2.17%, and the single highest share in the entire indie pool is 6.3% (HandBrake, more on that below). Compare that to search or direct traffic, which for most of these same products still make up the overwhelming majority of visits.

So the honest framing is: AI referral traffic is not yet a primary channel for anyone in this dataset. It's a secondary or tertiary source that's clearly growing in relevance, showing up for niche informational products, well-documented open-source tools, and AI-native apps first — a shape that matches how people currently use chat assistants (asking for a tool, a file converter, a comparison) more than how they use search engines for transactional or navigational queries.

ChatGPT's near-monopoly on AI referrals

If you're optimizing for one platform, the data makes the priority obvious.

ChatGPT dominates on both dimensions — the most products cite it (87.8%), and it supplies the largest average share of AI traffic where it appears.

Of the seven AI platforms Similarweb tracks, ChatGPT (chatgpt.com) appears in 144 of 164 products — 87.8% — and where it appears, it supplies an average of 65.5% of that product's total AI-sourced traffic. Nothing else comes close on either dimension:

Gemini appears in 85 products (51.8%), averaging 23.7% of AI traffic where present.
Claude appears in 67 products (40.9%), averaging 17.5%.
Perplexity appears in 41 products (25.0%), averaging 9.2%.
Copilot, DeepSeek, and Grok together appear in only 10 products combined, each contributing under 1% on average.

A few products buck the trend in an interesting way — a handful get the majority of their AI traffic from Claude or Gemini specifically rather than ChatGPT, which we'll get to in the case studies below. But as a rule, if you can only test your product's visibility in one assistant, test it in ChatGPT first; it's both the most common source and the largest single contributor everywhere else it shows up alongside.

Which categories AI assistants recommend most

AI referral traffic isn't evenly spread across the kinds of products indie makers build. It clusters hard around visual and creative resources.

Image and video tools dominate the category breakdown — a pattern consistent with how people phrase creative-tool questions to AI assistants.

Image Resources leads with 28 of the 164 products, followed closely by Video Editing (22), Image Editing (22), and Platforms (22), then Video Resources (20) and Screen Recording (18). Together, image- and video-related categories account for well over half of the dataset.

This lines up with how people actually phrase requests to chat assistants: "find me a free stock video site," "what's a good screen recorder for Mac," "how do I convert this video file" — these are exactly the kind of concrete, single-answer questions where an AI assistant can confidently name a specific tool instead of returning a list of ten blue links. Categories that are more subjective, workflow-dependent, or require comparing many options side by side (like broad SaaS platforms or niche B2B tools) show up far less, likely because the "right answer" is less obvious to an AI model and more dependent on the user's specific situation.

Does AI traffic correlate with growth?

This is the question we most wanted to answer, and it required joining our AI-referral dataset against our separate high-growth dataset (products with at least +20% month-over-month growth) by product slug.

Products with any AI referral traffic are about twice as likely to also be growing fast month-over-month.

Of the 164 products with AI referral traffic, 33 (20.1%) also qualify as high-growth in our separate dataset. Among the remaining 3,131 measurable indie products with no detected AI traffic, only 299 (9.5%) are high-growth. That's roughly a 2.1x difference in high-growth rate between the two groups.

We can't settle causality with this data, and there are at least two plausible stories that aren't mutually exclusive: AI traffic could be driving new visitors who stick around and compound into growth, or growth could be a side effect of the same things that make a product AI-citable in the first place — recent content, backlinks, press mentions, community discussion. Realistically it's probably both, reinforcing each other. Either way, the practical takeaway holds: shipping visibly and keeping documentation current appears to help on both fronts at once.

Five products actually getting AI traffic

Numbers are more useful with faces attached. Here are five real products from the dataset — each explanation below is our informed guess, not query-level data we actually have access to.

HandBrake — the highest AI-traffic share in the dataset at 6.3% of its 1.6M monthly visits (91% from ChatGPT). Free, open-source video transcoding software with 20+ years of documentation, forum threads, and tutorials behind it. Guess: "how do I compress an MP4" is a common, low-ambiguity question, and HandBrake's documentation depth makes it the default answer.

HandBrake's homepage — plain, documentation-heavy, and unmistakably answering one specific question, which is likely why ChatGPT reaches for it.

Hailuo AI — 6.1% share on 2.7M monthly visits, 98.5% from ChatGPT. An AI video generation tool that benefits from a double effect: people ask ChatGPT to recommend AI video generators, and it's a well-known, active entrant in that exact category.

Hailuo AI's homepage — an active, frequently updated AI video generator, the kind of visible product launch activity that keeps a tool top-of-mind for a model.

Bolt.new — 5.2% AI share on 3.8M monthly visits, 93.8% from ChatGPT. A prompt-to-app builder, part of the AI-coding-tool wave that gets discussed constantly across launch posts, comparisons, and walkthroughs — the kind of public discourse a model can recall by name.

Bolt.new's homepage — one of the most-discussed AI coding tools, the kind of product that shows up constantly in launch threads and comparisons a model can draw on.

Mixkit — 3.9% AI share on 3.7M monthly visits, 89.3% from ChatGPT. A free stock video, music, and sound-effects library that answers one very specific, repeatable request: "free stock footage, no attribution required."

DatePhotos.AI — a much smaller tool at 29,820 monthly visits, notable because its AI referral traffic (1.9% share) is 100% from Claude, not ChatGPT — the opposite of every case above. It's also growing +76.5% month-over-month, making it a concrete instance of the AI-traffic-and-growth overlap discussed earlier, and a reminder that ChatGPT's dominance is a population-level pattern, not a guarantee for every product.

How to make your product easier for AI to recommend

Nobody outside the AI labs knows the exact retrieval or training pipeline, but the pattern in this dataset — well-documented tools, specific use cases, active public discussion — points toward a few concrete, low-risk practices:

Write a clear, literal product description. AI assistants tend to recommend tools by restating what they do in plain language. Give the model — and human visitors — a one-sentence, jargon-free description near the top of your homepage.
Add structured data. Schema.org markup (SoftwareApplication, Product, FAQPage) gives crawlers and AI ingestion pipelines an unambiguous, machine-readable summary of what your product is, its pricing, and its category, reducing the guesswork a model would otherwise do from prose alone.
Get listed in directories that AI systems actually crawl. Directory listings are structured, categorized, and frequently updated — efficient sources for both search engines and AI retrieval. Every product on Turbo0 gets a structured listing with category tags, pricing, and a description: exactly the clean, indexable data that's cheap for automated systems to ingest. If your product isn't listed yet, submitting it to Turbo0 takes a few minutes and costs nothing.
Keep an llms.txt file current. An emerging, still-informal convention where sites publish a plain-text summary of their content specifically for AI consumption, similar in spirit to robots.txt for crawlers. Low-cost to maintain, and forward-looking even while adoption is early.
Publish content that answers specific, repeatable questions. The winning products here solve a narrow, clearly-named problem ("convert this video," "free stock footage") rather than a broad, ambiguous one. A dedicated page answering that exact question in plain language is more likely to match how AI assistants retrieve and cite sources.

A note on the data

This report uses Similarweb's AI-platform referral estimates as surfaced through Turbo0's product tracking, snapshotted on August 9, 2026. Similarweb's AI-referral attribution is itself an estimate, not first-party analytics from each product's own dashboard, so absolute percentages should be read as directional rather than precise. The 3,295-product denominator only includes indie listings (capped at 5M monthly visits) with Similarweb visit-history data at all — many more Turbo0 listings exist without measurable traffic data yet. And the growth correlation above is just that: a correlation observed at a single point in time, not a controlled experiment.

If you're building an indie product and want a low-effort way to become one of the structured data sources AI systems can point to, submit it to Turbo0 — the resulting directory listing is exactly the kind of clean, categorized data this report suggests AI assistants are already citing.

Originally published at turbo0.com.

We Track 6,000+ Indie Tools. 74 Are Confirmed Dead. Here's the Autopsy.

Justin3go — Tue, 18 Aug 2026 14:40:17 +0000

Turbo0 currently indexes 6,100 products. As of this writing, 74 of them are confirmed dead — sites that no longer resolve, redirect to a parking page, or have visibly shut down. That's a death rate of about 1.21% of everything we've ever listed.

That number is small on purpose: we don't guess, and we don't mark something dead because traffic dipped for a week. Every one of these 74 was manually verified. This post is what we found looking at all 74 together: which categories lose the most products, how long a typical tool survives before disappearing, and what its pricing model looked like on the way out.

If you're building something right now, treat this as a set of base rates, not a graveyard tour. Some of it will be reassuring. Some of it won't.

How We Know They're Dead

Every product in Turbo0 gets a recurring snapshot of two signals: Ahrefs Domain Rating (DR) and Similarweb traffic estimates, captured weekly and monthly respectively — a small time series per product, so we can watch DR drift and traffic rise, flatline, or drop to zero.

Those series are a signal, not a verdict. When a product's traffic has sat at zero for a while and DR is sliding, it goes on a review list, and someone on the team actually visits the site: still live? redirected to a domain-parking page? DNS even resolving? Only after that manual check does a product get marked dead — it goes onto a confirmed list, and a batch job flags the listing as unavailable in the directory.

One deliberate decision worth calling out: we don't delete dead listings. The page stays up with a visible "This site is no longer available" label, and every outbound link on it — regardless of pricing tier — switches to nofollow. We'd rather keep the historical record than erase it, but won't keep passing link equity to a domain that no longer serves the product it was indexed for.

One honest caveat: 74 is a floor, not a ceiling. Detection has lag — a product can go dark for weeks before its traffic signal drops enough to trigger review, and slow deaths (a site that still loads but hasn't shipped or answered support in a year) never get caught. The real number of abandoned products here is almost certainly higher than 74. What follows is what we can prove, not a full census.

Which Categories Actually Die More

The easy way to slice this is by raw counts: "Others" (18 dead), "Image Editing" (16 dead), and "Platforms" (15 dead) top the list. But raw counts mostly reflect how many products exist in a category in the first place — a category with 1,600 listings will rack up more dead products than one with 100, even at a lower failure rate. What matters is the death rate: dead products divided by total products in that category.

Death rate by category. Categories under 100 total listings are flagged — a single death moves their rate a lot, so treat those numbers as directional, not conclusive.

Ranked by rate instead of count, one category stands out with both a high rate and a large enough sample to trust: Image Editing, at 1.45% (16 dead out of 1,100 listed) — the highest rate among any category with a meaningful sample, and not close. The next comparable one, Platforms, sits at 1.10% off a similarly large base (1,368 listings).

Two other categories technically post similar or higher rates — Screen Recording and Video Resources, both 1.39% — but need a footnote. Screen Recording's rate comes from a single dead product out of only 72 listed: one data point wearing a percentage sign, not a trend. Video Resources is sturdier (5 dead out of 361) but still thin next to Image Editing's sample. We're flagging this rather than treating all three as equally proven.

The practical read: Image Editing is the one category where we can say, with real confidence, that competition and turnover are unusually high. It's also one of Turbo0's most crowded categories, likely no coincidence — a flood of AI-powered image tools launched over the past year, many built on the same handful of underlying models, competing almost entirely on UI and pricing rather than any defensible moat. That's not a reason to skip the category — it's a reason to have a specific answer for why you'll still be running when a dozen similar competitors aren't.

How Long Do They Actually Survive?

For each dead product we have an estimated survival window — time from launch to confirmed shutdown. Across all 74:

Estimated survival time in months for the 74 confirmed-dead products. The dashed line marks the median: 10.68 months.

Minimum: 2.42 months
p25: 8.33 months
Median: 10.68 months
p75: 12.79 months
p90: 14.34 months
Maximum: 16.51 months
Mean: 10.35 months

A few things jump out. First, the median is under a year — half of the products that eventually died didn't make it to their first anniversary. Second, the spread between p25 and p90 — 8.33 to 14.34 months — is a tight six-month band holding the middle 80% of all deaths. Almost nothing survived past 16.5 months, and almost nothing died in the first two months either: the failure mode here isn't "abandoned on day one," it's "ran for roughly a year, then quietly stopped."

That pattern lines up with a familiar arc: launch, get an initial traffic bump (a directory listing, a Product Hunt post, an early SEO win), coast on it for several months, then — without a compounding channel or revenue that covers hosting and time — wind down between month 8 and month 15. If your product is past that window and still running, the data suggests you've cleared the highest-risk stretch — not that you're safe, but that you've outlasted most of what didn't make it.

Pricing Model and Death: A Correlation, Not a Verdict

Here's the pricing breakdown across the 74 dead products:

Pricing tags on the 74 dead products. Free products make up just over half of all confirmed deaths.

Free: 37 products (51%)
Freemium: 29 products (39%)
Paid: 7 products (9%)

It's tempting to read this as "paid products are safer," and the raw numbers are consistent with that story — free products make up more than half of everything that died, paid products less than a tenth. A fully free tool has no revenue line; it survives entirely on the maker's willingness to keep paying for hosting and maintenance with zero return, a much weaker foundation than even a small trickle of subscription revenue.

But we want to avoid overclaiming causation: we don't know the pricing-model split of the surviving 6,026 products, and free tools are almost certainly the largest slice of the whole directory, not just the dead pool. If, say, 55% of all 6,100 listings are free, then free products dying at 51% of the dead-pool rate might just reflect their share of the population, not elevated risk. Paid having the fewest deaths (7) may likewise reflect that far fewer products here are Paid to begin with, not that charging money is shutdown-proof.

What we can say without overreaching: shipping with zero monetization built in removes the single biggest reason a maker keeps paying attention once the initial excitement fades. Even a Freemium tier — one paying customer, one signal that someone cares — changes the incentive to keep the lights on. The data doesn't prove "charge money and you'll survive," but it's consistent with "no revenue path at all is one more reason a project gets abandoned around month 10."

Five Products, Briefly

Names and numbers, without commentary beyond what the data shows:

Pain Signal (Freemium, Growth) — the shortest-lived product here, running an estimated 2.42 months before shutdown.
Unblur Image (Freemium, Image Editing) — an AI image-sharpening tool, one of the 16 Image Editing deaths, lasted about 4.2 months.
Beam Video (Paid, Video Resources) — a rare paid-tier death, survived an estimated 9.94 months, roughly in line with the median.
Screenrecorder.me (Free, Screen Recording) — the single confirmed death in that category (out of 72 listed), lasted about 15.1 months, well above the median.
NuxtBase (Paid, Website Creation) — the longest survivor in this dataset at an estimated 16.51 months; even a paid model and the longest run we've confirmed eventually still ended.

Beam Video's Turbo0 listing today — the dead-site badge and the nofollow treatment described above, applied to a real product.

A Wayback Machine snapshot of beamvideo.io from December 18, 2025 — the last look at the product before it went dark.

NuxtBase's Turbo0 listing — the longest-surviving product in this dataset (16.51 months), still eventually marked dead.

These aren't cautionary tales in the mocking sense — most were reasonably built tools solving real, if narrow, problems. They're just data points in a distribution most indie products eventually fall somewhere in.

One More Angle: When Were They Born

Month each of the 74 dead products was first listed on Turbo0 — this tracks our own listing volume more than anything else, so read it as context, not a mortality trend.

The cluster around August–October 2025 mostly reflects when Turbo0 itself listed more products, not a riskier launch window. It does mean most of these 74 launched within the last year and a half, consistent with the 10.68-month median — we're catching deaths close to real time, not sifting a decade of history.

What This Actually Teaches an Indie Maker

Pulling the threads together, here's what the data supports — not generic startup advice, but conclusions tied to these 74 products:

Month 8 through month 15 is your danger zone. With p25 at 8.3 months and p90 at 14.3 months, most failures here happened in that window — not immediately, rarely after 16 months. Heading into your first year without a plan for what keeps things running past month 10 is the risk this data flags.
A zero-revenue model isn't automatically fatal, but it removes your safety margin. Free products account for 51% of confirmed deaths. We can't prove causation given the unknown baseline, but the implication holds regardless: build in at least one signal of real demand — a paid tier, a waitlist that converts — before launch traffic fades, since it rarely sustains a project past year one.
Be honest about how crowded your category already is. Image Editing has both a large enough sample and a high enough death rate to call competition there unusually brutal — 16 deaths out of 1,100 listings, triple the rate in categories like Growth or Video Editing. Not a reason to skip image tools; a reason you need a specific answer for why users pick yours over a dozen near-identical wrappers.
Small-sample death rates can mislead — check the denominator before trusting a scary statistic, including some in this article. Screen Recording's 1.39% rate is one product out of 72. Don't let a single data point talk you out of, or into, a category.

If you're building an indie tool, Turbo0 tracks all 6,100 of these products — dead and alive — and you're welcome to submit your own. We'd rather see you in the "alive" column a year from now than in a future version of this report.

Originally published at turbo0.com.

High-Growth Indie Tools: What 333 Fast-Growing Products Have in Common

Justin3go — Tue, 18 Aug 2026 14:36:51 +0000

We track over 6,000 indie products in the Turbo0 directory, and every one of them has a public traffic snapshot from Similarweb attached to its listing. That gave us a rare chance to ask a boring but useful question: among indie tools that are actually growing right now, what do they have in common — category, pricing, backlink authority, or something else?

This is a data article, not a listicle. We are not claiming any of these 333 products is objectively "the best." We are reporting what a clean traffic snapshot says about who is winning right now, and trying to be honest about where the data is thin.

Methodology and what "high growth" actually means

Turbo0's indie pool starts at 5,960 alive listings (websites we've confirmed are not dead) with monthly visits capped at 5,000,000 — anything bigger, like ChatGPT or Google Fonts, is excluded so giants don't drown out indie signal. Of those 5,960, only 3,295 currently carry Similarweb visit-history data; growth can't be measured without a prior month to compare against, so that subset is our real denominator.

From those 3,295 measurable products, we filtered to:

Monthly visits ≥ 5,000 (enough traffic that the growth number isn't statistical noise on a handful of visits)
Month-over-month growth ≥ +20%

That left 333 products — about 10.1% of the measurable indie pool. This is the dataset behind every chart in this article. All traffic, growth, and Domain Rating (DR) figures are Similarweb/Ahrefs-style estimates from our early-August 2026 snapshot, not verified analytics from the product owners. Growth percentages on small bases can look dramatic — a jump from 900 to 7,800 visits is "+767%" and technically true, but it's a different phenomenon than a site holding steady at 300,000+ visits while adding another 90,000. We flag that distinction explicitly where it matters.

TL;DR on what we found:

Growth concentrates in visual/creative and utility categories, but density (share of a category's total products that are growing fast) tells a different story than raw counts — Video Resources and Platforms have the highest hit rates, not the biggest headline numbers.
Freemium dominates (52% of high-growth products), and pricing correlates with growth speed more than category does.
Backlink authority (DR) barely matters once you're already growing — the correlation between DR and growth rate inside this group is essentially zero.

Where growth concentrates: category counts vs. category density

By raw count, growth is heavily weighted toward a handful of categories:

Absolute count of high-growth products per category tag (products can carry more than one tag, so totals exceed 333).

Platforms (92), Others (67), and Image Editing (57) lead by volume, which mostly reflects the fact that these are Turbo0's biggest categories overall — more listings means more chances to show up on a "fastest growing" list. Raw counts alone would tell you to go build "another AI platform," which isn't a useful takeaway.

A more honest lens is density: for each category, what share of all indie products in that category (not just the high-growth ones) are currently in our high-growth set? We could compute this for the ten categories where we have full indie-pool denominators from our pricing/category cross-tab:

Category	High-growth count	Category pool size (indie)	Density
Video Resources	26	346	7.5%
Platforms	92	1,353	6.8%
Growth	43	653	6.6%
Image Resources	37	570	6.5%
Inspiration	18	286	6.3%
Video Editing	36	647	5.6%
Image Editing	57	1,072	5.3%
Management	27	629	4.3%
Others	67	1,632	4.1%
Website Creation	14	416	3.4%

By density, Video Resources actually has the highest hit rate — 7.5% of everything tagged Video Resources in the indie pool is currently in fast-growth mode, edging out Platforms (6.8%) even though Platforms has 3.5x the absolute count. Website Creation and Others sit at the bottom, meaning they're large, crowded categories where a fast-growing product is comparatively rare. We don't have full-pool denominators for the smaller categories (Audio Resources, Note-taking, Copywriting, Typography, Audio Editing, Audio Recording, Font Resources, Screen Recording), so we're reporting those by absolute count only in the chart above rather than guessing at a density figure.

Practically: if you're deciding where to build, "biggest category" and "category where growth is most likely" are not the same list. Browse what's already live in each space via Turbo0's category directory before assuming a crowded category is automatically a bad one — density still leaves real headroom in Platforms and Growth-tools specifically.

Pricing: Freemium wins, but "Free" is close behind

Distribution of the primary pricing tag across 332 tagged high-growth products (1 product had no matching price tag).

Freemium (173, 52%) is the dominant model among fast-growing products, followed by Free (118, 36%) and Paid (41, 12%). That's a meaningfully different mix from the indie pool at large, where our pricing dataset puts Paid products at a much larger relative share and shows materially lower median growth for Paid listings than for Free or Freemium ones. Read plainly: a no-friction first touch — try it free, decide whether to pay later — correlates with faster traffic growth than gating the product behind a paywall from day one. That doesn't mean paid products can't grow (41 of them are in this list), but they're underrepresented relative to their overall share of the directory, and the products that do grow while fully paid tend to be narrow, high-intent utilities rather than broad platforms.

Just how "high growth" is high growth?

Log-scaled histogram of MoM growth percentage. Median 80%, p90 389%, max 6,597% (on a small base — see caveats).

The +20% floor is just the entry bar — the real distribution skews much higher. The median product in this set grew 80% month-over-month, and the top decile grew 389%+. A handful of extreme outliers (like FileShot.io, up from 2,529 to 169,359 monthly visits, or two watermark-removal utilities — chatgptwatermarkremover.org and removegeminiwatermark.net — both up 1,000%+) are riding narrow, high-intent search demand off a small starting base, on sites with single-digit-to-low-20s DR. These are real gains, but a different growth shape than an established product compounding off hundreds of thousands of existing visits — "1,000% growth" alone isn't proof of durable product-market fit; it can just as easily mean a landing page caught a trending keyword three weeks ago.

Does Domain Rating matter? Barely, once you're already growing

Each point is one high-growth product. Color encodes DR (darker = higher authority). Both axes are log-scaled.

This is the counterintuitive finding. The median DR across the 333 high-growth products is 27 (mean 28.5) — modestly higher than the roughly 18–20 median DR across the indie pool's pricing groups overall, so some baseline authority does seem to help a product clear the growth bar in the first place. But once a product is already in the high-growth set, DR stops predicting how much it grows: the correlation between DR and growth rate across these 333 products is -0.08, essentially flat. Fully 26% have DR below 20, and 62% have DR below 30 — including several of the fastest movers in the set, like Youth Job Board Canada (DR 9, +761%) and the watermark-remover utilities above (DR 6–7, +1,000%+).

The scatter plot makes this visible: the darkest (highest-DR) points are scattered across the full range of growth rates rather than clustering at the top. High authority correlates weakly with starting from a larger visits base (DR-to-log-visits correlation is +0.19, still fairly weak) more than it correlates with growth velocity. If you're an indie maker without years of backlinks, this dataset does not support "you need high DR to grow fast" as a blocker.

AI-assistant referral traffic: present, but still tiny

Of the 333 high-growth products, 28 (8.4%) show any measurable referral traffic from AI assistants (ChatGPT, Gemini, Claude, Perplexity, and similar) — a slightly higher incidence than the roughly 5.0% of the broader Similarweb-covered indie pool with any AI referral at all. But where it exists, the share is small: median 0.6% of total traffic, and even the top case in this group tops out at 2.6%. Across the wider directory, ChatGPT accounts for the large majority of AI-referral share when it appears at all (~65% average share among products with any AI referral), with Gemini, Claude, and Perplexity trailing well behind.

Read that as: AI-assistant discovery is a real, growing edge, not yet a primary channel, even for products actively winning traffic elsewhere. Worth instrumenting for and worth making your product genuinely citable (clear docs, structured comparisons, a crawlable changelog), but not worth over-indexing your whole growth strategy on today.

On traffic sources more broadly, we have to flag a real limitation in our source data: Similarweb's search, social, and paid-referral share fields return exactly zero for every single product in our entire database, which is almost certainly an upstream data-tier limitation rather than a claim that no Turbo0 product gets organic search or social traffic. We can only speak confidently to direct, referral-link, and email traffic. Within products where a channel is identifiable, direct traffic dominates (average ~13.5% of measured share among high-growth products), referral links are a distant second (~2.7%), and email is negligible (~0.4%). We're not going to claim "SEO doesn't matter for indie growth" from this data — that conclusion isn't supported, it's a gap in what we can observe.

Three products, three growth shapes

To make the statistics concrete, three real listings from this dataset:

CrePal (Video Editing / Video Resources / Platforms, DR 35) grew from roughly 221,000 to 372,000 monthly visits (+68%) — a large, established product compounding off an already-substantial base. This is the "boring good" growth shape: steady expansion on top of real scale.

CrePal's homepage — an established, multi-category product with real scale behind its +68% growth.

Nano Banana Pro (Image Editing, DR 31) roughly quadrupled from 22,700 to 83,900 monthly visits (+269%) — mid-stage momentum, riding the broader wave of interest in AI image editing without yet being a top-tier authority site.

Nano Banana Pro's homepage — riding the broader AI-image-editing wave, mid-stage authority but momentum well above its DR would suggest.

Gemini Watermark Remover (Image Editing, DR 6) jumped from 1,583 to 17,932 monthly visits (+1,033%) on almost no backlink authority — a narrow, single-feature tool capturing demand for one very specific, high-intent search query.

A Gemini watermark-remover landing page — the archetype of a single-feature tool riding one narrow, high-intent search query to a 1,000%+ growth spike on almost no backlink authority.

Same "high growth" label, three genuinely different businesses. We'd treat them as different playbooks, not one recipe.

What this means for indie makers (and for us)

A few concrete, data-backed takeaways:

Ship the free tier first. Freemium and Free together are 88% of this list. If your model is fully paid from launch, expect a steeper climb to visible traffic growth — plan for it rather than being surprised by it.
Don't let DR anxiety stop you from launching. A quarter of the fastest-growing products in our directory have DR under 20. Authority may help you clear the growth bar eventually, but it does not predict how fast you'll grow once you're moving.
Density beats raw category size when picking a niche. Video Resources and Platforms had the best hit rates in our data, not the biggest headline counts — check both before you commit to a category.
Treat huge percentage growth numbers skeptically, including your own. A jump from a few hundred visits to a few thousand is real, but it's not evidence of durable demand yet. Watch whether growth holds for two or three months in a row, not one snapshot.
Instrument for AI-assistant referrals now, even though the volume is small today. 8.4% of high-growth products already show measurable ChatGPT/Gemini/Claude/Perplexity referral traffic; that share was likely near zero a year ago and is probably not shrinking.
Get listed somewhere your traffic snapshot can actually be tracked. We only have Similarweb history for 3,295 of 5,960 indie products, which means over 2,600 listings have no visible growth story at all — including possibly-growing ones. If you're not already indexed, submit your product to Turbo0 so there's a public trail to point to next time someone runs this analysis.

Data notes and limitations

All traffic, growth, and DR figures are third-party estimates (Similarweb-style traffic, Ahrefs-style Domain Rating) captured for this article on August 9, 2026 — not first-party analytics from the product owners, and not immune to smoothing or lag in ways we can't fully audit. The 333-product set is only the subset of the indie pool that had visit-history data available and cleared our +20% MoM / 5,000-visit thresholds; roughly 2,665 indie products had no comparable Similarweb history and are excluded by construction, not because they aren't growing. Search, social, and paid-referral traffic-source shares are structurally empty in our data source for every product in the database and should not be read as evidence about actual search or social performance. We'll revisit this analysis periodically as more listings accumulate traffic history.

Originally published at turbo0.com.

What is DeepSeek-Harness? A Complete Introduction

Justin3go — Tue, 18 Aug 2026 01:22:03 +0000

DeepSeek-Harness, commonly shortened to dsh, is an open-source agent harness built by DeepSeek AI. Its defining idea is "everything is a plugin": the CLI, the web UI, tool access, slash commands, skills, and even MCP server connections are all implemented as plugins on top of a general-purpose plugin framework called Cordis. There is no separate manifest format for each capability type — one plugin mechanism covers all of them.

dsh is currently in developer preview (version 0.1.0-rc.5 at the time of writing). The project's own README is explicit about what that means: expect compatibility-breaking changes as the framework iterates.

"Everything is a plugin" — what that actually means

Most agent tools split their extensibility into separate systems: one format for tools, another for slash commands, another for skills, another for MCP configuration. dsh collapses all of that into a single concept. A plugin is just a JS/TS module that exports an apply(ctx, config) function, and depending on what it registers on ctx, it can become any of the following:

You want to add...	The plugin registers...
A tool the model can call	`ctx.tools.register()`
A slash command (`/xxx`) for the UI	`ctx.commands`
A skill (injected prompt + tool)	a prompt section plus a tool, injected on invocation
An MCP server's tools	one plugin per MCP server, discovering and registering its tools via `ctx.tools.register()`
A hook into agent/tool lifecycle events	a listener on extension points like `agent/pre-step` or `tools/pre-execute`
A new LLM provider	a `LlmAdapter` registered via `ctx.llm.registerAdapter()`
A background/cron job	`ctx.jobs`

Notably, dsh ships official bridge plugins — dsh-hooks-claude-code and dsh-hooks-codex — that translate an existing Claude Code or Codex hooks.json into dsh's own hook extension points, so hook configs from those ecosystems can be reused rather than rewritten.

If you've used a harness where skills, commands, and MCP connections each need their own config file, this is the biggest conceptual shift: in dsh, they're all just code that calls ctx.

Installing dsh

The fastest way to try it is to run it straight from npm, no clone required:

npx @deepseek-ai/dsh web

This starts the web UI, listening by default on http://127.0.0.1:3080.

If you want to work from source instead — useful if you're developing your own plugin against the latest framework code — clone and build the repo directly:

git clone https://github.com/deepseek-ai/deepseek-harness.git
cd deepseek-harness
pnpm install
pnpm run build
pnpm dsh web

Profiles: how dsh keeps configurations separate

A profile is a named, runnable configuration — a directory under $DSH_HOME/profiles/<name> (with $DSH_HOME defaulting to ~/.dsh) that lists which plugin bundles are active and in what order. You start dsh against a specific profile:

dsh --profile <name>

dsh web is actually shorthand for --profile web, and dsh --profile headless "<task text>" runs a one-shot task with no UI at all. Profiles are how you keep, say, a minimal headless automation setup separate from a plugin-loaded web UI setup, without them stepping on each other's configuration.

Plugins are added to a profile with:

dsh plugin --profile <name> add <specifier>

We cover this command — and the npm/GitHub/local-path sources it accepts — in detail in How to Install DeepSeek-Harness Plugins.

The plugin ecosystem today

Here's the part that matters if you're trying to find plugins worth installing: DeepSeek AI does not run an official plugin marketplace or registry. The only first-party discovery mechanism is a convention — plugin authors are encouraged to tag their GitHub repository with the topic dsh-plugin so it can be found by search. There's no central review process and no official list.

Into that gap, the community has built its own directories. The most actively maintained one is awesome-dsh-plugin/awesome-dsh-plugin, a curated, hand-reviewed list that currently tracks 365 plugins across 11 categories — UI Enhancements, Tools & Capabilities, Workflow & Automation, Memory, Development & Runtime, and more.

That's exactly the gap FindHarness exists to close. We index those community-discovered plugins with real GitHub metadata — stars, license, last-push date, and full READMEs — so you can browse, search, and compare them like a proper catalog instead of scrolling a single giant README. Start with /plugins to search the full list, or /categories to browse by what a plugin actually does.

Where to go next

Ready to install something: How to Install DeepSeek-Harness Plugins (2026 Guide) covers the exact dsh plugin add syntax, every supported source, and the security tradeoffs of installing from GitHub.
Want recommendations first: 10 Best DeepSeek-Harness Plugins in 2026 ranks real, installable plugins by GitHub stars across categories.
Building your own plugin: How DeepSeek-Harness Plugins Work Under the Hood walks through the apply(ctx, config) contract and how to get a plugin discovered.

Originally published at findharness.com.

HUNT0 is live — Ship Early, Hunt Early

Justin3go — Thu, 01 Jan 2026 13:51:09 +0000

It all started with a slightly “ugly” sketch: a ladder leaning forward.

That ladder sketch became the HUNT0 logo. It’s a reminder that progress is built rung by rung — and shipping something imperfect beats waiting for perfect.

That’s also where the tagline “Ship Early, Hunt Early” comes from: makers ship early so the community can hunt early — discover, vote, and discuss — helping great products find their first users.

If you’re building in public, launch here. If you’re curious, start hunting.

What is HUNT0?

HUNT0 is a community-driven launch directory. It brings shipping and discovery into the same rhythm:

Reserve a launch date and make shipping a real event
Get early feedback through voting and comments
Use leaderboards and Explore to organize “new products” by time and interest — not noise

Launch v1.0.0: what we’ve built

v1.0.0 focuses on the core loop first: launch → discover → vote → discuss → recap/reward.

1) Home leaderboards: “what should I check out today?”

The home page is organized by time ranges so you can quickly scan what’s worth attention:

Top Products Launching Today: products launching today (UTC)
Yesterday / This Week / This Month: recaps with longer windows

Voting state is synchronized in real time across the page: vote on a product anywhere, and every instance updates immediately — no refresh needed.

2) Explore: filter by intent, not luck

Explore supports category, tags (up to 10), time range, and full-text search, with paginated results.

Under the same filters, Premium Launch products are prioritized above free launches in ordering — ideal for moments when visibility matters more.

3) Product pages: showcase, visit, and discuss in one place

Each product has a dedicated page for deeper context and community interaction:

Key info and external links (Visit)
Screenshot gallery and a longer “About this product”
Reputation-weighted votes and comments
Leaderboard/award badges (when you rank Top 3 in daily/weekly/monthly awards)

4) Submissions: Free queue + Premium Launch

We designed “launch” as a controlled workflow, not just posting a link:

Free Launch: limited daily capacity (default 10 slots/day) for most launches
Premium Launch: paid via Stripe Checkout for launches that need stronger visibility

If a premium checkout isn’t completed, the submission stays as a draft in your dashboard and won’t appear publicly until payment succeeds.

Submissions support richer presentation:

Up to 3 categories
Up to 10 tags
Contact/social links (at least one)
Logo and screenshots for a better product page

Reputation: make contribution count

Voting isn’t a flat “one person, one fixed vote”. HUNT0 uses Reputation → Level → Vote Weight:

Earn reputation by participating (daily visits, voting, commenting, launching)
Higher levels unlock stronger vote weight
Leaderboards aggregate weighted votes, reflecting trusted contributors more

It’s both an incentive system and a practical way to reduce noise in early-stage communities.

Reminders & awards: treat launches like events

To make launching feel like a real moment, we added automation around it:

Launch reminder email: sent 1 hour before the UTC launch day begins
Daily/weekly/monthly awards: automatically compute Top 3 and notify makers (with optional public recap)

Get started

If you’re a maker: go to Submit and reserve your launch date
If you want to discover: go to Explore and filter by category/tags
If you want the story: go to About and see where the ladder came from

We’ll keep iterating on discovery, leaderboards, and community incentives. Launch something, hunt something — and tell us what to improve.

Labubu Doll: Origins and History

Justin3go — Fri, 20 Jun 2025 01:21:22 +0000

Original link: Labubu Doll: Origins and History

Labubu was created by Hong Kong-born artist Kasing Lung (龙家昇) as part of his Nordic-inspired “Monsters” story series. Lung grew up in the Netherlands and drew on European fairy-tale and elf folklore to design Labubu’s distinctive look. The character first appeared in Lung’s artwork around 2015, but remained a niche art-toy concept until a licensing deal with the Chinese blind-box company Pop Mart in 2019. Pop Mart then began producing Labubu figurines and plushes, transforming Lung’s illustrations into mass-market collectibles. (Lung had sketched these characters in children’s books and illustration work before they became Pop Mart toys.) As Lung has noted, Labubu was always mischievous but kind-hearted – a “small monster” with pointed ears and serrated teeth who tries to help despite causing chaos.

Product Releases & Design Evolution

Labubu toys have been released in many forms over time. In 2015–2016, the character first debuted in How2Work’s collectible “Monsters” series (vinyl figures and storybooks). Major milestones include:

2019: Kasing Lung signs an exclusive license with Pop Mart, which launches the first official Labubu blind-box releases. Pop Mart begins producing Labubu figures (vinyl and plush) for China’s market.
2022: Pop Mart issues labubu-themed series like “Time to Chill” (Oct 2022) to growing fan interest. (By this time, Labubu figures were selling out minutes after restock.)
2023: Pop Mart expands Labubu into plush keychain charms. In October 2023 it released the “Tasty Macarons” (心动马卡龙) vinyl-face series (also called “Exciting Macaron”) featuring dessert-colored Labubu bag charms. (This was a new “vinyl face” line where Labubu’s vinyl mask is atop a soft plush body.) Later in 2023, Jump For Joy (May) and Dress Be Latte (Oct) plush editions came out as part of core collections.
2024: Pop Mart continued with themed Labubu series. In July 2024 it launched the “Have a Seat” vinyl-plush line (V2) with seated Labubu charms. That year also saw seasonal and cross-character releases (e.g. Halloween “Magic of Pumpkin” Labubu, etc. from The Monsters series). According to reports, the medium-size plush Labubus – often sold as blind-box bag charms – have been the most popular, with each new themed series drawing tens of thousands of shoppers.
2025: In April 2025 Pop Mart launched the “Big Into Energy” series (V3) of Labubu vinyl-plush charms. (A “Let's Checkmate” series followed in early 2025 as well.) Also in June 2025, Pop Mart held the first official Labubu auction in Beijing – a 131 cm (4.3-ft) Labubu sculpture sold for ¥1.08M (~\$150K), setting a record. By mid-2025, Pop Mart had issued over 300 different Labubu figures, ranging from small blind-box charms to giant “mega” editions.

Labubu’s design has evolved but retains core features: a round, furry body, rabbit-like pointy ears, wide eyes and nine sharp teeth forming a mischievous grin. Variations include different facial expressions, colors and costumes, but the “ugly-cute” look remains consistent. (The blind-box format adds rarity: each series includes at least one ultra-rare “secret” Labubu variant that collectors scramble to find.)

Labubu plush figures are popular as bag charms and fashion accessories. For example, Pop Mart has promoted Labubu at fashion events (above, two Labubu keychains adorn a designer handbag).

Limited Editions and Collaborations

Pop Mart has released numerous special-edition Labubus and brand collaborations. For example, in late 2024 Pop Mart introduced The Monsters – Coca-Cola Series vinyl blind-boxes: Labubu and friends in ski-adventure outfits under a Coca-Cola theme. In early 2025 it launched a The Monsters × One Piece crossover: 13 blind-box figures where Labubu characters were reimagined as One Piece manga figures. Other exclusives include museum and retail tie-ins: Pop Mart sold a “Labubu’s Artistic Quest” series only at its Louvre museum store in Paris. Globally, Pop Mart has partnered with artists and retailers, such as a “Street Elf” Labubu series designed by a New York graffiti artist and a London-only Hamleys toy-store edition. (TechNode notes Pop Mart plans tie-ups with Disney and Universal as well, though specific figures have yet to be announced.) These limited drops – often in tiny production runs – add to Labubu’s collectible appeal and frequently sell out immediately.

Popularity and Cultural Impact

Labubu has become a viral sensation, especially in East and Southeast Asia, but is also spreading worldwide. The craze accelerated in 2024 when K-pop star Lisa (of Blackpink) was seen with Labubu toys (a giant plush and a keychain) on social media. Lisa’s endorsement triggered a fandom frenzy: within weeks Labubu was everywhere in Thailand (fans even flew to China to buy them), and Asian celebrities and fashionistas began collecting Labubu. (For instance, in the Philippines celebrities like Vice Ganda and Heart Evangelista proudly showed off Labubus.) Retailers saw chaotic scenes: news reports described customers literally brawling and “cutting in line” for each new Pop Mart Labubu drop. In Singapore and Hong Kong, limited figures resell for thousands of dollars, and local authorities have even warned about Labubu-related scams. In July 2024 a life-sized Labubu mascot toured Bangkok’s landmarks as part of a Thai tourism campaign, underscoring the toy’s pop-culture status in Thailand.

Labubu’s appeal has also reached the West. Pop Mart has opened Pop‑Ups in Los Angeles and London and collaborated with Western brands. U.S. celebrities like Rihanna and Dua Lipa have been spotted carrying Labubu charms, and British footballer David Beckham even showcased a Labubu on his bag. Streetwear and designer communities note that Labubu, like Jellycat or Sanrio characters, blurs the line between toy and fashion charm. Forbes and Reuters both report that #Labubu has exploded on TikTok, with millions of hashtag views as influencers and fans worldwide unbox and display their Labubu collections. TechNode sums up Labubu’s reach: it “spans from China to Europe and from the US to Southeast Asia,” symbolizing Chinese pop culture’s growing global influence.

Enthusiasts queue at Pop Mart stores to buy Labubu releases. The craze for these blind-box toys has led to long lines and chaotic launches worldwide.

Collector Market and Resale Trends

Labubu’s collectibility has driven wild secondary-market prices. By official pricing, most blind-box Labubu figures sell for ¥50–¥200 (roughly US\$7–\$30) per box, depending on size. Larger plush dolls (about 15 inches tall) retail around ¥600 (∼\$85). However, scarcity fuels resellers: on eBay and resale platforms, rare Labubus routinely go for thousands of dollars. Forbes reported some fans listing limited editions for up to \$7,000 (e.g. a Vans collaboration piece), and StockX sales of special Labubu figures (like “Happy Halloween” editions) have fetched over \$3,000. Even entry-level Labubus can spike above retail when in high demand, prompting one investor to call it the new “Stanley Cup” craze.

The collector market hit new highs at official auctions. In June 2025, a 4.3-foot Labubu statue sold for ¥1.08 million (about \$150,000), setting a record price for any blind-box toy. (Reuters notes this was Labubu’s first dedicated auction.) In contrast, older or more common Labubu editions have sometimes been offloaded by collectors at a loss as hype shifts. Counterfeits are also rampant: bootleg Labubu knock-offs (derisively called “Lafufus”) flood Asian markets and online shops, sometimes sparking interest for their bizarre designs.

Collectors remain divided on the trend’s longevity, but for now Labubu continues to sell out rapidly. Pop Mart even reported that Labubu sales helped crash its online store during drops, and the brand’s interim report showed the “Monsters” line grossed RMB 6.3 billion (∼\$870 million) in just the first half of 2024. In sum, Labubu has transformed from an obscure art toy into a global phenomenon – its pointy-eared grin proving as marketable as it is endearing.

Sources: Verified information from Pop Mart and media reports (The New York Times, Reuters, Business Insider, Forbes, CNA, etc.) are cited above. All details are drawn from these connected sources, unless otherwise noted.