Twelve repositories for finding out before your users do

What it is

A self-hosted uptime monitor. You give it a URL, a port, a container or a certificate to watch, it checks on a schedule you choose, and it shows you a history of response times plus an alert when something stops answering. It also publishes a status page you can point people at.

Why it matters

Edition 5 gave you beszel and was explicit that it measures resources, not availability — it will tell you the box is at 92% memory, never that your landing page is returning a 502. That gap is the one that costs money. You publish a video, the traffic arrives over the following three days, and if the site is down for four hours in the middle of that window you will not know, because you were filming. Every campaign this radar has proposed is a spike of attention pointed at one Hetzner box, and attention that lands on an error page does not come back for a second try. There is a second use worth as much: watching your TLS certificates and your PostgreSQL port, which is how you find out about the expiring certificate a week early instead of on the morning it breaks.

What it is

A self-hosted error tracker that speaks Sentry's protocol: you drop the ordinary Sentry SDK into your React app and your FastAPI service, point its DSN at your own server, and every unhandled exception arrives with a stack trace, the browser, the URL and how many times it has happened. It is deliberately small — one process against SQLite or Postgres, no queue, no worker fleet.

Why it matters

• PolyForm Shield 1.0.0 is not open source. You may run it for your own business freely; you may not use it to build a competing error-tracking product. That is fine for your use, and irrelevant to Grasppy — but it belongs in the same notebook as n8n's fair-code and Remotion's licence, because it is another dependency you cannot fork if the company changes its mind
• Two thousand stars and a small team. The mitigation is unusually good here: it speaks the Sentry protocol, so if it stalls you change one DSN and point at something else — but check that before you rely on it
• An error tracker with no triage discipline becomes a firehose you stop opening. Mute the noisy ones in week one or it will go the way of every unread dashboard

What it is

A command-line site crawler and auditor. It walks every page of a site and reports back on broken links, redirects, response times, page sizes, headings, titles and meta descriptions, images, accessibility basics and security headers — as a single self-contained HTML report, or as Markdown, JSON or a spreadsheet. It also generates sitemaps and can export a working offline copy of a site.

Why it matters

Edition 2 gave you Unlighthouse, which is excellent at one question — how does each page score in Lighthouse — and silent about the boring failures that lose you more traffic than a performance score does. Dead links are the clearest case: you will rename a docs page, you will change a video URL, and six months later Google is still indexing a page that links into nothing. This finds those in one pass, along with the missing meta descriptions and the untitled pages that stop the Starlight docs from ranking properly. Two details make it fit you specifically: it is one binary with no Node project and no install ceremony, and its report is a file you can hand to Claude Code and say "work through this." At 764 stars it is genuinely under the radar, and unlike the last two SEO auditors this radar considered, its releases are dated and recent.

What it is

A tiny publish–subscribe notification service. Any script sends an HTTP POST to a topic URL, and the message appears as a push notification on your phone or in a browser tab. There is a free public server and a self-hosted single Go binary; the mobile apps are on both stores.

Why it matters

Count the things in this ledger that end with "and then it tells you": Uptime Kuma when the site is down, Bugsink when a new error appears, RSSHub and n8n when somebody on Reddit asks the question Grasppy answers, Procrastinate when a three-hour backtest sweep finishes. Every one of them currently ends in an email you will read tomorrow or a dashboard you will not open. This is the two-minute fix that turns all of them into a phone buzz — and for the Reddit case the difference between arriving first and arriving on page four is measured in hours. It is the wildcard because it is not a marketing tool in itself; it is the thing that makes the marketing tools you already have actually reach you.

What it is

A small Python tool that fetches the comments from any YouTube video — text, author, timestamp, like count, and replies — as JSON lines, sorted by popularity or recency. No API key, no quota, no OAuth consent screen; it is a command you run and a file you get.

Why it matters

