The Problem
Sick of gluing together half-baked web scrapers, brittle bots, and ugly dashboards just to automate some browser tasks? Most browser automation tools are either too simple, too clunky, or require rewriting everything for each new use case. Hyperbrowser tries to make that less painful — actual working web apps that scrape, automate, and spit out useful data, not just demo scripts.
What This Does
hyperbrowser-app-examples is a grab bag of full-stack apps built around the Hyperbrowser API. Each one is in its own directory: want to track competitor site changes? Look in competitor-tracker/ (see app/api/crawl/route.ts and lib/diff-html.ts). Need to generate startup ideas from Reddit? Check Idea-generator-reddit/app/components/index.ts and the API logic in app/api/generate/route.ts. All of these are real Next.js projects, with TypeScript everywhere, UI in React, and Tailwind for styling. You get the full setup: config files (next.config.ts, tailwind.config.js), actual source code, and even some snapshot HTML data in competitor-tracker/data/snapshots/.
It's not just front-end fluff. Each app wires up Hyperbrowser for automation, handles API keys via environment variables, and manages workflow logic in files like lib/hyper.ts or lib/hb.ts. The structure is clear, and you can actually run these locally without rewriting everything.
Real-World Use
Say you need to monitor a competitor’s pricing page. You’d clone the repo, go to competitor-tracker/, set your Hyperbrowser API key in the env file, and run the app. The workflow uses app/api/crawl/route.ts to fetch pages, saves snapshots to data/snapshots/, runs diffs with lib/diff-html.ts, and notifies you of changes. No need to cobble together ten different npm packages — just call the API, and let the UI show you the diff.
The Bottom Line
If you want production-ready web scraping apps that don’t look like 2005 PHP junk, this repo is solid. It’s overkill for hobby scripts — but great for anyone building real dashboards or automation tools. The code is readable, the UIs don’t suck, and you don’t have to reinvent the wheel every time. If your pain is browser automation, grab your API key and get started.