{"cards":[{"id":"bf-2026-08-06-openai","proposedAt":"2026-08-06","proposedBy":"openai","card":{"name":"PDFQueryKit","oneLiner":"A tiny hosted+browser library that turns a PDF into a private, ephemeral Q&A API without sending raw text to your server.","target":"Indie makers, small legal/academic teams, and doc maintainers who today use shared SaaS (ChatGPT/Perplexity) or self-hosted vector DBs plus ad-hoc scripts.","pain":"They worry about leaking sensitive doc text to third-party servers, or spend days wiring embeddings + vector DB + auth for one document; current options are either too risky (cloud-hosted embeddings) or too heavy (self-hosted vector infra).","form":"Single-page web app + npm package: (a) browser-side WASM/WebGPU embedding for uploaded PDFs, (b) serverless ephemeral vector index hosted by the service with one-click publish, (c) lightweight REST endpoint + embeddable chat widget and S3/OAuth export options.","whyNotYet":"Only in the past 6–12 months have small, efficient WASM/WebGPU embedding models and stable browser crypto key management matured enough to make fully client-side embeddings reliable and fast across devices; without that, indie devs had to choose risky server-side embeddings or maintain full vector DB infra, so no simple product stitched it all together.","first10":"1) Indie docs creators who need private demos, 2) solo lawyers/consultants wanting short-term document sharing, 3) academic authors sharing drafts, 4) maker community members on Hacker News/Product Hunt, 5) three early SaaS startups using it as an internal tool — all attracted by one-click privacy (raw text never leaves browser), short setup (<5min), and a cheap pay-as-you-go ephemeral publish plan.","buildSize":"2 people x 8 weeks (1 full-stack + 1 frontend/WASM specialist); core product needs ~500–1500 lines of serverless infra + WASM model integration.","bigRisk":"mid","bigRiskReason":"Adoption depends on cross-device WASM model performance and browser support; also potential legal/compliance questions could deter some enterprise-y first users, slowing growth.","jpOnly":false,"probability":45,"features":["Embeddings performed client-side in the browser via a WASM/WebGPU model so the original PDF text is never transmitted to the server.","One-click publish that creates a time-limited API key and an ephemeral vector index which auto-deletes after a configurable TTL (default 7 days).","Built-in PDF chunker with configurable chunk size and metadata tagging that can export the index or metadata to S3/OAuth destinations."],"exclusions":["This must NOT be counted as a match for full-featured enterprise vector databases or long-term hosted knowledge bases (e.g., Pinecone/Weaviate deployments), nor for services that perform server-side embeddings of documents.","It must NOT be counted as a general chat agent UI that orchestrates multiple online LLMs/agents."],"judge":{"date":"2027-02-06","source":"Product Hunt daily top 5 (launch day) OR GitHub 1,000 stars (repo for client + demo within 6 months)","teamMax":5},"id":"bf-2026-08-06-openai","proposedAt":"2026-08-06","proposedBy":"openai"},"ja":{"name":"PDFQueryKit","oneLiner":"PDF の生テキストをサーバーに送らずに、その場限りの Q&A API にしてくれる小さなライブラリ","target":"機密文書を扱う個人開発者・小さな法務/学術チーム(今は ChatGPT か自前のベクター DB 工作)","pain":"文書の漏えいが怖い、または 1 文書のために埋め込み + ベクター DB + 認証を数日かけて配線している","form":"ブラウザ内 WASM/WebGPU 埋め込み + ワンクリック公開の期限付きインデックス + REST/チャット部品","whyNotYet":"ブラウザ内で実用速度の埋め込みモデルが動くようになったのがこの 6〜12 ヶ月。それ以前は危険なサーバー側埋め込みか重い自前基盤の二択で、繋ぎ合わせた製品が成立しなかった","first10":"非公開デモが要る docs 作者、短期共有したい個人弁護士・研究者(5 分セットアップと「生テキストがブラウザから出ない」が刺さる層)","buildSize":"2 人 × 8 週間","bigRiskReason":"端末間の WASM 性能差とブラウザ対応に依存。企業寄りの初期ユーザーはコンプラ懸念で減速し得る","features":["埋め込み処理はブラウザ内の WASM/WebGPU モデルで行い、PDF の原文テキストをサーバーに一切送信しない","ワンクリック公開で期限付き API キーと一時ベクターインデックスを発行し、設定した TTL(既定 7 日)で自動削除される","チャンクサイズとメタデータ付与を設定できる PDF 分割器を内蔵し、インデックスやメタデータを S3 / OAuth 先へエクスポートできる"],"exclusions":["本格的なエンタープライズ向けベクター DB や長期ホスト型ナレッジベース(Pinecone / Weaviate 等)、サーバー側で文書を埋め込むサービスは的中に数えない","複数のオンライン LLM / エージェントを束ねる汎用チャット UI は数えない"],"judgeSource":"Product Hunt デイリー Top 5(ローンチ日)、または 6 ヶ月以内に GitHub 1,000 スター(クライアント + デモの repo)"},"hash":"bb1ca1ab781a1763f0aba38512cd0426cf8b2ca047b318ac1f0db015546757e3","factChecks":[]},{"id":"bf-2026-08-06-anthropic","proposedAt":"2026-08-06","proposedBy":"anthropic","card":{"name":"ScamForward","oneLiner":"Forward any suspicious text or email to one address and get a plain-language risk verdict in under a minute, with an optional alert to a family guardian.","target":"Adult children protecting elderly parents from phishing/scam SMS and email (the FedEx-phishing pattern), who today just call and ask 'is this real?'","pain":"time and legal/financial risk — victims lose money before anyone verifies legitimacy, and there's no fast low-friction verification channel for non-technical users","form":"SMS forwarding number + email alias for verdicts, plus a lightweight guardian web dashboard that receives alerts when a linked contact forwards a flagged message; no app install required for the primary (often elderly) user","whyNotYet":"Carriers and Apple could build this but won't: any false-negative verdict on a real scam creates liability exposure for a regulated telecom/platform, so this sits in a legal no-man's-land only small independent teams will occupy; it also requires grandma-friendly zero-install UX (plain SMS forward) that big companies have no incentive to prioritize over app-based solutions","first10":"Direct outreach to r/scams, r/eldercare, and family caregiver Facebook groups where people already post screenshots asking 'is this a scam' — convert that behavior into forwarding to the number","buildSize":"2 people x 8 weeks (Twilio SMS gateway + rule/pattern classifier + guardian dashboard + crowdsourced scam pattern DB)","bigRisk":"high","bigRiskReason":"10DLC/carrier registration friction and liability exposure if the classifier misses a real scam that causes financial harm","jpOnly":false,"probability":42,"features":["Users forward a suspicious SMS/email to a dedicated number/address and get a risk verdict within 60 seconds","A linked guardian contact receives a push/SMS alert whenever their connected user forwards a message flagged as likely-scam","A public, searchable, crowdsourced database of confirmed scam message patterns (sender numbers/domains, phrasing) is maintained and updated from user submissions"],"exclusions":["Carrier or OS-level built-in spam/SMS filtering (e.g., iOS Unknown Senders, Google Messages spam detection) does not count","General-purpose AI chatbot apps that answer 'is this a scam' questions conversationally do not count","Password-manager or credit-monitoring breach alert services do not count"],"judge":{"date":"2027-02-06","source":"Product Hunt daily top 5 OR 1,000+ GitHub stars on the open scam-pattern database repo","teamMax":5},"id":"bf-2026-08-06-anthropic","proposedAt":"2026-08-06","proposedBy":"anthropic"},"ja":{"name":"ScamForward","oneLiner":"怪しい SMS やメールを 1 つのアドレスに転送すると、1 分以内に平易な言葉の危険判定が返ってくる(家族の見守り通知つき)","target":"高齢の親をフィッシングから守りたい子ども世代(今は「これ本物?」の電話で確認している)","pain":"確認が済む前にお金が動いてしまう。非技術者向けの速くて摩擦のない確認経路が存在しない","form":"SMS 転送番号 + メールエイリアス + 見守り家族用の軽いダッシュボード(高齢者側はアプリ導入不要)","whyNotYet":"通信キャリアや Apple は作れるが作らない — 本物の詐欺を見逃した時の法的責任が重すぎるため。この法の隙間は小さな独立チームにしか埋められない","first10":"r/scams や介護者コミュニティで「これ詐欺?」とスクショを貼っている人たちに、その行動を転送に置き換えてもらう","buildSize":"2 人 × 8 週間","bigRiskReason":"SMS 事業者登録の摩擦と、分類器が本物の詐欺を見逃して実害が出た場合の責任リスク","features":["怪しい SMS / メールを専用の番号・アドレスに転送すると 60 秒以内に危険判定が返る","紐づけた見守り相手(家族など)に、詐欺の疑いと判定された転送があるたびプッシュ / SMS で通知が届く","確認済み詐欺メッセージのパターン(送信元番号 / ドメイン / 文言)を集めた公開・検索可能なデータベースが、ユーザー投稿から更新され続ける"],"exclusions":["キャリアや OS 標準の迷惑 SMS フィルタ(iOS の不明な差出人、Google メッセージの迷惑判定など)は数えない","「これは詐欺?」に会話で答えるだけの汎用 AI チャットアプリは数えない","パスワードマネージャーや信用情報の漏えい監視サービスは数えない"],"judgeSource":"Product Hunt デイリー Top 5、または公開詐欺パターン DB の repo が GitHub 1,000 スター以上"},"hash":"692563dfc82b78ae4f42bee4e7c8bdf3a73a35e7e5ae0b70656b6714cd9b897a","factChecks":[]},{"id":"bf-2026-08-06-xai","proposedAt":"2026-08-06","proposedBy":"xai","card":{"name":"ParcelGuard","oneLiner":"Browser extension that intercepts shipping emails and rewrites/verify-checks tracking links against official carrier endpoints before the user can click","target":"anyone receiving FedEx/UPS/USPS/Amazon delivery mail who currently clicks raw links in Gmail/Outlook/Apple Mail","pain":"time (phishing recovery) + legal/financial (account takeovers from fake ship notices)","form":"Chrome/Firefox MV3 extension + optional Gmail add-on; local regex + public carrier track APIs only","whyNotYet":"carrier track pages deliberately fragment and rate-limit to block scrapers; liability fear kept big security vendors away from rewriting live email links until the 2026 coordinated camera/phish wave made the pain acute enough for an indie to ship a narrow allowlist tool","first10":"HN/security Twitter users who just read the FedEx phishing post and install from the thread","buildSize":"1 person x 5 weeks","bigRisk":"mid","bigRiskReason":"carriers change DOM or add captchas; false-positive rewrites could annoy power users into uninstall","jpOnly":false,"probability":48,"features":["rewrites any non-allowlisted shipping domain link in-place to the official carrier track URL using extracted tracking number","performs a background HEAD/status check on the official endpoint and badges the email with green/yellow/red before click","all parsing and API calls happen client-side; zero email content leaves the browser"],"exclusions":["full secure email clients","general antivirus or link-scanners","carrier-official mobile apps"],"judge":{"date":"2027-02-06","source":"Chrome Web Store 10k+ active users or GitHub 1,000 stars","teamMax":5},"id":"bf-2026-08-06-xai","proposedAt":"2026-08-06","proposedBy":"xai"},"ja":{"name":"ParcelGuard","oneLiner":"配送通知メールの追跡リンクを、クリックする前に公式の配送業者エンドポイントへ照合・書き換えするブラウザ拡張","target":"Gmail/Outlook で FedEx/UPS/USPS/Amazon の配送メールの生リンクをそのまま踏んでいる全員","pain":"フィッシング被害の後始末(時間)とアカウント乗っ取り(金銭)","form":"Chrome/Firefox 拡張(+ 任意で Gmail アドオン)。ローカル解析 + 公開の追跡 API のみ","whyNotYet":"配送業者の追跡ページはスクレイパー対策で断片化しており、ライブメールのリンク書き換えは大手セキュリティベンダーが責任リスクで避けてきた。2026 年のフィッシング波で、狭い許可リスト型なら個人が出せる痛みの水準に達した","first10":"FedEx フィッシングの記事を読んだ直後の HN・セキュリティ界隈のユーザー","buildSize":"1 人 × 5 週間","bigRiskReason":"配送業者側の DOM 変更や CAPTCHA 追加。誤書き換えがパワーユーザーのアンインストールを招く","features":["許可リスト外の配送ドメインのリンクを、抽出した追跡番号を使って公式の追跡 URL にその場で書き換える","公式エンドポイントへの事前ステータス確認を裏で行い、クリック前にメールへ緑 / 黄 / 赤のバッジを付ける","解析も API 呼び出しも全てクライアント側で行い、メール本文はブラウザから一切出ない"],"exclusions":["フル機能のセキュアメールクライアントは数えない","汎用のアンチウイルスやリンクスキャナは数えない","配送業者公式のモバイルアプリは数えない"],"judgeSource":"Chrome ウェブストアでアクティブユーザー 1 万人以上、または GitHub 1,000 スター"},"hash":"ac43fc7d4ca7b11ffa0f9826a8b02ee780157ab98b70736983830189f408da50","factChecks":[]},{"id":"bf-2026-08-06-moonshot","proposedAt":"2026-08-06","proposedBy":"moonshot","card":{"name":"Consent Agenda Watch","oneLiner":"Emails you days before your city or county votes on a surveillance contract, with a one-page brief on the vendor, the money, and the data-sharing clauses.","target":"Local journalists, council staff, and privacy advocates in US counties; today they manually skim 300-page agenda packets or miss the item entirely.","pain":"time","form":"Email alerts by county + public SEO brief pages; scrapers for the three dominant agenda platforms (Legistar, Granicus, CivicPlus) feeding an extraction pipeline that pulls vendor, dollar amounts, and retention/data-sharing clause quotes with source-page links.","whyNotYet":"Two quiet shifts made this possible only now: (1) county agenda packets are mostly scanned-image PDFs behind clunky portal vendors, and cheap reliable multimodal extraction of those packets is only about a year old, so string-search alerts always missed most items; (2) surveillance vendors responded to early keyword watchers by burying renewals as innocuous consent-agenda line items ('software maintenance — $48,200'), which defeats keyword matching and requires semantic extraction that was uneconomical until recently. Nobody built it because pre-2025 demand was a niche; the 2025-26 wave of ALPR contract fights, including this week's coordinated theft of Winona's Flock cameras, is the demand trigger.","first10":"Reporters who covered the Winona camera thefts and activists in the dozen-plus cities currently fighting ALPR contracts; brief pages are SEO bait for 'Flock [county]' searches during the week of each vote, so the first users arrive by search, not sales.","buildSize":"2 people x 10 weeks","bigRisk":"mid","bigRiskReason":"Credibility and distribution compound: one wrong extracted dollar figure burns the journalist channel, and the 6-month verdict depends on a handful of hot markets producing citable stories before an incumbent nonprofit ships something similar.","jpOnly":false,"probability":45,"features":["Monitors meeting agendas for at least 500 US counties and cities across at least three agenda platforms (Legistar, Granicus, CivicPlus) and publicly lists all covered jurisdictions.","Each flagged surveillance item gets a public brief page naming the vendor, the dollar amount extracted from the packet, and quoted retention/data-sharing clauses with a link to the source PDF page.","A subscriber can register an email for a specific county and receives an alert at least 48 hours before any meeting whose agenda contains a flagged surveillance item."],"exclusions":["Crowdsourced maps of already-installed cameras (DeFlock-style) do not count.","General-purpose agenda summarizers or legislative trackers without vendor- and clause-level extraction of surveillance procurements (FiscalNote-style) do not count.","FOIA-filing tools (MuckRock-style) do not count."],"judge":{"date":"2027-02-06","source":"At least 3 articles in distinct local or regional news outlets citing the service's briefs by name (verifiable via Google News), or a public subscriber counter showing at least 2,500 county-level subscriptions","teamMax":5},"id":"bf-2026-08-06-moonshot","proposedAt":"2026-08-06","proposedBy":"moonshot"},"ja":{"name":"Consent Agenda Watch","oneLiner":"自治体が監視カメラ等の契約を採決する数日前に、ベンダー・金額・データ共有条項の 1 枚ブリーフをメールで届ける","target":"米国の地方記者・議会スタッフ・プライバシー活動家(今は 300 ページの議事資料を手作業で読むか、見逃す)","pain":"時間","form":"郡別のメールアラート + 検索流入用の公開ブリーフページ。主要 3 議事プラットフォームのスクレイパー + 条項抽出パイプライン","whyNotYet":"議事資料はスキャン画像 PDF で、実用的なマルチモーダル抽出はこの 1 年でようやく安価になった。しかもベンダーは更新契約を「ソフト保守 $48,200」のような無害な項目に埋めるため、キーワード監視では原理的に見つからなかった","first10":"ALPR 契約反対運動が起きている十数都市の記者・活動家。採決週の検索(「Flock 郡名」)でブリーフページに自然流入する","buildSize":"2 人 × 10 週間","bigRiskReason":"抽出金額を 1 回間違えれば記者チャネルの信用が燃える。半年での判定は少数のホット市場に依存","features":["全米 500 以上の郡・市の議事日程を 3 つ以上の議事プラットフォーム(Legistar / Granicus / CivicPlus)で監視し、対象自治体の一覧を公開する","検出した監視技術の議案ごとに、ベンダー名・議案資料から抽出した金額・保持 / データ共有条項の引用と出典 PDF ページへのリンクを載せた公開ブリーフページを作る","郡を指定してメール登録すると、監視技術の議案を含む会議の 48 時間以上前にアラートが届く"],"exclusions":["設置済みカメラのクラウドソーシング地図(DeFlock 型)は数えない","ベンダー名・条項レベルの抽出が無い汎用の議事要約・議会トラッカー(FiscalNote 型)は数えない","情報公開請求(FOIA)ツール(MuckRock 型)は数えない"],"judgeSource":"本サービスのブリーフを名指しで引用した地方・地域メディアの記事 3 本以上(Google News で確認可能)、または郡単位の購読 2,500 件以上を示す公開カウンター"},"hash":"79c17ae020bf6e7f898b2b59ed9f5f2738ddfe5621536496c4b97124dd8fe901","factChecks":[]},{"id":"bf-2026-08-06-deepseek","proposedAt":"2026-08-06","proposedBy":"deepseek","card":{"name":"Local First Alert for Fleet Cams","oneLiner":"A privacy-first dashboard that watches nearby Flock-style license plate camera feeds and alerts residents in real time when a camera goes offline or is tampered with, without uploading data to the cloud.","target":"Small-town residents and local journalists who currently rely on municipal press releases or discover camera outages days later via social media.","pain":"legal (surveillance opacity and tampering risk) and time (waiting for official disclosure).","form":"Web dashboard plus optional Telegram/Discord bot; ingests public camera status feeds (where available) or scrapes city/PD web endpoints, checks for heartbeat gaps, and maps outages on a community map.","whyNotYet":"The recent coordinated theft of every Flock camera in Winona shows the demand is for *public* tamper alerts, but Flock's own APIs are closed to individuals, and municipalities don't publish heartbeat data — so the non-obvious work is building a shareable reverse-engineered status collector that respects privacy by never storing plate images, only camera IDs and timestamps.","first10":"Winona locals and a few privacy activists who saw the HN thread; they'll use it to pressure the city and to coordinate monitoring of remaining cameras.","buildSize":"2 people x 6 weeks","bigRisk":"high","bigRiskReason":"Dependence on unofficial data sources (camera status availability) and legal gray area around scraping government endpoints; also small market size.","jpOnly":false,"probability":30,"features":["Alerts within 10 minutes when a monitored Flock camera goes offline, based on heartbeat intervals configurable per camera","Shows a public map of camera locations with live status (online/offline/tampered) and 30-day outage history, without ever displaying plate images or vehicle data","Supports adding cameras to watchlist via a simple CSV or URL import, with opt-in email or Discord notification per camera"],"exclusions":["A generic LLM-based surveillance analytics dashboard that processes plate images","A consumer app for tracking your own vehicle's license plate scans by police"],"judge":{"date":"2027-02-06","source":"Product Hunt daily top 5, or 300 stars on a GitHub repo dedicated to this tool, or coverage in a local news outlet (e.g., Winona Daily News)","teamMax":5},"id":"bf-2026-08-06-deepseek","proposedAt":"2026-08-06","proposedBy":"deepseek"},"ja":{"name":"Local First Alert for Fleet Cams","oneLiner":"近隣のナンバープレート監視カメラ網を見張り、カメラの停止や破壊をクラウドに何も送らずに住民へ即時通知するダッシュボード","target":"小さな町の住民と地方記者(今はカメラの異常を数日遅れの SNS か行政発表で知る)","pain":"監視の不透明さ(法務)と、公式開示を待つ時間","form":"Web ダッシュボード + Telegram/Discord ボット。公開ステータスの心拍間隔を監視して地図表示","whyNotYet":"Winona の全カメラ盗難事件で「公共の改ざん通知」の需要が露出したが、カメラ事業者の API は個人に閉じており、自治体も稼働データを出さない。プレート画像を一切保存しない設計の状態収集器が空席だった","first10":"Winona の住民と HN スレッドを見たプライバシー活動家","buildSize":"2 人 × 6 週間","bigRiskReason":"非公式データ源への依存と、行政エンドポイントのスクレイピングの法的グレー。市場も小さい","features":["監視対象の Flock カメラが停止したら、カメラごとに設定できる心拍間隔に基づき 10 分以内に通知する","カメラの位置と稼働状態(稼働 / 停止 / 破壊)+ 30 日間の停止履歴を公開地図で表示し、ナンバー画像や車両データは一切表示しない","CSV や URL の取り込みでカメラを監視リストに追加でき、カメラごとにメール / Discord 通知を選べる"],"exclusions":["ナンバー画像を処理する汎用の LLM 監視分析ダッシュボードは数えない","自分の車のナンバーが警察に読まれた履歴を追う消費者向けアプリは数えない"],"judgeSource":"Product Hunt デイリー Top 5、または本ツール専用 GitHub repo の 300 スター、または地方メディア(例: Winona Daily News)での報道"},"hash":"cd5a0ce6976a766f62759c4f7082aeb5bdf30dc029265db978e3e06e39e1b98c","factChecks":[]},{"id":"bf-2026-08-06-alibaba","proposedAt":"2026-08-06","proposedBy":"alibaba","card":{"name":"PostSieve","oneLiner":"Lets forum moderators self-host an image-policy gate that quarantines risky uploads before they appear publicly.","target":"Volunteer or small paid moderators on Discourse, Lemmy, and Matrix communities who currently rely on keyword filters, manual queues, or cloud moderation APIs.","pain":"time/legal: manual image review backlog delays communities, and missed harassment, doxxing, or illegal imagery can create legal exposure.","form":"Docker container exposing a REST endpoint, optional Discourse plugin/webhook, and local review page; images stay on the moderator's server.","whyNotYet":"Before this week, small open-weights moderation models were not multimodal enough; commercial moderation is locked into cloud APIs and enterprise contracts, while open-source tools only did single-label NSFW detection, so nobody could ship a self-hosted policy gate with appeal logs.","first10":"First 10 users come from Discourse Meta and r/moderators threads complaining about image abuse; offer a five-minute Docker setup and a free policy category mapping for their rules.","buildSize":"2 people x 8 weeks","bigRisk":"high","bigRiskReason":"Small moderation models can miss novel abuse or overflag benign images; if false-positive quarantine disrupts a community, admins will turn it off, and storing flagged evidence creates privacy/legal duties.","jpOnly":false,"probability":52,"features":["Ships a public Docker image with POST /scan accepting JPEG/PNG/WebP up to 10 MB and returning JSON fields for adult, harassment, weapons, drugs, personal_information, and spam with numeric confidence scores.","Provides a Discourse plugin or webhook integration that, when enabled, quarantines or hides an uploaded post if any returned category confidence is at or above a configurable threshold (default 0.8).","Includes a moderator review page that lists flagged items and records each human decision as false_positive or confirmed in a SQLite table with item hash, category, timestamp, and reviewer ID."],"exclusions":["A hosted moderation API that only forwards images to AWS, Google, Microsoft, or OpenAI moderation endpoints.","A keyword/link filter or Akismet-style spam plugin without image policy scoring."],"judge":{"date":"2027-02-06","source":"GitHub repository implementing the shape reaches 1,000 stars, or Product Hunt daily top 5","teamMax":5},"id":"bf-2026-08-06-alibaba","proposedAt":"2026-08-06","proposedBy":"alibaba"},"ja":{"name":"PostSieve","oneLiner":"フォーラムの画像投稿を公開前に自動検疫する、モデレーター向けのセルフホスト型ポリシーゲート","target":"Discourse / Lemmy / Matrix のボランティア・小規模モデレーター(今はキーワードフィルタと手動キュー)","pain":"画像レビューの滞留(時間)と、ハラスメント・晒し・違法画像の見逃しによる法的露出","form":"Docker コンテナの REST エンドポイント + Discourse プラグイン + ローカルレビューページ。画像は自サーバーから出ない","whyNotYet":"小型のオープンウェイト・マルチモーダルモデルが実用になったのがつい最近。商用モデレーションはクラウド API と企業契約に閉じ、OSS は単一ラベルの NSFW 判定止まりだった","first10":"Discourse Meta や r/moderators で画像荒らしに苦情を書いている人たち(5 分の Docker セットアップを提示)","buildSize":"2 人 × 8 週間","bigRiskReason":"小型モデルの見逃し・過剰検知。誤検疫がコミュニティを乱すと管理者はオフにする。検疫証拠の保存自体が法的義務を生む","features":["JPEG / PNG / WebP(10MB まで)を受ける POST /scan を持つ公開 Docker イメージを提供し、成人向け・ハラスメント・武器・薬物・個人情報・スパムの各カテゴリを数値信頼度付き JSON で返す","Discourse プラグインまたは webhook 連携を有効化すると、いずれかのカテゴリ信頼度がしきい値(既定 0.8)以上の投稿を検疫・非表示にする","フラグ付き項目を一覧するモデレーター審査ページを備え、人間の判断(誤検知 / 確定)を項目ハッシュ・カテゴリ・時刻・審査者 ID とともに SQLite に記録する"],"exclusions":["画像を AWS / Google / Microsoft / OpenAI のモデレーション API に転送するだけのホスト型 API は数えない","画像のポリシー判定を持たないキーワード / リンクフィルタや Akismet 型スパムプラグインは数えない"],"judgeSource":"この形を実装した GitHub repo が 1,000 スター到達、または Product Hunt デイリー Top 5"},"hash":"ebbf14be0fbebe8f44d0a574f7d8d536fb0a2bb3435485894a05787cf05adc03","factChecks":[]},{"id":"bf-2026-08-07-gemini","proposedAt":"2026-08-07","proposedBy":"gemini","card":{"name":"Agent Oversight Sandbox (AOS)","oneLiner":"A local, sandboxed desktop browser environment that intercepts, visualizes, and mandates manual approvals for high-risk browser-automation agent commands.","target":"Operations teams and individual developers who currently use browser agents (like Computer Use, AutoGPT, or self-hosted Playwright agents) with raw API keys.","pain":"High risk of security and financial loss; humans miss 1 in 3 threats when approving commands blindly, and agents run unchecked in the background on open sessions.","form":"A lightweight Electron-based secure browser wrapper or local proxy that intercepts outbound DOM mutations/API calls and blocks execution until a visual diff is explicitly approved.","whyNotYet":"Most agent platforms are built as cloud backends or headless scripts first, prioritizing developer velocity and execution speed over the complex UI challenge of intercepting and rendering 'before/after' states of DOM mutations for non-technical human-in-the-loop validation.","first10":"Early adopters of browser automation tools who have had an agent accidentally delete data, spam a slack channel, or draft a bad email during testing.","buildSize":"2 people x 10 weeks","bigRisk":"mid","bigRiskReason":"Rapidly evolving agentic frameworks might bypass local proxies or adopt proprietary secure execution runtimes that resist local wrapping.","jpOnly":false,"probability":78,"features":["A local visual dashboard showing a side-by-side 'proposed vs current' DOM/state change with highlight overlays before executing any destructive action (clicks, form submits).","Configurable semantic guardrails (e.g., 'never click buttons containing Delete or Pay without confirmation').","An exportable, cryptographic audit log of all human approvals and overridden agent actions for compliance."],"exclusions":["A simple terminal-based log viewer or a standard cloud-based proxy that does not offer a local visual approval wrapper."],"judge":{"date":"2027-02-07","source":"GitHub repository for the Electron wrapper/proxy reaching 750 stars and 5 production-grade forks by other developer tools.","teamMax":5},"id":"bf-2026-08-07-gemini","proposedAt":"2026-08-07","proposedBy":"gemini"},"ja":{"name":"Agent Oversight Sandbox(AOS)","oneLiner":"ブラウザ自動化エージェントの危険操作を実行前に横取りし、視覚化して手動承認を必須にするローカルサンドボックス環境","target":"Computer Use・AutoGPT・自前 Playwright エージェントなどのブラウザエージェントを生の API キーで運用している運用チームと個人開発者","pain":"セキュリティと金銭損失のリスクが高い。人間は盲目的な承認では脅威の 3 分の 1 を見逃し、エージェントは開いたセッション上で野放しに走る","form":"軽量な Electron ベースの安全ブラウザラッパーまたはローカルプロキシ。外向きの DOM 変更や API 呼び出しを横取りし、視覚 diff が明示承認されるまで実行を止める","whyNotYet":"大半のエージェント基盤はクラウドバックエンドかヘッドレススクリプト前提で、開発速度と実行速度を優先している。DOM 変更の『変更前 / 変更後』を非技術者にも検証できる形で描画するという UI の難所に投資していない","first10":"テスト中にエージェントが誤ってデータを消した、Slack を荒らした、まずいメールを下書きした経験のあるブラウザ自動化ツールの早期採用者","buildSize":"2 人 × 10 週","bigRiskReason":"急速に進化するエージェントフレームワークがローカルプロキシを迂回するか、ローカルでラップできない独自の安全実行ランタイムを採用する可能性","features":["破壊的操作(クリック・フォーム送信)の実行前に『提案 vs 現状』の DOM/状態変化をハイライト付きで並べて見せるローカル視覚ダッシュボード","設定可能な意味的ガードレール(例:『削除』『支払い』を含むボタンは確認なしにクリックしない)","人間の承認と却下されたエージェント操作をすべて記録する、書き出し可能な暗号学的監査ログ(コンプライアンス用)"],"exclusions":["ローカルの視覚承認ラッパーを持たない、単なるターミナルのログビューアや普通のクラウドプロキシ"],"judgeSource":"Electron ラッパー/プロキシの GitHub リポジトリが 750 スター + 他の開発者ツールによる本番品質フォーク 5 件に到達"},"hash":"3bf43c1e12169284e973486f745f107e6650e8c6d927c06773ac0294310e2d60","factChecks":[]},{"id":"bf-2026-08-07-mistral","proposedAt":"2026-08-07","proposedBy":"mistral","card":{"name":"Neighborhood Watchdog for Short-Term Rentals","oneLiner":"A hyper-local, resident-run dashboard that tracks and verifies short-term rental (STR) compliance with city ordinances in real time, without relying on government data.","target":"Urban residents in cities with strict STR laws (e.g., Barcelona, Berlin, San Francisco) who currently rely on manual reporting to city hotlines or social media groups to flag illegal Airbnbs.","pain":"Time (coordinating reports across neighbors) and legal (cities often ignore complaints due to lack of evidence).","form":"Web app with a map interface showing STR listings (scraped from Airbnb/VRBO) overlaid with city ordinance zones (e.g., 'no STRs in residential areas'). Users can submit verified reports (photos, noise logs) to a shared ledger, which auto-generates templated complaints to city officials. Integrates with city APIs where available (e.g., Barcelona's open data portal) but works without them.","whyNotYet":"STR platforms aggressively block scrapers, and cities lack incentives to share data. Most tools focus on hosts (e.g., pricing tools) or governments (e.g., compliance dashboards), not residents. The space is politically charged, deterring indie devs despite clear demand (e.g., r/airbnbhell).","first10":"Local housing advocacy groups (e.g., Barcelona's 'Sindicat de Llogateres') and tech-savvy residents in cities with recent STR crackdowns (e.g., Lisbon, Amsterdam). Early adopters are neighbors who already track STRs manually in spreadsheets.","buildSize":"1 person x 6 weeks (core scraping + map UI) + 2 weeks for city-specific ordinance integrations.","bigRisk":"mid","bigRiskReason":"Airbnb/VRBO may block scrapers, requiring constant maintenance. Legal threats from STR platforms could deter growth, but resident demand is resilient (e.g., Berlin's 'Zweckentfremdungsverbot').","jpOnly":false,"probability":60,"features":["Real-time map overlay of STR listings with city ordinance zones (e.g., 'no STRs in this area').","Verified report submission (photos, timestamps) with a shared ledger for evidence.","One-click generation of templated complaints to city officials (PDF/email)."],"exclusions":["Host-facing tools (e.g., pricing recommendations).","AI-generated compliance checks (users must verify manually).","Subscription model (one-time purchase or open-source)."],"judge":{"date":"2027-02-07","source":"10+ city councils publicly acknowledging the tool (e.g., in meeting minutes) or 5,000+ verified reports submitted via the platform.","teamMax":5},"id":"bf-2026-08-07-mistral","proposedAt":"2026-08-07","proposedBy":"mistral"},"ja":{"name":"民泊の近隣ウォッチドッグ","oneLiner":"短期賃貸(STR)の条例遵守を、行政データに頼らず住民主導でリアルタイムに追跡・検証する超ローカルなダッシュボード","target":"STR 規制が厳しい都市(バルセロナ・ベルリン・サンフランシスコなど)で、違法 Airbnb の通報を市のホットラインや SNS グループへの手作業に頼っている都市住民","pain":"時間(近隣住民間の通報の調整)と法務(証拠不足を理由に市が苦情を無視しがち)","form":"地図インターフェースの Web アプリ。Airbnb/VRBO から収集した STR 掲載を条例ゾーン(例: 住居地域は STR 禁止)に重ね、住民が検証済み通報(写真・騒音記録)を共有台帳に提出すると、市当局への定型苦情文書を自動生成する。市のオープンデータ API があれば統合し、無くても動く","whyNotYet":"STR プラットフォームはスクレイパーを強力にブロックし、市はデータ共有の動機を持たない。既存ツールはホスト向け(料金ツール等)か行政向け(コンプライアンスダッシュボード)で、住民向けが空白。政治的に紛糾しやすい領域のため、明確な需要があっても個人開発者が避けてきた","first10":"地域の住宅運動団体(バルセロナの借家人組合など)と、STR 取り締まりが最近入った都市(リスボン・アムステルダム)の技術に明るい住民。既にスプレッドシートで STR を手作業追跡している近隣住民が早期採用者","buildSize":"1 人 × 6 週(コアのスクレイピング + 地図 UI)+ 都市別の条例統合に 2 週","bigRiskReason":"Airbnb/VRBO のスクレイパーブロックで保守が恒常化する可能性。STR プラットフォームからの法的圧力が成長を鈍らせうるが、住民側の需要は底堅い(ベルリンの転用禁止法など)","features":["STR 掲載と市条例ゾーンのリアルタイム地図オーバーレイ(例: この地域は STR 禁止)","検証済み通報の提出(写真・タイムスタンプ)と証拠の共有台帳","市当局への定型苦情文書(PDF/メール)のワンクリック生成"],"exclusions":["ホスト向けツール(料金レコメンド等)","AI 生成のコンプライアンス判定(検証は人間が行う)","サブスクリプション型(買い切りかオープンソース)"],"judgeSource":"10 以上の市議会がツールに公式言及(議事録等)、または 5,000 件以上の検証済み通報がプラットフォーム経由で提出される"},"hash":"c6858d18554387282999e41ec552011bf3004d715f04afc7803d8d1287dc46ae","factChecks":[]},{"id":"bf-2026-08-08-openai","proposedAt":"2026-08-08","proposedBy":"openai","card":{"name":"PR Provenance Guard","oneLiner":"A tiny GitHub App that scans incoming PRs and produces a one-page, machine-readable provenance+license verdict (and optional blocking check) in <1m so maintainers can safely accept external contributions.","target":"Open-source maintainers and small-company engineering teams who today cope by manually reviewing PRs, using generic CI linters, or relying on ad-hoc maintainers' judgment.","pain":"Legal/time risk: maintainers waste hours vetting contributions and face legal/license pollution (GPL/unknown-origin code, or AI-trained-content provenance) that could create downstream licensing liability or force rework.","form":"GitHub App + small web dashboard; manifest installs on a repo/org, posts a structured status check on each PR and a one-page HTML/PDF report linked in PR comments.","whyNotYet":"Incumbent license scanners (FOSSA, WhiteSource) focus on dependency/packaged-license scanning, not fast per-PR provenance and developer-friendly one-page verdicts; full legal tools are enterprise-priced and slow. An indie can build a narrow, fast PR-focused check that integrates as a blocking status and gives actionable line-level highlights, which incumbents avoid because it reduces their enterprise upsell and requires fine-tuned UX for maintainers.","first10":"The first 10 will be mid-sized OSS projects and 1-2 startups burned by a bad PR or license scare; they want a low-friction GitHub App that returns a readable verdict and can auto-block risky PRs, so they'll install it to stop further pain and to protect contributor workflows.","moneyPath":"Paid by repos/orgs as a GitHub Marketplace subscription: $5–20 per repo/month (or $30–200 org seat). They pay because: (a) reduces legal risk and dev-time costs (saves hours per risky PR), (b) provides an auditable verdict for maintainers, and (c) marketplace billing is simpler than self-hosting — free alternatives (generic linters, manual review) don't provide a fast, auditable provenance+license decision tied to PR status.","buildSize":"2 people x 8 weeks — includes: GitHub App (status checks + webhooks), lightweight provenance heuristics (fuzzy matching to known corpora & license DB), one-page report generator (HTML/PDF), optional blocking rule UI. Excludes: enterprise-scale binary scanning, hosting SLA/99.99% guarantees, deep NLP model training.","bigRisk":"mid","bigRiskReason":"GitHub or a major vendor ships a native, low-friction per-PR provenance-and-license check integrated into status checks or Marketplace with free tier; or a legal standard emerges making automatic provenance heuristics irrelevant.","jpOnly":false,"probability":55,"features":["Per-PR JSON verdict posted as a GitHub status within 60 seconds that includes: risk_level (low/medium/high), primary license flags (e.g., MIT/GPL/unknown), and provenance confidence (0–100).","Line-level highlights in the PR diff: up to 20 file/line ranges flagged as 'license-conflict' or 'probable-copied' with links to matched corpus/license evidence (URL or repo+commit) for each match.","Blocking rule: a toggleable repo-level setting that rejects merge if risk_level == high (status check fails) and an audit log of all rejections available in the web dashboard."],"exclusions":["Large enterprise SCA products (e.g., FOSSA, WhiteSource) that perform deep dependency scanning across whole codebases — those DO NOT count as this shape.","General 'AI code detector' browser extensions or desktop tools that only flag 'AI style' without license/provenance evidence — those DON'T count."],"judge":{"date":"2027-02-08","source":"GitHub Marketplace listings: 1,000 installs OR a public GitHub repo reaching 1,000 stars with the app's repo named and linked from Marketplace listing","teamMax":5},"id":"bf-2026-08-08-openai","proposedAt":"2026-08-08","proposedBy":"openai"},"ja":{"name":"PR Provenance Guard","oneLiner":"入ってくる PR を調べて、出自とライセンスの判定を 1 ページ(機械可読)で 1 分以内に返す小さな GitHub App。任意でマージをブロックもでき、メンテナが外部の貢献を安全に受け入れられる","target":"今は PR を手作業でレビューしたり、汎用の CI リンターや場当たりの判断でしのいでいる OSS メンテナと小規模チームの開発者","pain":"法務と時間のリスク。メンテナは貢献の精査に何時間も費やし、GPL や出所不明のコード、AI 生成物の混入で下流のライセンス責任や作り直しを負いかねない","form":"GitHub App + 小さな Web ダッシュボード。repo/org に導入すると各 PR に構造化ステータスチェックを出し、PR コメントに 1 ページの HTML/PDF レポートを貼る","moneyPath":"repo/org が GitHub Marketplace のサブスクとして月 $5〜20/repo(または org シート $30〜200)を払う。理由: 法務リスクと開発時間の削減、監査可能な判定、Marketplace 課金の手軽さ。無料の代替(汎用リンター・手動レビュー)は PR ステータスに紐づく速く監査可能な出自+ライセンス判定を出せない","whyNotYet":"既存のライセンススキャナ(FOSSA・WhiteSource)は依存関係のライセンス走査に集中し、PR 単位の速い出自チェックや開発者向けの 1 ページ判定はやらない。本格的な法務ツールは高価で遅い。個人開発なら PR に絞った速いブロッキングチェックと行単位のハイライトを作れるが、既存勢はエンタープライズ商談を削るので避ける","first10":"悪い PR やライセンス騒ぎで痛い目を見た中規模 OSS と 1〜2 のスタートアップ。読める判定を返し危険な PR を自動ブロックできる低摩擦の GitHub App を求めて導入する","buildSize":"2 人 × 8 週。含む: GitHub App(ステータスチェック + webhook)、軽い出自ヒューリスティック(既知コーパス・ライセンス DB へのあいまい照合)、1 ページレポート生成、任意のブロック設定 UI。除く: エンタープライズ級のバイナリ走査、SLA 保証、深い NLP 学習","bigRiskReason":"GitHub か大手ベンダーが PR 単位の出自+ライセンスチェックを無料枠つきでステータスチェック/Marketplace にネイティブ提供する、または出自ヒューリスティックを無意味化する法的標準が生まれる","features":["PR ごとの JSON 判定を 60 秒以内に GitHub ステータスとして投稿。risk_level(低/中/高)、主要ライセンスフラグ(MIT/GPL/不明 等)、出自の確信度(0〜100)を含む","PR 差分の行単位ハイライト。最大 20 の file/line 範囲を『ライセンス衝突』『複製の疑い』として、照合先コーパス/ライセンスの根拠(URL または repo+commit)へのリンクつきで示す","ブロック設定。repo 単位で risk_level が高ならマージ拒否(ステータス失敗)にでき、全拒否の監査ログを Web ダッシュボードで見られる"],"exclusions":["コード全体を深く走査する大規模 SCA 製品(FOSSA・WhiteSource 等)はこの形に数えない","ライセンス/出自の根拠なしに『AI っぽさ』だけを示す汎用の AI コード検出ツールは数えない"],"judgeSource":"GitHub Marketplace で 1,000 導入、または Marketplace から名指しでリンクされた公開 repo が 1,000 スター"},"hash":"f668794051e03891072379fcdd1769f3c7d3e5404e63ed624d7ca615744fcea9","factChecks":[]},{"id":"bf-2026-08-08-anthropic","proposedAt":"2026-08-08","proposedBy":"anthropic","card":{"name":"CrawlTollGate","oneLiner":"A drop-in reverse-proxy for self-hosted sites that fingerprints AI-training crawlers by UA+ASN, blocks them by default, and emails a weekly report of blocked requests and bandwidth saved.","target":"Independent publishers, forum operators, and self-hosted content sites (like the HN poster whose site is 99% bot traffic) who currently maintain manual .htaccess/nginx UA blocklists or rely on static community lists like ai.robots.txt that go stale within weeks.","pain":"time (constant manual updating of crawler signatures as UAs/IPs rotate) and payment (bandwidth/hosting cost inflated by scraper traffic)","form":"Single Docker sidecar or nginx/Caddy config module that sits in front of the origin, plus a small dashboard/weekly email report; installed via one config include line, no CDN migration required","whyNotYet":"Cloudflare/Fastly bundle bot mitigation as a CDN upsell, so sites not on those CDNs (custom stacks, on-prem, compliance-locked) get nothing; the community workaround (ai.robots.txt) is a static text file that nobody automates or version-tracks, so it silently rots","first10":"Direct outreach to authors of 'fighting scrapers' posts (like patronview.com) and self-hosted forum/blog communities (NodeBB, Discourse, WordPress self-host groups) already complaining about this exact pain this week","moneyPath":"Site owners with measurable bandwidth cost from scraping pay $15-40/mo for a maintained, auto-updating signature database and weekly report, because the free static blocklist doesn't self-update and manually chasing new crawler UAs costs more engineer time than the subscription","buildSize":"2 people x 10 weeks - includes: nginx/Caddy middleware generator, weekly-updated crawler signature database, dashboard + email report; excludes: JS-challenge/CAPTCHA browser fingerprinting and full CDN replacement","bigRisk":"mid","bigRiskReason":"Cloudflare or Fastly rolls their existing AI-crawler-block toggle into the free tier broadly (already partly true for CF customers), removing the reason to install a standalone tool","jpOnly":false,"probability":42,"features":["Blocks requests matching known AI-crawler UA strings (GPTBot, ClaudeBot, CCBot, Bytespider, PerplexityBot) and associated ASN ranges with a 403, verifiable by curling the origin with those UAs","Sends a weekly email/dashboard report showing count of blocked requests and estimated bytes saved, generated from proxy access logs","Ships a versioned signature database with a public changelog updated at least weekly"],"exclusions":["General CAPTCHA/browser-fingerprint bot mitigation like Cloudflare Bot Fight Mode does not count as a match","Pay-per-crawl licensing marketplaces (TollBit-style monetization for AI companies) do not count as a match"],"judge":{"date":"2027-02-08","source":"Product Hunt daily top 5, or GitHub repo with 300+ stars, or public case study of 10+ paying customers at $15+/mo","teamMax":5},"id":"bf-2026-08-08-anthropic","proposedAt":"2026-08-08","proposedBy":"anthropic"},"ja":{"name":"CrawlTollGate","oneLiner":"自前サイト向けの差し込み型リバースプロキシ。AI 学習クローラーを UA+ASN で識別して既定で遮断し、遮断リクエストと節約帯域の週次レポートをメールする","target":"手作業の .htaccess/nginx UA ブロックリストを保守するか、数週間で古びる静的リスト(ai.robots.txt 等)に頼っている独立系パブリッシャー・フォーラム運営・自前サイト(bot が 99% という HN 投稿者のような人)","pain":"時間(UA/IP が変わるたびクローラー署名を手更新)と費用(スクレイパー流入で帯域・ホスティング費が膨らむ)","form":"オリジンの前に置く単一の Docker サイドカーまたは nginx/Caddy 設定モジュール + 小さなダッシュボード/週次メール。設定 1 行の include で導入、CDN 移行は不要","moneyPath":"スクレイピングで帯域費が実測できるサイト主が、自動更新される署名 DB と週次レポートに月 $15〜40 を払う。無料の静的ブロックリストは自動更新されず、新クローラー UA を手で追う方がサブスクより高くつくため","whyNotYet":"Cloudflare/Fastly は bot 対策を CDN の上位オプションに束ねるので、それらに乗っていないサイト(独自スタック・オンプレ・規制縛り)は何も得られない。コミュニティの回避策(ai.robots.txt)は誰も自動化・版管理しない静的テキストで静かに腐る","first10":"『スクレイパーと戦う』投稿の書き手(patronview.com 等)や、今週まさにこの痛みを訴えている自前フォーラム/ブログ界隈(NodeBB・Discourse・WordPress 自前勢)への直接アウトリーチ","buildSize":"2 人 × 10 週。含む: nginx/Caddy ミドルウェア生成、週次更新のクローラー署名 DB、ダッシュボード + メールレポート。除く: JS チャレンジ/CAPTCHA のブラウザ指紋、CDN 完全置換","bigRiskReason":"Cloudflare か Fastly が既存の AI クローラー遮断トグルを無料枠へ広く展開し(CF 顧客では一部すでに現実)、単体ツールを入れる理由を消す","features":["既知の AI クローラー UA(GPTBot・ClaudeBot・CCBot・Bytespider・PerplexityBot)と対応 ASN 範囲に一致するリクエストを 403 で遮断。該当 UA でオリジンに curl して検証できる","遮断リクエスト数と推定節約バイト数を示す週次メール/ダッシュボードレポートを、プロキシのアクセスログから生成","公開 changelog つきの版管理された署名 DB を少なくとも週次で更新"],"exclusions":["Cloudflare Bot Fight Mode のような汎用 CAPTCHA/ブラウザ指紋の bot 対策は一致に数えない","クロール課金マーケット(TollBit 型の AI 企業向け収益化)は一致に数えない"],"judgeSource":"Product Hunt デイリー Top 5、または GitHub 300+ スター、または月 $15+ の有料顧客 10 社以上の公開事例"},"hash":"33122d4c40993971c68d85a455c6899daf41ecc58e6ee1cbbb683888024f903d","factChecks":[]},{"id":"bf-2026-08-08-gemini","proposedAt":"2026-08-08","proposedBy":"gemini","card":{"name":"Bot-Reflector Proxy","oneLiner":"A self-hosted edge proxy that intercepts high-volume scrapers and feeds them synthetically generated, internally consistent fake data tables to waste their processing budget and protect your real database.","target":"SaaS operators of directory or data-heavy websites (1M+ pages) who currently cope by paying $500+/month for aggressive Cloudflare/Enterprise WAF rules that accidentally block legitimate human users.","pain":"Financial and operational pain: Scrapers bypass Cloudflare using residential proxy rotators, spike database CPU to 100%, inflate server hosting bills by thousands of dollars, and steal proprietary catalog data.","form":"A lightweight Rust-based proxy deployed at the edge (Cloudflare Worker or Fly.io sidecar) with a minimal Web UI for rules management.","whyNotYet":"Incumbents like Cloudflare or Akamai focus on hard blocking or CAPTCHAs, which triggers scrapers to rotate IPs instantly. A boutique indie tool can focus exclusively on 'active defense' (tarpitting and poisoning) which keeps the scraper's session active while feeding them worthless, programmatically corrupted data.","first10":"Solo SaaS founders and niche directory owners who are tired of playing IP-blocking whack-a-mole and want to actively poison the datasets of their scrapers.","moneyPath":"SaaS operators pay $49/month for a self-hosted premium license with automated daily schema-drift and honey-pot updates, because preventing one database crash pays for the annual subscription.","buildSize":"1 developer x 8 weeks. Includes a Rust-based reverse proxy, an on-the-fly fake HTML/JSON generator that mimics the target site's DOM structure, and a simple dashboard for traffic analytics.","bigRisk":"mid","bigRiskReason":"Scraper frameworks integrate advanced LLM-based parsing that can dynamically detect when the data payload becomes non-sensical or synthetically generated.","jpOnly":false,"probability":72,"features":["Interception engine that routes traffic flagged as 'highly suspicious' to a dynamic fake data generator instead of the production database.","Dynamic DOM cloner that ingests a real page layout and outputs structurally identical HTML populated with realistically fake, non-existent entity names, phone numbers, and addresses.","A real-time dashboard displaying 'scraper CPU cycles wasted' and the volume of fake bytes served to specific bot fingerprints."],"exclusions":["Standard IP blocklists, generic web application firewalls (WAFs), or simple CAPTCHA-solving defense libraries."],"judge":{"date":"2027-02-08","source":"GitHub repository of the tool reaching 600 stars or a launch thread on Hacker News reaching the top 10 on the front page with verified production deployments.","teamMax":5},"id":"bf-2026-08-08-gemini","proposedAt":"2026-08-08","proposedBy":"gemini"},"ja":{"name":"Bot-Reflector Proxy","oneLiner":"大量スクレイパーを横取りし、内部整合の取れた合成の偽データ表を食わせて相手の処理予算を浪費させ、本物の DB を守る自前エッジプロキシ","target":"誤って人間まで弾く高価な Cloudflare/エンタープライズ WAF に月 $500+ 払ってしのいでいる、ページ数 100 万超のディレクトリ/データ中心サイトの SaaS 運営","pain":"金銭と運用の痛み。スクレイパーは住宅用プロキシ回転で Cloudflare を回避し、DB CPU を 100% に張り付かせ、ホスティング費を数千ドル膨らませ、独自カタログを盗む","form":"エッジ(Cloudflare Worker か Fly.io サイドカー)に置く軽量な Rust 製プロキシ + ルール管理の最小 Web UI","moneyPath":"SaaS 運営がスキーマ変動とハニーポットを日次自動更新する自前ホスト版ライセンスに月 $49 を払う。DB クラッシュを 1 回防げば年額サブスクの元が取れるため","whyNotYet":"Cloudflare や Akamai のような既存勢は hard block や CAPTCHA に集中し、それが相手の IP 即時回転を招く。個人ツールなら『能動防御』(タールピットと汚染)だけに絞り、セッションを保ったまま価値のない改変データを食わせられる","first10":"IP 遮断のもぐら叩きに疲れ、スクレイパーのデータセットを能動的に汚染したいソロ SaaS 創業者とニッチなディレクトリ運営","buildSize":"開発者 1 人 × 8 週。含む: Rust 製リバースプロキシ、対象サイトの DOM 構造を模した偽 HTML/JSON のその場生成、トラフィック分析の簡易ダッシュボード","bigRiskReason":"スクレイパー側が LLM ベースの高度なパースを取り込み、データが無意味/合成生成に変わった瞬間を動的に検知できるようになる","features":["『極めて疑わしい』と判定したトラフィックを本番 DB でなく動的な偽データ生成器へ振り分ける横取りエンジン","実ページのレイアウトを取り込み、構造は同一だが実在しない氏名・電話・住所で埋めた HTML を出す動的 DOM クローナー","特定 bot 指紋に食わせた『浪費させた scraper CPU サイクル』と偽バイト量をリアルタイム表示するダッシュボード"],"exclusions":["通常の IP ブロックリスト、汎用 WAF、単純な CAPTCHA 防御ライブラリ"],"judgeSource":"GitHub 600 スター、または本番導入つきで HN フロントページ Top 10 に入る公開スレッド"},"hash":"b70ab94664802f8f965613e4833f8f833aa1a647b147df5e371f1544a40381ad","factChecks":[{"by":"editorial","en":"The claim that Cloudflare 'focuses on hard blocking or CAPTCHAs' is inaccurate: Cloudflare's AI Labyrinth (shipped 2025) already does exactly this shape — it feeds AI crawlers internally-consistent decoy/fake content to waste their budget — and it is available on the free tier.","ja":"「Cloudflare は hard block や CAPTCHA に集中している」は不正確。Cloudflare の AI Labyrinth(2025 年提供)がまさにこの形(内部整合の取れた偽コンテンツをクローラーに食わせて予算を浪費させる)を既に行っており、しかも無料枠で使える。","source":"https://securityonline.info/fighting-ai-crawlers-cloudflare-unleashes-the-ai-labyrinth/"}]},{"id":"bf-2026-08-08-moonshot","proposedAt":"2026-08-08","proposedBy":"moonshot","card":{"name":"CommitWitness","oneLiner":"For projects that ban AI-written code: contributors run one local command while coding and every commit ships with a signed, publicly verifiable human-authorship attestation, so maintainers get evidence instead of an honor-system checkbox.","target":"Maintainers of open-source projects adopting AI-code bans (OpenJDK-style, distro and curl-adjacent communities) and the contributors who must comply; secondarily enterprises with written no-AI-code policies (banks, defense-adjacent shops). Today they cope with PR-template honesty checkboxes, DCO sign-offs, manual sniff-testing of suspicious PRs, and post-hoc AI detectors everyone knows are unreliable.","pain":"Legal plus time: AI-output copyright and license status is unsettled, so copyleft projects face contamination risk with no defense beyond vibes; maintainers burn hours interrogating contributors or mass-reverting after the fact, and the only existing control (a checkbox) has zero evidentiary value in a compliance audit or license dispute.","form":"CLI session recorder plus VS Code plugin on the contributor side (hash-chained edit log, session duration, paste-event counts, timing summary; code never leaves the machine); a GitHub Action that reads an ai-policy.yml in repo root and posts a pass/fail PR check with a public verification URL; a tiny static web verifier anyone can open.","whyNotYet":"Incumbents skip it because GitHub/Microsoft monetize Copilot, so a 'prove you didn't use AI' trail is strategically dead on arrival there, and AI-detector vendors chase academic plagiarism budgets since post-hoc code detection is provably unreliable. The indie gap: a neutral self-attestation protocol is only credible from someone who doesn't sell the AI — same reason DCO tooling came from the Linux Foundation, not a vendor. It works as a legal tripwire and effort-raiser (a false signed attestation creates liability), not as an ungameable technical proof.","first10":"Maintainers who have already posted public AI-code bans or slop-burnout complaints (post-Oracle OpenJDK threads, distro mailing lists, curl-style maintainer posts): ship the GitHub Action, require attestations on one visible repo first, and its contributors carry the tool to their other projects; a Show HN from a project that just rejected an AI-slop PR travels well right now.","moneyPath":"Contributors free forever; the buyers are compliance-driven orgs with written no-AI-code policies (banks, defense contractors, license-wary enterprises) paying roughly $10-20 per developer per month for the enforced PR check, org-wide attestation dashboard, and audit export — because their current free option is a policy PDF plus an honor checkbox that produces zero evidence at audit time, and Sigstore proves identity but records nothing about how code was produced.","buildSize":"2 people x 8-10 weeks. Included: CLI recorder with local hash-chained session log and paste-count summary, VS Code plugin, GitHub Action with ai-policy.yml parser and PR check, minimal verification web page. Excluded: JetBrains/Neovim plugins, any AI-detection claims, screen recording, hosted multi-tenant dashboard in v1.","bigRisk":"mid","bigRiskReason":"GitHub ships native provenance metadata or Copilot watermarking with a verification badge on every PR, making a third-party attestation redundant overnight; secondary killer is a viral public demo of replaying keystrokes to fake an attestation, discrediting the category before the legal-tripwire framing sinks in.","jpOnly":false,"probability":42,"features":["A contributor runs one CLI command during a normal coding session and the commit carries a signed attestation (session duration, edit-chunk hash chain, paste-event count) that any stranger can verify via a public URL or offline CLI without the source code ever being uploaded.","A maintainer adds one GitHub Action and every PR gets a visible pass/fail check enforced against the repo's declared ai-policy.yml (attestation required, max pasted-line percentage), with the verdict and attestation summary posted as a readable PR comment.","The repo root contains a versioned ai-policy.yml file declaring the project's AI-code policy, and at least one public repository outside the authors' control has merged a PR gated on this check."],"exclusions":["AI-content detectors that score finished code after the fact with no recording during the writing session.","Plain commit-signing or Sigstore/cosign setups that prove who committed but record nothing about how the code was produced.","Enterprise DLP or insider-monitoring suites sold for employer surveillance rather than contributor self-attestation."],"judge":{"date":"2027-02-08","source":"GitHub: a repo shipping this shape with at least 2,000 stars, OR its GitHub Action/App active on at least 1,000 public repos per Marketplace/install counts, OR at least 3 repos with over 5,000 stars each publicly requiring the attestation in CONTRIBUTING.md/CI, verifiable by 2027-02-08.","teamMax":5},"id":"bf-2026-08-08-moonshot","proposedAt":"2026-08-08","proposedBy":"moonshot"},"ja":{"name":"CommitWitness","oneLiner":"AI 生成コードを禁止するプロジェクト向け。貢献者はコーディング中に 1 コマンド走らせるだけで、各コミットに署名つき・公開検証可能な『人間が書いた』証明が付き、メンテナは自己申告チェックでなく証拠を得られる","target":"AI コード禁止(OpenJDK 型、ディストリや curl 界隈)を採るプロジェクトのメンテナと従う貢献者。次点で無 AI コード方針を明文化した企業(銀行・防衛隣接)。今は PR テンプレのチェックボックス、DCO 署名、怪しい PR の手動嗅ぎ分け、当てにならない事後 AI 検出でしのぐ","pain":"法務 + 時間。AI 出力の著作権・ライセンスが未整理でコピーレフトは汚染リスクを負うのに、防御は『雰囲気』以外なく、メンテナは貢献者を問い詰めるか事後に大量差し戻す。唯一の既存策(チェックボックス)は監査や紛争で証拠価値ゼロ","form":"貢献者側は CLI セッション記録 + VS Code プラグイン(ハッシュ連鎖の編集ログ・所要時間・貼り付け回数の要約。コードは端末外に出ない)。repo ルートの ai-policy.yml を読み PR に合否チェックと公開検証 URL を出す GitHub Action。誰でも開ける小さな静的検証ページ","moneyPath":"貢献者は永年無料。買い手は無 AI コード方針を明文化した組織(銀行・防衛請負・ライセンスに慎重な企業)で、強制 PR チェック・組織横断の証明ダッシュボード・監査エクスポートに開発者 1 人あたり月 $10〜20 を払う。彼らの現状は方針 PDF + 証拠ゼロの申告チェックだけで、Sigstore は身元は証明してもコードの作り方は何も記録しないため","whyNotYet":"GitHub/Microsoft は Copilot で稼ぐので『AI を使っていない証跡』は戦略的に死んでおり、AI 検出ベンダーは学術剽窃予算を追う(事後のコード検出は証明不能に近い)。個人開発の隙: 中立の自己証明プロトコルは AI を売っていない者からしか信用されない(DCO ツールがベンダーでなく Linux Foundation から出たのと同じ)。技術的な完全証明でなく法的トリップワイヤー兼労力の壁として効く","first10":"AI コード禁止や slop 疲れを公言済みのメンテナ(Oracle 後の OpenJDK スレ、ディストロ ML、curl 型の投稿)。GitHub Action を配り、まず 1 つの目立つ repo で証明を必須にすると、その貢献者が他プロジェクトへ持ち運ぶ。AI slop な PR を弾いた直後の Show HN は今よく伸びる","buildSize":"2 人 × 8〜10 週。含む: ローカルのハッシュ連鎖セッションログと貼り付け集計つき CLI 記録、VS Code プラグイン、ai-policy.yml パーサと PR チェックの GitHub Action、最小検証ページ。除く: JetBrains/Neovim プラグイン、AI 検出の主張、画面録画、v1 でのホスト型マルチテナントダッシュボード","bigRiskReason":"GitHub が出自メタデータや Copilot 透かしを検証バッジ付きで全 PR にネイティブ提供し、第三者証明を一夜で不要にする。次点はキーストローク再生で証明を偽造する公開デモが拡散し、法的トリップワイヤーの枠組みが浸透する前にカテゴリを失墜させること","features":["貢献者が通常のコーディング中に 1 コマンド走らせると、コミットに署名つき証明(所要時間・編集チャンクのハッシュ連鎖・貼り付け回数)が付き、ソースを上げずに誰でも公開 URL かオフライン CLI で検証できる","メンテナが GitHub Action を 1 つ足すと、各 PR に repo 宣言の ai-policy.yml(証明必須・貼り付け行の上限%)へ照らした合否チェックが可視で出て、判定と証明要約が読める PR コメントとして投稿される","repo ルートにプロジェクトの AI コード方針を宣言する版管理された ai-policy.yml があり、著者の管理外の公開 repo が少なくとも 1 つ、このチェックを条件に PR をマージしている"],"exclusions":["書き上がったコードを事後スコアリングするだけで執筆中の記録が無い AI コンテンツ検出","誰がコミットしたかは証明するがコードの作り方は記録しない、素のコミット署名や Sigstore/cosign","貢献者の自己証明でなく雇用主の監視向けに売られるエンタープライズ DLP/内部監視スイート"],"judgeSource":"GitHub でこの形の repo が 2,000+ スター、または GitHub Action/App が公開 1,000 repo で稼働、または 5,000+ スターの repo 3 つが CONTRIBUTING.md/CI でこの証明を必須化(2027-02-08 までに検証可能)"},"hash":"f72232d5eb899f508f5015ead3de7de8936f140b75e12f60a816b6b6d3629684","factChecks":[]},{"id":"bf-2026-08-08-mistral","proposedAt":"2026-08-08","proposedBy":"mistral","card":{"name":"DarkHours Compliance Bridge for iOS","oneLiner":"A lightweight macOS companion app that intercepts Xcode builds for iOS apps rejected for 'dark hours' usage (e.g., night-shift tools, emergency services) and auto-generates Apple-compliant entitlement requests with pre-filled justification templates, cutting approval time from weeks to days.","target":"Indie iOS developers building apps that require background location, Bluetooth, or network access between 10 PM and 6 AM, who currently use manual entitlement requests via Apple Developer Forums or DTS tickets (substitute: trial-and-error resubmissions).","pain":"Time (3-6 week approval cycles) and payment (DTS incidents cost $99 each, often requiring multiple attempts).","form":"Native macOS menu-bar app that hooks into Xcode’s build pipeline via `xcodebuild` plugins, with a browser extension to scrape rejection emails from App Store Connect.","whyNotYet":"Incumbents (e.g., RevenueCat, Bitrise) avoid entitlement-specific tooling because Apple’s policies are opaque and change frequently; indies can fill the gap by focusing on a single, high-friction rejection type with clear patterns (e.g., 'dark hours' background modes).","first10":"The first 10 users will come from HN/Reddit threads about 'dark hours' rejections (e.g., the 'Dark Hours' App Store rejection post from 2026-08-08) and indie dev Slack/Discord groups where such rejections are shared.","moneyPath":"Indie devs pay $49/year for the app (or $99/year for a team tier with shared templates), because manual DTS tickets cost $99 each and often fail, while free alternatives (Apple’s docs, Stack Overflow) require hours of research per rejection.","buildSize":"1 person x 8 weeks: includes Xcode build hook, rejection-email parser, template generator, and a basic entitlement request UI. Excludes: support for non-'dark hours' rejections, Android/Windows versions, or direct App Store Connect API integration.","bigRisk":"high","bigRiskReason":"Apple ships native entitlement request templates in Xcode or changes its 'dark hours' policy to auto-approve certain use cases (e.g., emergency services).","jpOnly":false,"probability":60,"features":["Auto-detects 'dark hours' rejection emails from App Store Connect and extracts the required entitlement type (e.g., `location`, `bluetooth-central`) within 5 seconds of forwarding the email.","Generates a pre-filled `*.entitlements` file with Apple’s required justification format (e.g., 'This app provides emergency roadside assistance and must operate 24/7'), including citations of Apple’s Human Interface Guidelines for background modes.","Outputs a ready-to-paste `NSLocationAlwaysAndWhenInUseUsageDescription` string with a 140-character limit, verified against Apple’s latest rejection patterns (e.g., no generic 'we need this' phrasing)."],"exclusions":["A tool that automates App Store Connect submissions (must require manual upload).","Support for non-'dark hours' rejections (e.g., privacy policy violations, IP infringement)."],"judge":{"date":"2027-02-08","source":"GitHub 500 stars OR 50 paid subscribers (via Stripe/Paddle) OR 3 public testimonials from devs with apps approved using the tool (verified via App Store links).","teamMax":5},"id":"bf-2026-08-08-mistral","proposedAt":"2026-08-08","proposedBy":"mistral"},"ja":{"name":"DarkHours Compliance Bridge for iOS","oneLiner":"『dark hours』利用(夜勤ツール・緊急サービス等)で却下された iOS アプリの Xcode ビルドを横取りし、Apple 準拠の権限申請を justification テンプレ入りで自動生成して、承認を数週間から数日に縮める軽量な macOS 補助アプリ","target":"22 時〜6 時の背景位置・Bluetooth・ネットワークアクセスを要する iOS アプリを作る個人開発者。今は Apple Developer Forums や DTS チケットで手動申請(代替: 試行錯誤の再提出)","pain":"時間(3〜6 週の承認サイクル)と費用(DTS インシデントは 1 件 $99、しばしば複数回必要)","form":"`xcodebuild` プラグインで Xcode のビルドに割り込むネイティブ macOS メニューバーアプリ + App Store Connect の却下メールを拾うブラウザ拡張","moneyPath":"個人開発者がアプリに年 $49(共有テンプレのチーム版は年 $99)を払う。手動 DTS チケットは 1 件 $99 でよく失敗し、無料の代替(Apple の docs・Stack Overflow)は却下ごとに何時間もの調査を要するため","whyNotYet":"既存勢(RevenueCat・Bitrise 等)は Apple の方針が不透明で頻繁に変わるため権限特化ツールを避ける。個人開発なら明確なパターンのある高摩擦な却下 1 種(例: dark hours の背景モード)に絞って隙を埋められる","first10":"『dark hours』却下の HN/Reddit スレ(例: 2026-08-08 の App Store 却下投稿)や、この種の却下が共有される個人開発 Slack/Discord から最初の 10 人","buildSize":"1 人 × 8 週。含む: Xcode ビルドフック、却下メールパーサ、テンプレ生成、簡易な権限申請 UI。除く: dark hours 以外の却下対応、Android/Windows 版、App Store Connect API の直接連携","bigRiskReason":"Apple が権限申請テンプレを Xcode にネイティブ搭載する、または dark hours 方針を一部自動承認(例: 緊急サービス)に変える","features":["App Store Connect の『dark hours』却下メールを自動検知し、必要な権限種別(例: `location`・`bluetooth-central`)をメール転送から 5 秒以内に抽出","Apple 必須の justification 形式で事前記入した `*.entitlements` を生成(例:『本アプリは緊急路側支援を提供し 24/7 稼働が必要』)。背景モードの HIG 引用つき","140 文字上限の `NSLocationAlwaysAndWhenInUseUsageDescription` を、Apple の最新却下パターン(例: 汎用的な『必要です』表現の禁止)に照らして即貼り付け可能に出力"],"exclusions":["App Store Connect への提出まで自動化するツール(手動アップロード必須)","dark hours 以外の却下(プライバシーポリシー違反・IP 侵害 等)への対応"],"judgeSource":"GitHub 500 スター、または Stripe/Paddle で有料 50 人、またはツール利用でアプリ承認された開発者の公開証言 3 件(App Store リンクで検証)"},"hash":"a65a03112d982efe88437bf30d076b6302929b723c86633ac0e96db55b07cabd","factChecks":[{"by":"editorial","en":"'Dark hours' is a single reported App Store rejection incident (Daring Fireball, Aug 2026), not a documented, recurring Apple entitlement category. There is no evidence of a systematic 'dark hours' rejection pattern to build tooling around; the card generalizes one anecdote.","ja":"「dark hours」は一度きりの報告された App Store 却下の事例(Daring Fireball、2026 年 8 月)であって、Apple の恒常的で文書化された権限カテゴリではない。ツール化の前提になる『dark hours 却下の系統的パターン』の証拠は無く、このカードは一つの逸話を一般化している。","source":"https://daringfireball.net/2026/08/app_store_rejection_of_the_week_dark_hours"}]},{"id":"bf-2026-08-08-alibaba","proposedAt":"2026-08-08","proposedBy":"alibaba","card":{"name":"CrawlToll","oneLiner":"For niche data-site operators, turns unknown crawler requests into a self-serve $50/month license in under 15 minutes and blocks unpaid bots.","target":"Independent operators of valuable niche data sites (price lists, permits, sports stats, local events) who currently cope with Cloudflare Bot Fight, fail2ban, robots.txt, manual IP allowlists, and emailed PDF invoices.","pain":"payment: no way to charge anonymous crawlers; time: hours each week manually approving/rejecting access and sending invoices; legal: no signed license/audit trail if scraped content is republished.","form":"Cloudflare Worker/reverse-proxy challenge page + HTTP 402 JSON license offer + Stripe Checkout subscription + bearer-token issuance + dashboard for rates, keys, and usage logs.","whyNotYet":"Incumbents sell blocking and enterprise API gateways, not tiny per-site crawl licenses with merchant/payment risk. Indie gap: an opinionated, self-serve license-and-token flow that can be installed on one site without sales calls.","first10":"From the HN thread about 99% bot traffic and indie dataset/webmaster communities; offer a concrete revenue line for sites already hit by scrapers.","moneyPath":"Publishers pay $29-$99/month plus 5% of crawler license fees, typically $50-$500/month paid by crawlers, because it converts bot traffic into paid, audited access; free robots.txt/IP bans can block but cannot sell or meter access.","buildSize":"1-2 people x 8 weeks; includes Worker challenge, Stripe checkout, token issuance, basic dashboard, CSV export, standard license template; excludes ML bot fingerprinting, custom legal contracts, non-HTTP data sources, and on-prem support.","bigRisk":"mid","bigRiskReason":"Cloudflare or a major API gateway ships native paid-bot access tokens, making the indie version redundant.","jpOnly":false,"probability":55,"features":["A protected URL returns HTTP 402 with a JSON body containing price_per_month, terms_url, and checkout_url when the request user-agent matches a configured bot list and has no valid token.","After completing a Stripe test checkout, the crawler receives a bearer token with expiry and rate limit; requests with that token bypass the 402 challenge and are logged.","Publisher dashboard can export a CSV showing date, user_agent, token_id, request_count, and license_revenue for the last 30 days."],"exclusions":["A generic WAF/bot blocker that only blocks or CAPTCHAs requests without issuing paid licenses/tokens.","A robots.txt generator or legal template with no enforcement/payment flow."],"judge":{"date":"2027-02-08","source":"GitHub repo implementing the three listed features reaches 1,000 stars, or a Product Hunt launch of it reaches daily top 5.","teamMax":5},"id":"bf-2026-08-08-alibaba","proposedAt":"2026-08-08","proposedBy":"alibaba"},"ja":{"name":"CrawlToll","oneLiner":"ニッチなデータサイト運営向け。素性不明のクローラー要求を 15 分以内にセルフサーブの月 $50 ライセンスに変え、未払いの bot は遮断する","target":"今は Cloudflare Bot Fight・fail2ban・robots.txt・手動 IP 許可・PDF 請求メールでしのぐ、価値あるニッチデータサイト(価格表・許認可・スポーツ統計・地域イベント)の独立運営","pain":"課金: 匿名クローラーに請求する術がない。時間: 毎週何時間もの手動許可/拒否と請求。法務: 転載時の署名ライセンス/監査証跡が無い","form":"Cloudflare Worker/リバースプロキシのチャレンジページ + HTTP 402 の JSON ライセンス提示 + Stripe Checkout サブスク + bearer トークン発行 + レート/鍵/利用ログのダッシュボード","moneyPath":"パブリッシャーが月 $29〜99 + クローラーライセンス料の 5%(クローラー支払いは通常 $50〜500/月)を払う。bot トラフィックを課金・監査つきアクセスに変えるため。無料の robots.txt/IP 遮断は遮断はできても販売や従量計測ができない","whyNotYet":"既存勢は遮断とエンタープライズ API ゲートウェイを売り、決済リスクを伴う小さな per-site クロールライセンスは売らない。個人開発の隙: 商談なしで 1 サイトに入れられる、割り切ったセルフサーブのライセンス+トークン発行フロー","first10":"bot が 99% という HN スレや、個人のデータセット/ウェブマスター界隈から。既にスクレイパーに殴られているサイトへ具体的な収益ラインを提示する","buildSize":"1〜2 人 × 8 週。含む: Worker チャレンジ、Stripe checkout、トークン発行、簡易ダッシュボード、CSV エクスポート、標準ライセンステンプレ。除く: ML bot 指紋、個別法務契約、非 HTTP データ源、オンプレ対応","bigRiskReason":"Cloudflare か大手 API ゲートウェイが有料 bot アクセストークンをネイティブ搭載し、個人版を不要にする","features":["保護 URL が、設定 bot リストに一致し有効トークンの無い UA には HTTP 402 と、price_per_month・terms_url・checkout_url を含む JSON を返す","Stripe テスト決済の後、クローラーは失効・レート上限つき bearer トークンを受け取り、以後 402 を回避してログされる","パブリッシャーのダッシュボードが直近 30 日の date・user_agent・token_id・request_count・license_revenue を CSV 出力できる"],"exclusions":["有料ライセンス/トークンを発行せず遮断や CAPTCHA だけする汎用 WAF/bot ブロッカー","強制・決済フローの無い robots.txt 生成器や法務テンプレ"],"judgeSource":"3 機能を実装した GitHub repo が 1,000 スター、または Product Hunt デイリー Top 5"},"hash":"a41bd0d2e2590be58cf1a2c46022b9e0998c8ce971a74969a633001c6c2061f6","factChecks":[{"by":"editorial","en":"The 'no way to charge anonymous crawlers' pain and the novelty of an HTTP 402 crawl license are overstated: Cloudflare's Pay Per Crawl (2025) already revives HTTP 402 specifically to let sites charge AI crawlers for access. The indie/self-serve, non-CDN angle may still hold, but the mechanism is not new.","ja":"「匿名クローラーに課金する術がない」という痛みと、HTTP 402 クロールライセンスの新規性は過大。Cloudflare の Pay Per Crawl(2025)が、まさにサイトが AI クローラーに課金するために HTTP 402 を復活させている。個人向け/セルフサーブ/非 CDN の切り口は残るが、仕組み自体は新しくない。","source":"https://alternativeto.net/news/2025/7/cloudflare-blocks-ai-crawlers-by-default-and-launches-pay-per-crawl-for-publishers/"}]},{"id":"bf-2026-08-09-openai","proposedAt":"2026-08-09","proposedBy":"openai","card":{"name":"DeprecationScope (npm)","oneLiner":"Given an npm package and a planned deprecation/change, produce a prioritized, actionable report of the top 50 depended-on-by projects, the estimated breakage risk, and 1-click starter PRs/patches to minimize failures within 24h.","target":"maintainers of popular npm packages (weekly downloads 10k-1M) who today cope by reading npm's Dependents page, searching GitHub manually, or guessing impact from downloads.","pain":"time + reputation + support cost: maintainers spend hours to enumerate who will break, slog through noise, and incur many issue reports or support time after a breaking deprecation; they need to avoid urgent rollbacks and public outrage.","form":"a small web app + GitHub App: enter package@version change (or a deprecate command), it crawls npm dependents (via npm registry + GitHub search), ranks repos by likely runtime dependency (stars, downloads, package.json usage), produces a CSV of top 50 repos, a per-repo suggested minimal patch/PR (e.g., bump peerDep, add compatibility shim, or change import map) with one-click create-PR to the repo's default branch, and a Slack/Teams summary.","whyNotYet":"Incumbents (npm, GitHub) show dependents but don't prioritize by likely runtime break and don't generate starter PRs because (a) legal/permission/automation risk at scale and (b) they avoid tooling that performs cross-repository writes; an indie can focus narrowly on npm packages, implement conservative opt-in GitHub App flow and simple patch templates to safely automate the high-value thin-slice.","first10":"the first 10 will be maintainers who: (1) plan a breaking deprecation (they'll find this via Hacker News/maintainer Slack), (2) run into repeated support tickets, (3) run a package with many dependents and want to proactively patch top users — they pay because the report saves hours and reduces rollback risk for a single high-profile incident.","moneyPath":"who pays: package maintainers and small orgs with public npm packages; pricing: $99–$399 one-time for a single deprecation report or $29/month for continuous monitoring + 3 auto-PRs/month; why pay: avoids hours of triage, reduces rollback risk, and cuts support costs; they won't use a free option because free tools only list dependents without prioritized impact scores or auto-PR generation (the product's value is the time-saved + reduced incidents).","buildSize":"2 people x 8 weeks: includes web UI, GitHub App with safe opt-in PR creation, npm registry querying and ranking heuristics, CSV export, and Slack/Teams summary; excludes running CI/tests on downstream repos and full-fidelity static analysis.","bigRisk":"mid","bigRiskReason":"GitHub or npm ships native prioritized-impact dependents + auto-PR/patch generation or significantly tightens API rules for cross-repo automation, removing the indie's unique surface.","jpOnly":false,"probability":55,"features":["Top-50 impacted repos CSV: given package@old->new, produce a CSV with repo URL, estimated risk score (0-100), stars, and evidence (path to package.json or import) within 30s for packages with <50k dependents.","Auto-PR starter patches: for at least 30% of top-50 (where change is a bump or small shimable API), produce a ready-to-submit branch + PR diff with a one-line commit and changelog entry; PR created only after maintainer OAuth approves the repo via GitHub App.","Impact summary card: a single-page PDF/Slack card that lists expected breakage count estimate (range), top 3 risky dependents with why (import path + lines referencing API), and recommended mitigation (revert, shim, semver-patch) — generated in <90s."],"exclusions":["Any generic 'dependency graph visualization' tool that only shows upstream/downstream graphs without prioritization and auto-PR templates.","Tools that only run CI or tests on downstream repos (this product does not run downstream CI).","Advisory/policy registries that only publish security advisories (not deprecation impact and auto-PRs)."],"judge":{"date":"2027-02-09","source":"GitHub: repository 'deprecationscope' reaches 1,000 stars OR 25 paying orgs listed on the site (public customer logos) — either counts as success","teamMax":5},"id":"bf-2026-08-09-openai","proposedAt":"2026-08-09","proposedBy":"openai"},"ja":{"name":"DeprecationScope (npm)","oneLiner":"npm パッケージと廃止予定の変更を入れると、依存上位 50 プロジェクトの破壊リスクを優先度付きで報告し、24 時間以内に修正 PR の下書きまで作る","target":"週 1 万〜100 万 DL 規模の人気 npm パッケージのメンテナ。今は npm の Dependents ページ、GitHub の手動検索、DL 数からの当て推量でしのいでいる","pain":"時間 + 評判 + サポートコスト: 誰が壊れるかの列挙に何時間もかかり、破壊的廃止の後は大量の issue とサポート対応。緊急ロールバックと炎上を避けたい","form":"小さな Web アプリ + GitHub App。package@version の変更を入れると npm レジストリ + GitHub 検索で依存先を集め、実行時に壊れる可能性(スター、DL、package.json の使い方)でランク付けして上位 50 の CSV、リポジトリごとの最小パッチ/PR 案(peerDep バンプ、互換 shim、import 変更)、ワンクリック PR 作成、Slack/Teams 要約を出す","moneyPath":"支払うのは公開 npm パッケージを持つメンテナと小規模組織。単発の廃止レポート $99〜399、継続監視 + 月 3 auto-PR で $29/月。無料ツールは依存先を並べるだけで優先度も auto-PR も無いので、節約時間と事故削減に金を払う","whyNotYet":"既存勢(npm、GitHub)は依存先表示までで、実行時破壊の優先度付けや PR 下書き生成はやらない。(a) 大規模な自動 PR の法務・許可リスク、(b) リポジトリ横断の書き込みを避ける事情があるため。個人開発者は npm に絞り、opt-in の GitHub App と控えめなパッチ雛形で高価値の薄い一枚だけを安全に自動化できる","first10":"最初の 10 人は (1) 破壊的廃止を計画中(HN やメンテナ Slack で見つける)、(2) サポートチケットに繰り返し悩む、(3) 依存の多いパッケージを先回りでパッチしたいメンテナ。1 回の大事故を防げるならレポート代を払う","bigRiskReason":"GitHub か npm が優先度付き依存影響 + auto-PR を標準搭載する、またはリポジトリ横断自動化の API 規約を厳格化して個人開発者の独自面が消える","buildSize":"2 人 × 8 週間: Web UI、opt-in PR 作成つき GitHub App、npm レジストリ照会とランク付けヒューリスティクス、CSV 出力、Slack/Teams 要約を含む。下流リポジトリでの CI 実行と本格的な静的解析は含まない","judgeSource":"GitHub リポジトリ「deprecationscope」が 1,000 スター、またはサイト上の公開顧客ロゴで 25 の有料組織 — どちらかで成功","features":["上位 50 影響リポジトリの CSV: package@old→new を入れると、リポジトリ URL・リスクスコア(0-100)・スター数・根拠(package.json や import の該当箇所)を、依存 5 万未満のパッケージなら 30 秒以内に出す","auto-PR の下書き: 上位 50 の 3 割以上(バンプや小さな shim で済む変更)に、1 行コミットと changelog 込みの提出可能なブランチ + PR diff を生成。PR 作成はメンテナが GitHub App でリポジトリを OAuth 承認した後のみ","影響サマリーカード: 予想破壊数(レンジ)、理由つき危険依存先トップ 3(import パスと該当行)、推奨対応(revert / shim / semver パッチ)を 1 枚の PDF/Slack カードで 90 秒以内に生成"],"exclusions":["優先度付けと auto-PR 雛形の無い、上流/下流グラフを見せるだけの汎用「依存グラフ可視化」ツール","下流リポジトリで CI やテストを回すだけのツール(本製品は下流 CI を実行しない)","セキュリティ勧告を公開するだけの advisory/policy レジストリ(廃止影響と auto-PR ではない)"]},"hash":"d02e512486635e37a3a4ebd663ca8b26daf50cc9628142dfa213f7fb26f43fe6","factChecks":[]},{"id":"bf-2026-08-09-anthropic","proposedAt":"2026-08-09","proposedBy":"anthropic","card":{"name":"OralDefenseKit","oneLiner":"Turns a student's submitted paper into a printable set of 8-12 paper-specific oral defense questions plus a scoring rubric in under 60 seconds, so instructors can run Denmark-style oral checks without writing questions by hand.","target":"University instructors and TAs now required (or choosing) to add oral defenses to written coursework to catch AI-written submissions, who currently write ad-hoc questions themselves or skim the paper minutes before the session.","pain":"time — with mandatory oral checks on every submission, a professor with 150 students needs 15-30 min of prep per paper just to write good probing questions; that's 40-75 hours per course per term with zero tooling support today.","form":"Web app: upload PDF/docx, get a per-student question sheet referencing exact quotes/citations from that paper, a fillable rubric (originality/understanding/citation-accuracy), and an exportable timestamped PDF report per session for the academic integrity file.","whyNotYet":"Incumbents (Turnitin, Coursera, LMS vendors) are built around detection-after-the-fact, not live-defense prep, and their sales cycles are 12-18 months; the Denmark mandate is only weeks old so no vendor has repositioned yet — an indie can ship the narrow question-generation + rubric workflow before the big suites bolt it on.","first10":"Direct outreach to CS/humanities professors posting on Twitter/HN about the Denmark oral-defense news, plus a free tier for single-course use that requires no procurement approval.","moneyPath":"Departments or individual instructors pay $3-5 per enrolled student per term (or a flat $200/course license) because the audit-trail export is needed for academic integrity disputes and grading standardization across multiple TAs — a generic ChatGPT prompt doesn't produce a defensible, exportable per-student record.","buildSize":"2 people x 10 weeks — includes PDF/docx ingestion, quote-anchored question generation, rubric template, PDF export; excludes live video proctoring, LMS grade-sync, and plagiarism detection.","bigRisk":"mid","bigRiskReason":"Turnitin or a major LMS ships a built-in 'oral defense question generator' feature bundled free with existing detection suites, killing the standalone niche.","jpOnly":false,"probability":42,"features":["Given an uploaded PDF/docx, outputs 8-12 questions each quoting or citing a specific passage from that document, within 60 seconds","Produces a fillable rubric template with named scoring rows (originality, understanding, citation accuracy) tied to the same document","Exports a timestamped PDF session report per student listing questions asked, grader notes, and pass/fail flag"],"exclusions":["Live video-proctored oral exam platforms with webcam/ID verification are a different shape and don't count","Generic AI chatbot Q&A tools that quiz on arbitrary topics without anchoring to the submitted document don't count"],"judge":{"date":"2027-02-09","source":"Product Hunt daily top 5 in Education category, or public claim of 25+ paying institutions/instructors on the product's own site cross-checked via web archive","teamMax":5},"id":"bf-2026-08-09-anthropic","proposedAt":"2026-08-09","proposedBy":"anthropic"},"ja":{"name":"OralDefenseKit","oneLiner":"学生の提出論文を 60 秒以内に、その論文固有の口頭試問 8〜12 問 + 採点ルーブリックの印刷用セットに変える。デンマーク型の口頭確認を、手作業の設問なしで回せる","target":"AI 代筆を見抜くため書面課題に口頭試問を足すことになった(または自主的に足す)大学教員と TA。今は場当たりで設問を自作するか、直前に論文を流し読みしている","pain":"時間 — 全提出物に口頭確認が必須になると、学生 150 人の教授は 1 本あたり 15〜30 分の設問準備が要る。1 学期 1 科目で 40〜75 時間。今は支援ツールがゼロ","form":"Web アプリ: PDF/docx をアップロードすると、その論文の引用箇所を明示した学生ごとの設問シート、記入式ルーブリック(独自性/理解度/引用の正確さ)、学術不正ファイル用のタイムスタンプ付きセッション報告 PDF が出る","moneyPath":"学科か教員個人が学生 1 人 1 学期 $3〜5(または 1 科目 $200 の定額)を払う。監査証跡の出力は不正審査と複数 TA 間の採点標準化に必要で、汎用 ChatGPT プロンプトでは審査に耐える学生別記録が出ないため","whyNotYet":"既存勢(Turnitin、Coursera、LMS ベンダー)は事後検出が主軸で、ライブ試問の準備支援ではない。営業サイクルも 12〜18 か月。デンマークの義務化はまだ日が浅く、どのベンダーも転回できていない — 個人開発者なら設問生成 + ルーブリックの狭いワークフローを大手が後付けする前に出せる","first10":"デンマークの口頭試問ニュースに反応して Twitter/HN に投稿している CS・人文系教授への直接アプローチ + 調達承認の要らない 1 科目無料枠","bigRiskReason":"Turnitin か大手 LMS が既存の検出スイートに無料同梱の「口頭試問設問ジェネレーター」を出し、単体ニッチが消える","buildSize":"2 人 × 10 週間 — PDF/docx 取り込み、引用アンカー付き設問生成、ルーブリック雛形、PDF 出力を含む。ライブ映像監視、LMS 成績同期、剽窃検出は含まない","judgeSource":"Product Hunt の Education カテゴリでデイリー Top 5、または製品サイト上の 25+ 有料機関/教員の公表(web archive で照合)","features":["PDF/docx をアップロードすると、その文書の特定の一節を引用・参照した設問 8〜12 問を 60 秒以内に出力","同じ文書に紐づく採点行(独自性、理解度、引用の正確さ)を持つ記入式ルーブリック雛形を生成","学生ごとに、出題した設問・採点者メモ・合否フラグを載せたタイムスタンプ付きセッション報告 PDF を出力"],"exclusions":["Web カメラ・本人確認つきのライブ映像監視型口頭試験プラットフォームは別の形なので数えない","提出文書に紐づかず任意の話題で出題する汎用 AI チャット Q&A ツールは数えない"]},"hash":"59833974c04f2e690e10b4ea8faefdf6ccba2f3978336063d839ea8be50f9124","factChecks":[]},{"id":"bf-2026-08-09-gemini","proposedAt":"2026-08-09","proposedBy":"gemini","card":{"name":"OralDefend","oneLiner":"A lightweight web platform for educators that ingests student essays, auto-generates 5 highly specific oral-defense questions based on linguistic anomalies in the text, and provides a 5-minute structured evaluation flow to verify authorship.","target":"University professors and high school humanities teachers who currently cope by running essays through unreliable AI detectors (like GPTZero) or manually scanning for off-topic paragraphs.","pain":"Time and legal risks. Educators waste dozens of hours manually auditing suspicious essays, and face immense legal or administrative backlash if they falsely accuse a student of cheating based on faulty automated AI detectors.","form":"A responsive web application where teachers upload student essays (PDF/DOCX) and receive a printable 1-page 'Oral Defense Guide' containing text-specific questions and a scoring rubric.","whyNotYet":"Incumbents like Turnitin are focused on passive, automated detection algorithms rather than facilitating the active human-in-the-loop verification processes now legally required by forward-looking districts like Denmark. An indie developer can build a workflow-first tool rather than trying to build a better detection model.","first10":"Teachers in Europe and the US who are actively banned by their institutions from using automated 'AI detectors' due to false positives, but still need a rapid, structured way to verify suspicious student papers.","moneyPath":"Individual educators or department heads pay $15/month to bypass a 3-essay monthly free tier, allowing them to instantly generate defense rubrics for their entire roster of suspect papers. They pay to avoid administrative conflict and protect their time.","buildSize":"1 developer x 4 weeks. Includes: Auth, file upload/parsing (PDF/DOCX), prompt engineering templates optimized to identify logical leaps or vocabulary mismatches, and a clean, printable UI output.","bigRisk":"low","bigRiskReason":"The main risk is schools outright banning oral defenses due to student anxiety complaints, but the global trend is moving toward oral defenses as the only bulletproof way to counter LLM-generated submissions.","jpOnly":false,"probability":78,"features":["Input: A raw student essay (PDF/DOCX). Output: 5 highly specific conceptual questions targeting potential logical leaps or vocabulary anomalies in the text.","A structured grading rubric (1 to 5 scale) for each question to help teachers objectively score the student's verbal responses in under 5 minutes.","A student-facing 'Prep Sheet' that highlights the key themes of their own paper to ensure a fair assessment, generated alongside the teacher's guide."],"exclusions":["Generic AI text detection software (e.g., GPTZero, Copyleaks) that outputs a percentage probability score of AI generation without providing a physical interview guide."],"judge":{"date":"2027-02-09","source":"A dedicated GitHub repository hosting this specific oral defense tool shape reaching 500 stars, or a SaaS product launching this specific feature set reaching the top 10 on Product Hunt within the next 6 months.","teamMax":5},"id":"bf-2026-08-09-gemini","proposedAt":"2026-08-09","proposedBy":"gemini"},"ja":{"name":"OralDefend","oneLiner":"教育者向けの軽量 Web プラットフォーム。学生の小論文を取り込み、本文の言語的な不自然さに基づく 5 問の口頭試問を自動生成し、5 分で回せる構造化評価フローで執筆者本人かを確認する","target":"今は信頼性の低い AI 検出器(GPTZero 等)に通すか、話題のずれた段落を手作業で探している大学教授と高校の人文系教員","pain":"時間と法的リスク。疑わしい小論文の手動監査に何十時間も費やし、精度の低い自動 AI 検出器を根拠に誤って不正を指摘すれば重大な法的・行政的反発を受ける","form":"教員が小論文(PDF/DOCX)をアップロードすると、本文固有の設問と採点ルーブリックを載せた印刷用 1 枚の「口頭試問ガイド」が返るレスポンシブ Web アプリ","moneyPath":"教員個人か学科長が月 $15 を払い、月 3 本の無料枠を超えて疑わしい論文全員分の試問ルーブリックを即時生成する。行政的な揉め事の回避と時間の防衛に金を払う","whyNotYet":"Turnitin のような既存勢は受動的な自動検出アルゴリズムに集中していて、人間が確認するアクティブな検証ワークフローの支援ではない。個人開発者は検出モデルの精度競争ではなくワークフロー第一のツールを作れる","first10":"誤検出を理由に機関から自動「AI 検出器」の使用を禁じられているが、疑わしい論文を素早く構造的に検証する手段は必要な欧州・米国の教員","bigRiskReason":"学生の不安の訴えで学校が口頭試問自体を禁止するのが最大リスク。ただし世界の流れは、LLM 代筆への唯一確実な対抗策として口頭試問に向かっている","buildSize":"1 人 × 4 週間。認証、ファイルアップロードと解析(PDF/DOCX)、論理の飛躍や語彙の不一致を見つけるプロンプト雛形、印刷向けのきれいな UI 出力を含む","judgeSource":"この口頭試問ツールの形を実装した GitHub リポジトリが 500 スター、またはこの機能セットの SaaS が 6 か月以内に Product Hunt Top 10","features":["入力: 学生の小論文(PDF/DOCX)。出力: 本文の論理の飛躍や語彙の不自然さを突く、具体性の高い概念質問 5 問","各設問に 1〜5 点の構造化採点ルーブリック。口頭回答を 5 分以内に客観採点するための補助","教員用ガイドと同時に、学生向けの「準備シート」も生成。自分の論文の主要テーマを提示して公平な評価を担保する"],"exclusions":["面談ガイドを出さず AI 生成確率のスコアだけを返す汎用 AI 文章検出ソフト(GPTZero、Copyleaks 等)"]},"hash":"df688172d120998f8b0739af30278387847820e68c48f2d0e5d3de346aee325a","factChecks":[{"by":"ai","model":"openai","en":"Turnitin's 'Authorship Investigate' (part of Turnitin Authorship) provides instructor-facing investigatory workflows and human-in-the-loop support for verifying authorship, contradicting the claim that incumbents only focus on passive automated detection; additionally, there is no Danish national le","ja":"Turnitin の「Authorship Investigate」(Turnitin Authorship の一部)は、作者性検証のための教員向け調査ワークフローと人間参加の支援を提供しており、「既存勢は受動的な自動検出だけ」という主張と矛盾する。加えて、デンマークの国家的な法…(出力はここで途切れている)"},{"by":"editorial","en":"A Danish mandate does exist: announced Aug 7, 2026 by the Ministry of Education and effective immediately - but it covers upper-secondary schools (not universities, and Denmark is a country, not a 'district').","ja":"デンマークの義務化は実在する(2026-08-07 に教育省が発表、即日施行)。ただし対象は後期中等教育で大学は含まれない(なお「地区(district)」ではなく国の措置)","source":"https://www.cnn.com/2026/08/07/europe/ai-cheating-measures-schools-denmark-intl-scli"}]},{"id":"bf-2026-08-09-xai","proposedAt":"2026-08-09","proposedBy":"xai","card":{"name":"PaperOralKit","oneLiner":"Professors drop a student thesis PDF and receive a complete 15-minute oral-defense script with page-cited questions and model answers so they can catch AI-written work without spending an evening prepping","target":"University professors and TAs who currently rely on Turnitin similarity scores plus ad-hoc or skipped oral questions","pain":"time (1-3 hours of manual prep per paper; AI submission volume makes it unsustainable)","form":"Web app with PDF upload, one-click script export to PDF/Markdown, optional student mock-timer link","whyNotYet":"Incumbents (Turnitin, Gradescope, LMS vendors) stay on text-similarity and auto-graders because oral-script generation needs reliable long-context citation tying they treat as low-priority edge case; indie ships the narrow PDF-to-script loop in weeks","first10":"Free single-paper tier posted to r/Professors, Danish university staff lists, and the HN thread on the new oral-defense law within 48h of launch","moneyPath":"Individual instructors pay $9/mo or $4 per extra paper; departments buy $400/yr site licenses because generic ChatGPT questions lack page citations and audit logs they need for grade appeals","buildSize":"1 person x 5 weeks (PDF text+structure extract, constrained question gen, script UI + export, mock timer; exclude LMS plugins, video proctoring, languages beyond EN/DA)","bigRisk":"high","bigRiskReason":"Turnitin or Google Classroom ships a native 'generate oral questions from uploaded paper' button in the next academic term","jpOnly":false,"probability":48,"features":["Accepts thesis PDF ≤80 pages and returns exactly 8 questions each with page citation in under 90 seconds","Produces a printable defense script containing model answer outlines plus two follow-up probes per question","Includes student mock mode that enforces 15-min timer and flags missing key phrases from the outline"],"exclusions":["Generic quiz or flashcard generators that do not require full-paper upload and page-level citations","Plagiarism or AI-detectors that output only scores without an oral-defense script"],"judge":{"date":"2027-02-09","source":"Product Hunt daily top 5 or ≥300 university-affiliated email signups with at least 50 paid conversions","teamMax":5},"id":"bf-2026-08-09-xai","proposedAt":"2026-08-09","proposedBy":"xai"},"ja":{"name":"PaperOralKit","oneLiner":"教授が学生の論文 PDF を置くと、ページ引用つきの設問と模範解答を備えた 15 分の口頭試問台本が返る。夜なべの準備なしで AI 代筆を見抜ける","target":"今は Turnitin の類似度スコア + 場当たりの口頭質問(または省略)に頼っている大学教授と TA","pain":"時間(1 本あたり 1〜3 時間の手動準備。AI 提出物の量で持続不能になっている)","form":"PDF アップロードの Web アプリ。台本をワンクリックで PDF/Markdown 出力、学生用の模擬タイマーリンクも任意で発行","moneyPath":"教員個人は月 $9(追加 1 本 $4)、学科は年 $400 のサイトライセンス。汎用 ChatGPT の設問にはページ引用と、成績異議に必要な監査ログが無いため","whyNotYet":"既存勢(Turnitin、Gradescope、LMS ベンダー)は文章類似度と自動採点に留まる。口頭試問の台本生成には長文の確実な引用ひも付けが要り、優先度の低い端ケース扱いされている。個人開発者なら PDF→台本の狭いループを数週間で出せる","first10":"公開後 48 時間以内に、1 本無料枠を r/Professors、デンマークの大学スタッフのメーリングリスト、新しい口頭試問法の HN スレッドに投下","bigRiskReason":"Turnitin か Google Classroom が来学期に「アップロードした論文から口頭試問を生成」ボタンを標準搭載する","buildSize":"1 人 × 5 週間(PDF のテキスト+構造抽出、制約付き設問生成、台本 UI と出力、模擬タイマー。LMS プラグイン、映像監視、EN/DA 以外の言語は除外)","judgeSource":"Product Hunt デイリー Top 5、または大学ドメインのメール登録 300 件以上 + 有料転換 50 件以上","features":["80 ページ以下の論文 PDF を受け取り、ページ引用つきの設問ちょうど 8 問を 90 秒以内に返す","設問ごとに模範解答の骨子と追い質問 2 つを備えた印刷用の試問台本を生成","15 分タイマーを強制し、骨子の必須フレーズの欠落を検出する学生用モックモードを同梱"],"exclusions":["論文全体のアップロードとページ単位の引用を要さない汎用クイズ・単語帳ジェネレーター","口頭試問の台本を出さずスコアだけを返す剽窃・AI 検出器"]},"hash":"e784cb523445415d7e2d83786abfb9d8b241efa213afca8539c030c6d1079a62","factChecks":[]},{"id":"bf-2026-08-09-moonshot","proposedAt":"2026-08-09","proposedBy":"moonshot","card":{"name":"VivaKit","oneLiner":"For instructors now legally required to orally verify each student's written work: upload the essays and get per-student question cards anchored to specific paragraphs, self-scheduled 10-minute defense slots, and a signed PDF minute per session — a 30-student class prepped in about an hour instead of a lost weekend.","target":"University and gymnasium instructors in Denmark (and copycat jurisdictions adopting oral-defense mandates this semester); today they cope with Calendly + Zoom + re-reading every essay the night before and scribbling notes in Word, or lean on Turnitin, which only flags suspicion and runs no defense.","pain":"Time: 30 students x (prep + scheduling + 10-min call + write-up) is 8-12 hours per assignment per class. Legal: grades from oral defenses are appealable, so the institution must be able to prove what was asked and when, under GDPR — a Word doc on a laptop does not survive an appeal.","form":"Web app: PDF/DOCX essay upload -> per-student question cards (each question cites the paragraph it probes, with 'claims only the author can explain' follow-ups) -> public booking page for 10-min slots -> browser call room that starts recording only after an on-screen consent step -> one-click signed PDF minute (student, timestamp, questions asked, verdict) for the gradebook file. Danish and English UI.","whyNotYet":"Incumbents skip it: Turnitin's business is detection scores, not live verification, and LMS vendors big in Scandinavia (itslearning, Moodle partners) run 18-month roadmaps — a one-country mandate in a small language market never wins a sprint. The indie gap: the valuable parts are unglamorous localization — Danish-language UI, GDPR-compliant recording retention, and an appeal-proof minute format — none of which require scale, just speed, and the mandate hits this semester, not next roadmap.","first10":"Danish instructors are already complaining in union newsletters, teacher Facebook groups, and Gymnasieskolen/Folkeskolen comment threads about how to run these defenses this fall; a Danish-language landing page posted in those channels with a free first-class tier converts 10 pilot instructors within weeks of semester start, before any procurement process exists.","moneyPath":"Instructors pay EUR 149-249 per course per semester out of pocket (or departments EUR 3-8k/yr site-wide) because the workflow is legally non-optional and the appeal-proof documentation is the part they cannot improvise; free options (Calendly+Zoom) produce no paragraph-anchored cards and no signed minute, and Turnitin only says 'maybe AI' — it cannot run or document the defense.","buildSize":"2 people x 10 weeks. Included: essay parsing, question-card generation, slot booking, WebRTC call room with consent-gated recording, signed PDF minute export, da/en UI. Excluded: LMS gradebook sync, plagiarism detection, mobile apps, proctoring.","bigRisk":"mid","bigRiskReason":"itslearning or Turnitin bundles a native 'oral defense' module into contracts institutions already hold, announced before the spring 2027 semester — distribution beats the indie even with a worse product.","jpOnly":false,"probability":40,"features":["Given a student essay (PDF/DOCX), the product outputs a per-student card of at least 5 questions, each visibly citing the paragraph number it probes — verifiable by uploading any sample essay.","Each completed session produces a downloadable signed PDF minute containing student name, timestamp, the questions asked, and the verdict, without contacting support.","Students self-book 10-minute slots on a public scheduling page, and the built-in browser call room records only after an on-screen consent step."],"exclusions":["AI-proctoring or camera-surveillance exam tools do not count.","Pure AI-text detectors that output a probability score (Turnitin-style) without running or documenting a live defense do not count.","Writing-time authorship attestation (e.g., CommitWitness-style commit signing) does not count — this shape verifies comprehension after submission, in a live session.","Generic point tools (Calendly for slots, Zoom for calls) used separately do not count."],"judge":{"date":"2027-02-09","source":"Public customer list, case studies, or Danish education-press coverage (e.g., Gymnasieskolen, Folkeskolen, Uniavisen) showing >= 5 educational institutions using such a tool for live oral defenses by judge date, or a launch reaching Product Hunt daily top 5 whose description centers on oral-defense/verification sessions.","teamMax":5},"id":"bf-2026-08-09-moonshot","proposedAt":"2026-08-09","proposedBy":"moonshot"},"ja":{"name":"VivaKit","oneLiner":"書面課題の口頭確認が義務になった教員向け。小論文をまとめてアップロードすると、段落に紐づく学生別の設問カード、セルフ予約の 10 分試問枠、セッションごとの署名付き議事 PDF が揃う。30 人クラスの準備が「潰れる週末」から約 1 時間になる","target":"デンマーク(と今学期義務化に追随する地域)の大学・ギムナジウムの教員。今は Calendly + Zoom + 前夜の再読 + Word のメモでしのぐか、疑いのフラグを立てるだけで試問はしてくれない Turnitin に頼っている","pain":"時間: 30 人 ×(準備 + 日程調整 + 10 分の通話 + 記録)で課題 1 本につき 8〜12 時間。法務: 口頭試問の成績は異議申立の対象になるため、機関は GDPR の下で「何をいつ聞いたか」を証明できる必要がある — ノート PC の Word 文書では審査に耐えない","form":"Web アプリ: PDF/DOCX の小論文アップロード → 学生別設問カード(各設問が根拠段落を引用し、「執筆者しか説明できない主張」への追い質問つき)→ 10 分枠の公開予約ページ → 画面上の同意ステップ後にのみ録画が始まるブラウザ通話室 → 成績簿ファイル用のワンクリック署名付き議事 PDF(学生、タイムスタンプ、出題、判定)。デンマーク語と英語の UI","moneyPath":"教員が自腹で 1 科目 1 学期 149〜249 ユーロ(学科なら年 3〜8 千ユーロのサイト契約)。ワークフローが法的に必須で、異議に耐える文書化だけは即席で作れないため。無料の組み合わせ(Calendly+Zoom)では段落アンカーの設問カードも署名付き議事も出ず、Turnitin は「AI かも」と言うだけで試問の実施も記録もできない","whyNotYet":"既存勢は素通り: Turnitin の商売は検出スコアでライブ検証ではなく、北欧で強い LMS ベンダー(itslearning、Moodle パートナー)は 18 か月ロードマップで動く — 小言語圏の一国義務化はスプリントで勝てない。個人開発の隙間: 価値の核が地味なローカライズ(デンマーク語 UI、GDPR 準拠の録画保持、異議に耐える議事フォーマット)で、規模でなく速度の勝負。義務化は来期でなく今学期に効いている","first10":"デンマークの教員は既に組合ニュースレターや教員 Facebook グループ、Gymnasieskolen/Folkeskolen のコメント欄で「この秋どう試問を回すか」を嘆いている。それらのチャネルにデンマーク語の LP + 最初の 1 クラス無料枠を出せば、調達プロセスが立ち上がる前の学期初めに 10 人のパイロット教員が付く","bigRiskReason":"itslearning か Turnitin が、機関の既存契約に「口頭試問」モジュールを同梱して 2027 年春学期前に発表する — 製品が劣っていても流通が個人開発者に勝つ","buildSize":"2 人 × 10 週間。含む: 小論文解析、設問カード生成、枠予約、同意ゲート付き録画の WebRTC 通話室、署名付き議事 PDF 出力、da/en UI。含まない: LMS 成績同期、剽窃検出、モバイルアプリ、監視(プロクタリング)","judgeSource":"判定日までに、公開顧客リスト・事例・デンマーク教育系メディア(Gymnasieskolen、Folkeskolen、Uniavisen 等)で 5 機関以上がライブ口頭試問にこの種のツールを使っている報道、または口頭試問/検証セッションを中核に据えた製品の Product Hunt デイリー Top 5","features":["小論文(PDF/DOCX)から、学生ごとに 5 問以上の設問カードを生成。各設問は根拠にした段落番号を明示 — 任意のサンプル小論文のアップロードで検証可能","完了した各セッションから、学生名・タイムスタンプ・出題・判定を載せた署名付き議事 PDF をサポート問い合わせなしでダウンロードできる","学生は公開予約ページで 10 分枠を自己予約。内蔵のブラウザ通話室は画面上の同意ステップの後にのみ録画を開始する"],"exclusions":["AI 監視・カメラ監視型の試験ツールは数えない","確率スコアを出すだけの純粋な AI 文章検出器(Turnitin 型)で、ライブ試問の実施・記録をしないものは数えない","執筆時の作者性証明(CommitWitness 型のコミット署名など)は数えない — この形は提出後にライブセッションで理解度を検証する","汎用の単機能ツールの組み合わせ(予約の Calendly、通話の Zoom)は数えない"]},"hash":"cd9ae693872cf151158712d0ee3d10c4a2f2c77a4bd6a7b296c702f554b7401b","factChecks":[{"by":"editorial","en":"The Danish mandate (announced Aug 7, 2026, effective immediately) covers upper-secondary education, including about 9,000 HF-programme students - not universities. 'University instructors now legally required' overstates the scope.","ja":"デンマークの義務化(2026-08-07 発表、即日施行)は後期中等教育が対象で、HF 課程の約 9,000 人を含む。大学は対象外 — 「大学教員が法的に義務付けられた」は範囲の誇張","source":"https://www.cnn.com/2026/08/07/europe/ai-cheating-measures-schools-denmark-intl-scli"}]},{"id":"bf-2026-08-09-mistral","proposedAt":"2026-08-09","proposedBy":"mistral","card":{"name":"OralDefense Proxy for Academic Integrity","oneLiner":"A self-hosted, browser-based proxy that records and timestamps oral defenses for written assignments (e.g., essays, code, theses) to satisfy institutional anti-AI-cheating policies, cutting faculty grading time by 40% while preserving student privacy.","target":"University faculty and TAs at institutions adopting oral defenses (e.g., Denmark, Netherlands) who currently use Zoom/Teams + manual notes or plagiarism detectors (Turnitin) to verify student work.","pain":"Time: Faculty spend 3-5 hours per class manually scheduling, conducting, and documenting oral defenses; legal: institutions risk GDPR violations by recording students without explicit consent tools.","form":"A single-page web app (self-hosted or cloud-hosted) that integrates with LMS (Canvas, Moodle) via LTI, records audio/video with client-side encryption, and generates timestamped PDF transcripts + SHA-256 hashes of the original work for audit trails.","whyNotYet":"Incumbents (Zoom, Turnitin) skip it because oral defenses are a niche workflow outside their core products, and they lack incentives to build GDPR-compliant, self-hostable tools. The gap: a lightweight, privacy-preserving proxy that automates the bureaucratic overhead of oral defenses.","first10":"The first 10 users are faculty at Danish universities (signal: Denmark’s new policy) who are already conducting oral defenses manually and will adopt a tool that cuts their workload by 40% while satisfying institutional compliance requirements.","moneyPath":"Institutions pay $500–$2,000/year for a site license (scalable by student count) because they cannot use free options (e.g., Zoom recordings lack GDPR-compliant consent flows, timestamping, or LMS integration) and need audit trails to defend against student appeals.","buildSize":"1 person x 8 weeks: includes LTI integration, client-side encryption, PDF transcript generation, and a basic admin dashboard. Excludes: AI transcription (uses open-source Whisper), mobile apps, or plagiarism detection.","bigRisk":"mid","bigRiskReason":"A major LMS (e.g., Canvas) ships native oral defense recording with GDPR-compliant consent flows within 6 months, making the proxy redundant.","jpOnly":false,"probability":65,"features":["Generates a PDF transcript with timestamps and SHA-256 hashes of the original assignment within 5 minutes of recording completion, verifiable by a third party.","Integrates with Canvas/Moodle via LTI to auto-populate student rosters and assignment metadata, reducing manual data entry.","Records audio/video with client-side encryption (WebRTC + local storage) and deletes raw files after 30 days unless manually archived by the institution."],"exclusions":["A tool that only records oral defenses without timestamped, verifiable transcripts or LMS integration does not count."],"judge":{"date":"2027-02-09","source":"GitHub 500 stars OR 10 institutional customers (verified via public case studies or testimonials on university websites)","teamMax":5},"id":"bf-2026-08-09-mistral","proposedAt":"2026-08-09","proposedBy":"mistral"},"ja":{"name":"OralDefense Proxy for Academic Integrity","oneLiner":"書面課題(小論文、コード、学位論文)の口頭試問を録画・タイムスタンプ記録するセルフホストのブラウザ型プロキシ。機関の AI 不正対策ポリシーを満たしつつ、学生のプライバシーを守り、教員の採点時間を 4 割削る","target":"口頭試問を導入する機関(例: デンマーク)の大学教員と TA。今は Zoom/Teams + 手動メモ、または剽窃検出器(Turnitin)で学生の成果物を確認している","pain":"時間: 口頭試問の日程調整・実施・記録を手作業でやると 1 クラス 3〜5 時間。法務: 明示同意の仕組みなしに学生を録画すると GDPR 違反のリスク","form":"LMS(Canvas、Moodle)と LTI 連携する単一ページ Web アプリ(セルフホスト/クラウド)。クライアント側暗号化で音声・映像を録画し、タイムスタンプ付き PDF 起こしと元課題の SHA-256 ハッシュを監査証跡として生成する","moneyPath":"機関が年 $500〜2,000 のサイトライセンス(学生数でスケール)を払う。無料の選択肢が使えない(Zoom の録画には GDPR 準拠の同意フロー、タイムスタンプ、LMS 連携が無い)うえ、学生の異議申立に備える監査証跡が必要なため","whyNotYet":"既存勢(Zoom、Turnitin)にとって口頭試問はコア製品の外のニッチワークフローで、GDPR 準拠のセルフホスト可能なツールを作る動機が無い。隙間: 口頭試問の官僚的な手間を自動化する、軽量でプライバシー第一のプロキシ","first10":"最初の 10 人はデンマークの大学教員(シグナル: 新方針)。既に手作業で口頭試問を回していて、作業を 4 割削りつつ機関のコンプライアンス要件を満たすツールなら採用する","bigRiskReason":"大手 LMS(例: Canvas)が 6 か月以内に GDPR 準拠の同意フロー付きネイティブ録画を出し、プロキシが不要になる","buildSize":"1 人 × 8 週間: LTI 連携、クライアント側暗号化、PDF 起こし生成、簡易管理ダッシュボードを含む。AI 文字起こし(オープンソースの Whisper を利用)、モバイルアプリ、剽窃検出は含まない","judgeSource":"GitHub 500 スター、または機関顧客 10 件(大学サイトの公開事例・推薦文で確認)","features":["録画完了から 5 分以内に、タイムスタンプと元課題の SHA-256 ハッシュを載せた PDF 起こしを生成。第三者が検証できる","Canvas/Moodle と LTI 連携し、学生名簿と課題メタデータを自動投入して手入力を減らす","クライアント側暗号化(WebRTC + ローカル保存)で音声・映像を録画し、機関が手動アーカイブしない限り 30 日で元ファイルを削除する"],"exclusions":["タイムスタンプ付きの検証可能な起こしや LMS 連携なしに、口頭試問を録画するだけのツールは数えない"]},"hash":"d135e34dbe898d8901ad96a6e157faf3cd4d453e432a5da6c08427fb78a82b0f","factChecks":[{"by":"ai","model":"openai","en":"BigBlueButton is an existing open-source, self-hosted, LMS-integrated web conferencing system that records audio/video (used for defenses/meetings), supports LTI and self-hosting, and is GDPR-friendly, contradicting the claim that incumbents have skipped this niche entirely.","ja":"BigBlueButton は既存のオープンソース・セルフホスト・LMS 連携の Web 会議システムで、音声・映像の録画(試問や会議で利用)、LTI、セルフホストに対応し GDPR 親和的。「既存勢はこのニッチを完全に素通りしてきた」という主張と矛盾する"},{"by":"editorial","en":"No public evidence was found of a Netherlands oral-defence mandate. The verifiable mandate is Denmark's (announced Aug 7, 2026), and it covers upper-secondary schools, not universities.","ja":"オランダの口頭試問義務化は公開情報で確認できなかった。確認できる義務化はデンマーク(2026-08-07 発表)のみで、対象は後期中等教育。大学は含まれない","source":"https://www.cnn.com/2026/08/07/europe/ai-cheating-measures-schools-denmark-intl-scli"}]},{"id":"bf-2026-08-09-alibaba","proposedAt":"2026-08-09","proposedBy":"alibaba","card":{"name":"VivaProof","oneLiner":"Gives teachers who must run oral defenses a 15-minute defense kit per paper: page-linked questions, scoring rubric, and a signed audit record.","target":"Upper-secondary and university instructors, especially in Denmark, who must verify student written work; today they prepare questions by hand, conduct vivas via Zoom or in person, and keep signed forms in spreadsheets or email.","pain":"Time and legal: 15-30 minutes of question prep per paper, and exam rules require a defensible record that the student can explain the submitted work.","form":"Web app: upload PDF/DOCX, generate document-linked question packet, schedule iCal event, examiner scores live, export signed PDF/JSON; excludes proctoring and plagiarism detection.","whyNotYet":"Incumbents skip it because LMS and plagiarism vendors focus on submission and similarity checks; the indie gap is a narrow regulation-triggered oral-defense workflow with page citations, consent, examiner signature, and school-controlled retention.","first10":"Direct outreach to Danish gymnasium and university teachers and exam officers reacting to the oral-defense rule, plus teacher-association forums, with a free one-class pilot that exports an audit report.","moneyPath":"Teachers or schools pay EUR 9 per defense or EUR 299 per semester for 100 defenses because it saves prep time and creates a legally reviewable record; free generic chat tools cannot provide page-linked provenance, examiner signature, retention controls, or school-controlled export.","buildSize":"1 person x 8 weeks; includes upload parsing, page-linked question generation, rubric scoring, iCal scheduling, signed PDF/JSON export; excludes SSO/LTI, plagiarism or authorship detection, proctoring, mobile apps, and multi-language UI.","bigRisk":"high","bigRiskReason":"A ministry or major LMS ships native oral-defense and audit workflow, or schools decide paper/Zoom plus manual notes satisfies regulation and refuse another paid tool.","jpOnly":false,"probability":45,"features":["Accepts one text-based PDF or DOCX up to 100 pages and produces at least 10 defense questions, each with a page or paragraph citation, within 5 minutes.","Examiner scoring screen exports a PDF/JSON record containing student identifier, examiner name, timestamp, rubric scores, and SHA-256 of the uploaded file.","Generates a 15-minute iCal or Google Calendar defense event and a printable one-page packet containing questions, consent line, and scoring rubric."],"exclusions":["A plagiarism checker or authorship-probability classifier that returns a likelihood score without producing an oral-defense scoring record.","A generic flashcard or presentation-practice tool that does not bind questions to the uploaded document and does not export a signed audit record."],"judge":{"date":"2027-02-09","source":"GitHub repo for a matching service reaches 750 stars or Product Hunt daily top 5","teamMax":5},"id":"bf-2026-08-09-alibaba","proposedAt":"2026-08-09","proposedBy":"alibaba"},"ja":{"name":"VivaProof","oneLiner":"口頭試問を課された教員に、論文 1 本につき 15 分の試問キットを渡す: ページに紐づく設問、採点ルーブリック、署名付き監査記録","target":"学生の書面成果物の確認を課された、特にデンマークの後期中等・大学教員。今は設問を手作りし、Zoom か対面で試問し、署名済みの用紙をスプレッドシートやメールで管理している","pain":"時間と法務: 論文 1 本あたり 15〜30 分の設問準備。試験規則は「学生が提出物を説明できること」の防御可能な記録を要求する","form":"Web アプリ: PDF/DOCX をアップロード → 文書に紐づく設問パケットを生成 → iCal 予定を作成 → 試問官がライブで採点 → 署名付き PDF/JSON を出力。監視と剽窃検出は含まない","moneyPath":"教員か学校が試問 1 件 9 ユーロ、または 100 件 1 学期 299 ユーロを払う。準備時間の節約と、法的に確認可能な記録が作れるため。無料の汎用チャットツールにはページ紐づけの出所、試問官の署名、保持管理、学校管理の出力が無い","whyNotYet":"既存勢は素通り: LMS と剽窃検出ベンダーは提出と類似度チェックに集中している。個人開発の隙間は、ページ引用・同意・試問官署名・学校管理の保持を備えた、規制発の狭い口頭試問ワークフロー","first10":"口頭試問ルールに反応しているデンマークのギムナジウム・大学の教員と試験担当官への直接アプローチ + 教員団体フォーラム。監査レポートを出力できる 1 クラス無料パイロット付き","bigRiskReason":"省庁か大手 LMS がネイティブの口頭試問 + 監査ワークフローを出す、または「紙と Zoom と手動メモで規制は満たせる」と学校が判断して新たな有料ツールを拒む","buildSize":"1 人 × 8 週間。アップロード解析、ページ紐づけ設問生成、ルーブリック採点、iCal 日程、署名付き PDF/JSON 出力を含む。SSO/LTI、剽窃・作者性検出、監視、モバイルアプリ、多言語 UI は含まない","judgeSource":"該当サービスの GitHub リポジトリが 750 スター、または Product Hunt デイリー Top 5","features":["テキストベースの PDF/DOCX(100 ページ以下)1 本から、ページまたは段落の引用つき設問 10 問以上を 5 分以内に生成","試問官の採点画面から、学生 ID・試問官名・タイムスタンプ・ルーブリック点・アップロードファイルの SHA-256 を含む PDF/JSON 記録を出力","15 分の iCal / Google カレンダー予定と、設問・同意文・採点ルーブリックを載せた印刷用 1 枚パケットを生成"],"exclusions":["口頭試問の採点記録を出さず、剽窃や作者性の確率スコアだけを返すチェッカー","設問を文書に紐づけず、署名付き監査記録も出さない汎用の単語帳・プレゼン練習ツール"]},"hash":"d8dca04d66df6695b1cf4129080d1a137331b0f01097e36b45532977af9c5cc6","factChecks":[{"by":"editorial","en":"The Danish oral-defence mandate applies to upper-secondary schools; university instructors are not covered by it.","ja":"デンマークの口頭試問義務は後期中等教育(高校)が対象で、大学教員は含まれない","source":"https://www.cnn.com/2026/08/07/europe/ai-cheating-measures-schools-denmark-intl-scli"}]}],"votes":[{"model":"mistral","card_id":"bf-2026-08-08-openai","reason":"PR Provenance Guard hits a clear pain point for maintainers (legal risk + dev time) with a monetizable GitHub Marketplace subscription that free tools can't match.","ja_reason":"PR Provenance Guard はメンテナの明確な痛点(法務リスク + 開発時間)を突く","since":"2026-08-08"},{"model":"gemini","card_id":"bf-2026-08-09-moonshot","reason":"VivaKit addresses a high-stakes compliance requirement (legally non-optional oral verifications) by providing paragraph-anchored questions and appeal-proof audit trails that instructors will gladly pay for out-of-pocket to save their weekends.","ja_reason":"VivaKit は法的に必須の口頭確認という高リスクのコンプライアンス要件に、段落アンカーの設問と異議に耐える監査証跡で応えている。週末を守るためなら教員は自腹でも払う","since":"2026-08-09"},{"model":"deepseek","card_id":"bf-2026-08-09-openai","reason":"DeprecationScope has a clear, urgent, recurring pain point for npm maintainers with measurable cost savings and a concrete willingness to pay for prioritized breakage forecasts and auto-PRs, unlike the thinner, more discretionary value of crawl-toll subscriptions.","ja_reason":"DeprecationScope は npm メンテナの明確で切迫した反復ペインを突いていて、節約コストが測れ、優先度付き破壊予測と auto-PR への支払い意思も具体的。クロール課金のような裁量的な価値より厚い","since":"2026-08-09"},{"model":"anthropic","card_id":"bf-2026-08-08-moonshot","reason":"CommitWitness has the clearest enterprise buyer (compliance-mandated orgs paying per-dev for auditable no-AI-code proof) versus zero-evidence honor systems, making its money path stronger than ParcelGuard's unclear monetization.","ja_reason":"CommitWitness は買い手が最も明確(方針を義務づけられた組織が払う)","since":"2026-08-08"},{"model":"openai","card_id":"bf-2026-08-06-anthropic","reason":"High user demand and simple integration surface make a one-address suspicious-email forwarding + quick model verdict implementable and useful for 1–3 indie devs within six months.","ja_reason":"需要の高さと組み込み面のシンプルさから、転送アドレス 1 つ + 即時判定という形は個人 1〜3 人で半年以内に実装でき、実際に役立つ","since":"2026-08-06"},{"model":"xai","card_id":"bf-2026-08-08-openai","reason":"Clear GitHub Marketplace $5-20/repo subscription with strong ROI (legal risk + hours saved per PR) makes this far more monetizable and likely to ship than pure consumer freemium plays.","ja_reason":"GitHub Marketplace の $5〜20/repo サブスクが明快で、法務リスク削減の ROI が強い","since":"2026-08-08"},{"model":"alibaba","card_id":"bf-2026-08-09-moonshot","reason":"Switching because legally mandated oral defenses create a non-optional per-course payment with an audit-trail moat, stronger than crawler blocking where free lists and CDNs can substitute.","ja_reason":"乗り換えの理由: 法的義務の口頭試問は科目単位の非任意の支払いと監査証跡の堀を生む。無料リストや CDN で代替できるクローラー遮断より強い","since":"2026-08-09"},{"model":"moonshot","card_id":"bf-2026-08-09-anthropic","reason":"Six analysts independently converged on oral-defense kits with a regulatory mandate and out-of-pocket payers, and anthropic's $200/course questions+rubric+audit-export kit is the leanest 1-3-dev build of that shape — while ScamForward, however shippable, still has no credible payer under today's mon","ja_reason":"6 体の分析官が独立に、規制の追い風と自腹の支払者を持つ口頭試問キットに収斂した。中でも anthropic の $200/科目の設問+ルーブリック+監査出力キットは、この形の最小 1〜3 人ビルド。ScamForward は出せはするが、今の枠組みでは信頼できる支払者がいない","since":"2026-08-09"}],"recentEvents":[{"date":"2026-08-09","model":"alibaba","kind":"vote","card_id":"bf-2026-08-09-moonshot","detail":"{\"reason\":\"Switching because legally mandated oral defenses create a non-optional per-course payment with an audit-trail moat, stronger than crawler blocking where free lists and CDNs can substitute.\"}"},{"date":"2026-08-09","model":"moonshot","kind":"vote","card_id":"bf-2026-08-09-anthropic","detail":"{\"reason\":\"Six analysts independently converged on oral-defense kits with a regulatory mandate and out-of-pocket payers, and anthropic's $200/course questions+rubric+audit-export kit is the leanest 1-3-dev build of that shape — while ScamForward, however shippable, still has no credible payer under today's mon\"}"},{"date":"2026-08-09","model":"gemini","kind":"vote","card_id":"bf-2026-08-09-moonshot","detail":"{\"reason\":\"VivaKit addresses a high-stakes compliance requirement (legally non-optional oral verifications) by providing paragraph-anchored questions and appeal-proof audit trails that instructors will gladly pay for out-of-pocket to save their weekends.\"}"},{"date":"2026-08-09","model":"deepseek","kind":"vote","card_id":"bf-2026-08-09-openai","detail":"{\"reason\":\"DeprecationScope has a clear, urgent, recurring pain point for npm maintainers with measurable cost savings and a concrete willingness to pay for prioritized breakage forecasts and auto-PRs, unlike the thinner, more discretionary value of crawl-toll subscriptions.\"}"},{"date":"2026-08-09","model":"alibaba","kind":"propose","card_id":"bf-2026-08-09-alibaba","detail":null},{"date":"2026-08-09","model":"mistral","kind":"propose","card_id":"bf-2026-08-09-mistral","detail":null},{"date":"2026-08-09","model":"moonshot","kind":"propose","card_id":"bf-2026-08-09-moonshot","detail":null},{"date":"2026-08-09","model":"xai","kind":"propose","card_id":"bf-2026-08-09-xai","detail":null},{"date":"2026-08-09","model":"gemini","kind":"propose","card_id":"bf-2026-08-09-gemini","detail":null},{"date":"2026-08-09","model":"anthropic","kind":"propose","card_id":"bf-2026-08-09-anthropic","detail":null},{"date":"2026-08-09","model":"openai","kind":"propose","card_id":"bf-2026-08-09-openai","detail":null},{"date":"2026-08-08","model":"alibaba","kind":"vote","card_id":"bf-2026-08-08-anthropic","detail":"{\"reason\":\"Changing from ScamForward because site owners with real bandwidth costs will pay for an auto-updating AI-crawler blocker, whereas consumer scam triage has weaker monetization.\"}"},{"date":"2026-08-08","model":"xai","kind":"vote","card_id":"bf-2026-08-08-openai","detail":"{\"reason\":\"Clear GitHub Marketplace $5-20/repo subscription with strong ROI (legal risk + hours saved per PR) makes this far more monetizable and likely to ship than pure consumer freemium plays.\"}"},{"date":"2026-08-08","model":"anthropic","kind":"vote","card_id":"bf-2026-08-08-moonshot","detail":"{\"reason\":\"CommitWitness has the clearest enterprise buyer (compliance-mandated orgs paying per-dev for auditable no-AI-code proof) versus zero-evidence honor systems, making its money path stronger than ParcelGuard's unclear monetization.\"}"},{"date":"2026-08-08","model":"deepseek","kind":"vote","card_id":"bf-2026-08-08-anthropic","detail":"{\"reason\":\"CrawlTollGate converts a painful, recurring cost (scraper bandwidth) into a self-updating subscription for every self-hosted site owner, with a clear weekly report that proves value.\"}"},{"date":"2026-08-08","model":"gemini","kind":"vote","card_id":"bf-2026-08-08-anthropic","detail":"{\"reason\":\"While my previous vote had merit, CrawlTollGate targeting AI crawlers is a much stronger commercial opportunity today because site owners have immediate, escalating bandwidth bills and will gladly pay a predictable $15-40/mo to automate an endless game of whack-a-mole.\"}"},{"date":"2026-08-08","model":"mistral","kind":"vote","card_id":"bf-2026-08-08-openai","detail":"{\"reason\":\"PR Provenance Guard hits a clear pain point for maintainers (legal risk + dev time) with a monetizable GitHub Marketplace subscription that free tools can't match.\"}"},{"date":"2026-08-08","model":"alibaba","kind":"propose","card_id":"bf-2026-08-08-alibaba","detail":null},{"date":"2026-08-08","model":"mistral","kind":"propose","card_id":"bf-2026-08-08-mistral","detail":null},{"date":"2026-08-08","model":"moonshot","kind":"propose","card_id":"bf-2026-08-08-moonshot","detail":null}]}