This is the sharpest research tool this radar has found, and it is nearly free. Edition 6 gave you yt-dlp for what competitors published and Edition 5 gave you youtube-transcript-api for what they said. Comments are the other side of that conversation, and they are the only one of the three written by your buyers. Pull the comments from the twenty most-viewed videos about summarising long chats, mapping documents and backtesting forex strategies, and you will find the same six complaints repeated in different words — "he goes too fast", "this doesn't work on Mac", "what about a 500-page PDF", "how do I do this in Russian". Each of those is a video title, a docs page, and a line of landing-page copy, and each one is evidence rather than instinct. It also works on your own channel: the questions under your videos are the fastest signal you have about what the product fails to explain — and they are also the thumbnail and title feedback loop, because a comment saying "clicked for X, got Y" is telling you your title lied. Note the trap this project illustrates: its GitHub releases page stops at August 2025 and looks abandoned, while PyPI shows a release five weeks ago. Check PyPI for this one.

What it is

The long-established Python client for Reddit's official API. It handles authentication, rate limiting and pagination, and gives you subreddits, submissions, comments and search results as ordinary Python objects — including a stream mode that yields new posts as they appear.

Why it matters

Edition 4 gave you RSSHub and made the right argument: the gap in your stack is listening, not publishing. RSSHub gets you a feed of new items. PRAW gets you the archive and the search — which is the more valuable half at this stage, because you do not yet need to be notified of the next question, you need to read the last two years of them. Search r/ChatGPT, r/productivity, r/ObsidianMD, r/Forex and r/algotrading for the phrases people actually use about drowning in a long thread or validating a scalping idea, pull a few thousand posts and their top comments, and you have the vocabulary problem solved: the words in your headline stop being your words and become theirs. There is a second, slower payoff. Answering one of those questions honestly and usefully, with a link only where it genuinely helps, is the cheapest customer acquisition that exists for a product like Grasppy — and it works precisely because it is not marketing. Be careful here: Reddit is fast to punish self-promotion, and the correct posture is to be a person who is useful and occasionally mentions their tool.

What it is

A command-line tool for talking to language models. You pipe text in, get text out, and every exchange is logged to a local SQLite file you can search afterwards. It speaks to the major hosted providers and, through plugins, to local models; it supports saved prompt templates, fragments, schemas for structured output, and embeddings.

Why it matters

You already have Claude Code, so the case for this is narrow and specific: bulk. Claude Code is a conversation; this is a pipe. When entry 05 hands you nine thousand comments across forty videos, the useful shape is cat comments.jsonl | llm -s "extract every distinct complaint about the tool being explained" run over each file in a loop, not forty chat sessions. The same applies to the Edition 6 corpora — every competitor article trafilatura pulled down, every transcript, every Reddit thread. Two features earn their place beyond that. Saved templates mean the prompt you spent an hour refining — "summarise this transcript as a video outline in English and Russian" — becomes a named command you reuse for a year. And the SQLite log means the work is queryable: three months from now you can ask which titles you generated in July, and get an answer. It is also a very fast way to prototype a Grasppy prompt before writing any FastAPI code, and it sits naturally behind LiteLLM from Edition 5 when you want the spend capped.

What it is

A tiny custom element that replaces the standard YouTube iframe. Instead of loading YouTube's player and its several hundred kilobytes of JavaScript on page load, it renders the thumbnail with a play button; the real player is only fetched when a visitor actually clicks. The measured difference is roughly an order of magnitude in initial weight.

Why it matters

Your marketing depends on video, so your landing page and your blog posts will have embeds on them — and a standard embed is usually the single largest cost on the page, worse than every image combined. Edition 6 put imgproxy in front of you for image weight and made the Core Web Vitals argument; this is the same argument for the heavier offender, and it is a smaller job. Swap <iframe> for <lite-youtube> and the page that ranks for "how do I summarise a long chat" stops being slow because of the demo video sitting on it. There is a privacy angle worth a sentence too: no YouTube script runs until the visitor chooses to play, which is a defensible position for a product whose pitch is that your text stays on your server.

What it is

