DeepFeather
中文

Method · public rules

Not a one-line “AI can.” A review you can inspect.

DeepFeather isolates the job a product is actually hired to do, then separates what code can reproduce from what a person can rely on—and what the paid product still defends. Every product gets its own page; the evidence label tells you how far the conclusion has really gone.

Method last updated: 2026-08-26

1,034independent product verdicts
322English pages passing the index gate
150Chinese pages passing the index gate
01

Three verdicts for three different realities

YES

The core job can become a narrower personal tool. This is not a claim of full product parity.

KINDA

The core loop is buildable, while collaboration, data, integrations, reliability, or upkeep remain real work.

NOT REALLY

The decisive value comes from a network, licensed content, hardware, trust, or ongoing operations—not interface code.

02

Evidence does not collapse into one badge

Higher tiers are closer to a usable replacement. Counts come directly from the current catalog.

  1. 01Built & verified0

    A reviewable repository, date, and check result exist.

  2. 02Build check failed0

    A real attempt was made but did not pass its acceptance criteria.

  3. 03Human-reviewed blueprint197

    Scope and prompt were reviewed, but the build has not been run.

  4. 04Catalog estimate837

    A structured judgment without real build evidence yet.

03

What every product page examines

  1. 01

    Define the core job

    Judge the repeated user task—not an entire brand, market, and team compressed into one prompt.

  2. 02

    Check public pricing

    Prefer an official source, plan, billing unit, and checked date. Keep uncertainty visible when pricing moves.

  3. 03

    Find mature prior art

    Look for open-source and existing alternatives first. A good tool that already exists often beats generating from zero.

  4. 04

    Draw the build boundary

    State the buildable slice, remaining human work, and what disappears when the subscription goes away.

  5. 05

    Assign evidence honestly

    Only a real build is “verified.” A reviewed prompt is never presented as a finished product.

  6. 06

    Correct continuously

    Products, prices, and model capabilities change. Pages expose sources and dates and accept public corrections.

04

Indexing policy

Every product page is open for indexing only after it passes the public quality gate.

All 1,034 catalog products remain browsable. 322 English pages and 150 Chinese pages currently pass the evidence, source, workflow, moat, prompt, and residue checks. Catalog estimates that do not pass remain accessible with noindex and stay out of the sitemap.

Editorial independence

Sponsorship cannot buy a verdict, rank, moat judgment, or copy change. Commercial placements must remain visibly separate from editorial content.

Found an outdated price, fact, or judgment?

Submit a public correction ↗ · or email hello@deepfeather.com

Browse every product →