Brijraj Rana

Launchwatch

Vibe coded Mac app, 2026

Keeps checking your live sites from the menu bar.

View on GitHub Download

Launchwatch panel: acme-rockets.com is down, with a timeline of recent events and the likely cause of each, a strip of the last seven days, uptime, certificate and domain dates and a chart of response times, above five other sites that are fineLaunchwatch panel: acme-rockets.com is down, with a timeline of recent events and the likely cause of each, a strip of the last seven days, uptime, certificate and domain dates and a chart of response times, above five other sites that are fine
One site down, opened up

Details

Role
Design and direction, vibe coded
Built with
Swift, SwiftUI, AppKit, the Launchcheck engine
Platform
macOS 14+, Apple Silicon and Intel
Year
2026
Source
Open, MIT, v0.3.0

What it does

Launchcheck is run once, before a site goes live. Launchwatch is what happens after: it sits in the menu bar, checks every site every few minutes, and speaks up when one goes down, slows down, or changes in a way search engines notice. And it says why.

Design notes

  1. One line says how things are

    All 6 sites are fine, or the name of the one that is not. A site that is down is always the headline, whatever else is going on.

  2. Says why

    An alert comes with its likely cause in a sentence: the certificate, the host, an error page, or the part of the request that got slower. When it cannot tell, it does not guess.

  3. Stands on its own

    What the audit found can be read inside the panel and copied as a list. Launchcheck adds the full report, and is never required.

  4. Quiet until it matters

    The menu bar icon carries no color and no number until something needs attention. Notifications fire when something changes, never to say all is well.

  5. No false alarms

    A site is called down only after a second failed check. Slow means slow for that site, measured against its own usual speed. An offline Mac is not six broken sites.

  6. The quiet failures

    Every six hours the Launchcheck engine reads the site again: a noindex that appeared, a robots.txt that blocks everything, a title that changed.

  7. A day in a line, a week in a strip

    Each row carries the last 24 hours of response times. Opened up, 28 cells cover the last seven days, red where the site was down.

  8. Monday morning

    One sentence about the week: how much everything was up, what went out, which certificate is running short.

  9. Color means something

    Red, amber and green are only ever a state. The rest is the same warm monochrome as Launchcheck.

More screens

Launchwatch with the issues of one site listed inside the panel: pages set to noindex with why it matters and the pages affected, then five more issues, and Copy as MarkdownLaunchwatch with the issues of one site listed inside the panel: pages set to noindex with why it matters and the pages affected, then five more issues, and Copy as Markdown
What the audit found, read in place
Launchwatch panel with one site dimmed and marked as paused until a time, the others greenLaunchwatch panel with one site dimmed and marked as paused until a time, the others green
A site paused while it is being worked on
Launchwatch panel with the weekly summary open: 6 sites, 99.9% up, 1 outage, a certificate expiring in 9 days, 1 score fellLaunchwatch panel with the weekly summary open: 6 sites, 99.9% up, 1 outage, a certificate expiring in 9 days, 1 score fell
The weekly summary, unfolded
Launchwatch panel with six sites, all green, each with a response-time line and a scoreLaunchwatch panel with six sites, all green, each with a response-time line and a score
The usual state: nothing to do
Launchwatch settings: how often to check and audit, notifications, the weekly summary, domain expiry, a webhook address and open at loginLaunchwatch settings: how often to check and audit, notifications, the weekly summary, domain expiry, a webhook address and open at login
The settings, in the panel itself

Source

Launchwatch is open source under the MIT licence. The code is on GitHub.