A static search library. After your site is built, it indexes the generated HTML and writes a set of small index fragments; the browser downloads only the fragments a given search needs, so a large site costs a visitor a few tens of kilobytes rather than a whole index. It ships a ready-made search UI and supports filters and multilingual indexes, including Russian.

Why it matters

Two reasons, and the second is the one that matters more than it looks. The obvious one: as the Astro site and the Starlight docs grow into the dozens of pages this radar keeps telling you to write, a visitor who cannot find the page you wrote for them is the same as a page you never wrote — and Starlight already bundles this, so extending the same search across your blog and marketing pages is consistency rather than a new dependency. The less obvious one: what people search for on your own site is the highest-intent keyword data you will ever have, and it is free. Someone typing "russian subtitles" or "500 page pdf" into your docs search is telling you, in their own words, both what to write next and what your product is expected to do. Wire the query into Umami as a custom event and you have a list nobody else in your market has — which is worth more than the search feature itself.

What it is

Microsoft's open framework for finding and removing personal data in text: names, emails, phone numbers, card numbers, national identifiers and more, through a mix of pattern matching, checksums, context words and NLP models. It can redact, mask, hash or replace what it finds, and you can add your own recognisers.

Why it matters

Think about who actually has a four-hundred-message thread worth mapping. It is somebody working: a consultant with a client discussion, a manager with a project channel, a researcher with interview notes. Every one of them hesitates at the same moment, and the hesitation is not about your features — it is "what happens to this text?" Grasppy already has the strong answer, because Docling and BERTopic run locally on your own box. Presidio lets you go one step further and say something specific: names, emails and numbers are detected and masked before any text is sent to a model for labelling. That is a sentence on your landing page, a paragraph in your docs, and a genuine feature — and it separates you from every competitor whose pipeline is a thin wrapper around somebody else's API. It is also the honest engineering position: if you are going to send chunks to an LLM to name topics, you should know what is in them. Do not oversell it in your copy — call it a reduction of risk, not a guarantee, because that is what it is.

What it is

A React tree component: virtualised so it stays fast with thousands of nodes, with keyboard navigation, multi-select, inline renaming, drag-and-drop reordering and built-in filtering. Every row is your own React component.

Why it matters

Your traffic is going to arrive from YouTube, and a large share of YouTube traffic is on a phone. A pan-and-zoom node canvas — React Flow with elkjs — is the right thing on a laptop and close to unusable on a five-inch screen, where the nodes are either too small to read or too large to see two at once. So the honest position is that Grasppy needs two views of the same tree, and the second one is a list. This is the component for it: virtualised, so a 500-message thread does not stall the browser; searchable, which on mobile is faster than any amount of zooming; and keyboard-navigable, which is also the accessible path and the one a screen reader can follow. There is a strategic point underneath the practical one. A map that only works on a desktop makes every video you publish half as effective, because the viewer watching on their phone cannot try the thing you just demonstrated. Fixing that is worth more than most features.

What it is

A hyperparameter optimisation framework. You write a function that scores one configuration; Optuna chooses which configurations to try, using the results so far to sample the promising regions, and prunes runs that are clearly going nowhere before they finish. Every trial is stored in a database, so a study can be paused, resumed and inspected.

Why it matters

ScalpingMate's real constraint is how many hypotheses you can kill per day, and grid search is the slowest possible way to kill them: entry threshold × stop × target × session, and you are running thousands of backtests, most of them on parameter values that were obviously bad after the first six months of data. Optuna's sampler concentrates on the regions that are working, and its pruning stops a hopeless trial part-way — together that is usually an order of magnitude fewer full backtests for the same answer, on a CPU box that has other jobs to do. It also fits the tools already in the ledger rather than replacing them: it wraps skforecast's rolling-origin backtest as the objective function, so the thing being optimised is walk-forward performance rather than a curve fitted to the whole history. One warning, and it is the important part: a smarter search finds an overfitted result faster than a dumb one. Everything Edition 6 said about arch's reality check applies double here — the more configurations you try, the more certain it is that the best of them is luck. Optuna finds candidates; it never validates them.