Fingerprint-based request-flood blocking for small SaaS sites without a security team
Problem
Small sites are constantly hit by loops of form submissions and mass signups, and captchas no longer work, yet founders have no budget for a security team or an enterprise WAF.
Solution
A lightweight reverse-proxy or middleware service that scores requests by IP, behavioral fingerprint, submission cadence, and signup patterns, then applies JS challenges, rate limits, or soft bans to suspicious traffic. A simple dashboard shows every blocked request and false positives, with one-click rule tuning.
Resume Claude Code sessions seamlessly across multiple Macs and your iPhone
Problem
Developers juggle several Macs and a phone, yet Claude sessions are tied to a local machine, so moving work between devices means manually shuttling project folders through cloud drives. Multiple accounts and instances make it worse, and one developer even weekend-built a TUI just to dig through thousands of sessions and forks.
Solution
A lightweight desktop sync daemon that packages session directories, project context, and account profiles into portable workspaces synced through the user's own cloud drive or a peer-to-peer channel. It offers a browser for sessions and forks, letting you pick which session to resume when you switch devices.
A runbook plus appeal-letter generator for teams whose GitHub or cloud account gets locked
Problem
When a developer account is wrongly suspended, the platform offers only a support ticket that can go unanswered for months, and even a paid enterprise org loses access. Affected teams scramble through old emails and invoices to assemble an appeal, because nobody planned for a locked account beforehand.
Solution
A local-first tool that first inventories critical accounts (code hosting, cloud, payments, domains) with each one's recovery path and fallback contact, producing an offline runbook. If a lockout happens, it walks the user through a structured appeal form, gathers subscription receipts and business-impact evidence, and outputs a ready-to-paste appeal letter plus a recovery timeline.
Help small shops handle AI agents calling to book appointments
Problem
AI assistants now call salons, dentists and dry cleaners to book on behalf of customers, and about a third of staff stay on the line after realizing it's an AI. The person answering has no rules on what to say, what to refuse, or how to tell a real customer from a robocall.
Solution
A playbook for shop owners and front desks: an on-screen card listing what can be answered (hours, prices, availability) and what must not be promised (holds, discounts, payment info), plus a log-and-callback confirmation flow.
Pre-launch health checks and handover docs for internal tools at factories
Problem
Indie developers build internal tools that replace Excel for safety-equipment tracking and maintenance logs, but clients may self-build with Copilot-like tools and nobody worries about long-term maintenance. Developers need a way to prove build is easy but upkeep is hard, and to make handover auditable.
Solution
A handover toolkit that turns a small internal tool's fields, data sources, permissions, backups and migration plan into a client-friendly launch checklist and maintenance handbook. Periodic health checks (backups, permission drift, key field changes) become the differentiator.
Turn architecture decisions and past findings into agent-retrievable context
Problem
When coding with AI, the agent doesn't know why things were designed this way or which approaches already failed, so it keeps proposing rejected ideas. These decisions are scattered across PRs, issues and personal notes, unusable by the agent.
Solution
A lightweight decision-record library: structured templates for context, options, conclusion and affected scope, plus an MCP/CLI interface so coding agents can retrieve relevant decisions before editing. Commits can be linked to affected decision entries.
A zero-ops self-hosted comment system for static blogs
Problem
Adding comments to a blog usually means running a container/VPS/database or handing reader comment data and privacy to a third-party platform. The builder himself said existing options didn't work the way he wanted, so he had to build his own.
Solution
An open-source comment system packaged as one Cloudflare Worker with D1 for storage and KV for cache, deployed into the user's own account within free tiers. Includes built-in anti-spam, privacy-minimal commenter fields, Markdown, and email notifications.
A tiny utility that switches audio input/output the moment you plug in USB-C earbuds
Problem
Plugging in USB-C earbuds often doesn't switch audio output, and noise-cancelling headsets still route to speakers during calls, forcing users to dig through system settings every day. Options are scattered and behave differently per device.
Solution
A menu-bar utility that watches audio device plug/unplug events, remembers each headset's preferred input/output combo, and switches with one click or hotkey. Adds per-app overrides (e.g. meeting apps) and simple auto-rules like switch-on-plug.
Force a quick scan of key risk items before you approve an AI coding agent's plan
Problem
With Claude Code, Cursor, Codex and similar tools, users often skip straight to code or skim before approving agent-generated plans. A recent question asked when was the last time you read the whole plan before approving a substantial change, showing awareness of the risk but a lack of lightweight checking tools.
Solution
A lightweight tool where you paste the agent's plan and it highlights risk points against a checklist: files touched, database changes, permissions and secrets, rollback plan, test plan, unspecified assumptions. It outputs a tickable pre-read checklist so users can quickly go through it before approval.
Follow only the part of a shared doc or list you care about and get notified with highlighted diffs
Problem
Shared docs or lists are long, and every update forces a full reread to spot changes. When a partner updates a shopping list, a bank updates terms, or a team updates a shared list, users only want to know what changed in the part they care about, but must search manually.
Solution
Let users subscribe to any fragment of a shared doc or list. The system periodically fetches or syncs via API, detects changes, and only pushes a highlighted diff notification for that fragment, covering shopping lists, terms pages, shared spreadsheets and more.
Measure real token consumption and stability of AI coding plans over an 8–10 hour dev day
Problem
Users complain that Claude Code + Opus runs out of tokens, MiniMax Pro works daily but not on MAX, Kimi is expensive, DeepSeek is strong but its consumption is unknown. Everyone relies on scattered free credits or self-paid plans, with no unified benchmark for which combo lasts a full dev day.
Solution
Provide a reproducible benchmark harness that runs a set of typical dev tasks (read code, fix bugs, write tests, refactor) to measure token consumption, completion time, failure rate, and interruptions across models and plans, outputting comparable reports.
Catch App Store Connect rejection-causing Info.plist mistakes before you upload
Problem
Developers often get rejected because of small Info.plist issues: letters in CFBundleVersion, TODO permission strings, unexpanded $(VARIABLE) in the built app, missing LSApplicationCategoryType for Mac apps. These only surface after upload, wasting a build and waiting time.
Solution
Offer a zero-dependency Node CLI and GitHub Action that parses XML and binary plists, distinguishes the project plist from the built .app plist, matches Apple docs and ITMS error rules, and gives per-issue hints with official documentation links.
A less app-switching way to fill 2FA codes for heavy iPhone users
Problem
After a code is generated, users still have to switch apps, find the account, copy, and switch back. AutoFill fails in many apps, and third-party keyboards can't detect the host app, so the last step often gets stuck.
Solution
Build an iOS third-party keyboard plus a main app where all 2FA entries are listed and filled with one tap. The app supports imports from Google Authenticator, Aegis, Bitwarden and others, with local AES encryption and optional iCloud sync.
See where each agent's tokens actually go, call by call
Problem
After switching to a heavily plugin-based agent, one user found long tasks cost more than double their previous setup — a $350 day with no visibility into which call, sub-agent, or tool round burned the money. Official dashboards show only a total.
Solution
A local proxy layer that logs each request's prompt, tool calls, sub-agent forks, and token counts, then aggregates them into a task-and-tool flame view of time and spend. It flags repeated calls and bloated context and suggests cuts.
Turn a shop owner's "how do I do this again?" into a visual manual
Problem
Small e-commerce shops get flooded with repeat how-to questions right after hiring their first employee. Trainual costs $249/mo plus a setup fee and Scribe's free tier is too thin with per-seat pricing, so owners write a chaotic late-night Google Doc nobody can follow.
Solution
Record a screen walkthrough or narrate the steps, and the tool turns it into manual cards with screenshots and bullet points. Search, share read-only links by role, and let staff check off completed steps. Repeated questions get folded into the manual in one click.
Long podcasts as a searchable web page with highlights and notes
Problem
People who listen at their desk are stuck juggling a phone, and on long episodes finding one sentence or the crowd-favorite moment means scrubbing blindly. There is no handy place to save a quote, and the lively parts of the comment section are invisible.
Solution
A browser podcast player: scan to log in and sync subscriptions and progress, overlay comment heat on the timeline and jump straight to those moments, highlight a synced transcript word by word with search and click-to-play, and save any sentence as a note exportable to Markdown.
Default-deny network rules for home IoT, opened by device model
Problem
Dishwashers, bulbs, and TVs all have a MAC address, but nobody knows where they phone home. Blocking traffic risks breaking the device, and users are left asking forums for something like uBlock Origin for IoT.
Solution
A rules pack plus small admin UI importable into OpenWrt/home routers: new devices are blocked by default, and users pick a branded "make + model" profile from a crowdsourced list to allow only the domains it needs. The UI also shows which domains each device actually contacts.
Zero-config auto-deploy for PHP sites that only have FTP
Problem
Plenty of PHP sites and freelance projects still live on shared hosting with no SSH and no Git. Every change means manually uploading files over FTP, which leads to missed files, wrong folders, and overwritten production. Mainstream CI/CD never connects to these environments.
Solution
A deploy tool that works over FTP/SFTP or hosting panel APIs: connect a repo, build and package it, upload only changed files by hash, and auto-rollback on failure. Includes deploy history, diff preview, and a paste-able hook command.
Centralizes AI-agent code changes from multiple devices into one review queue
Problem
Many developers run agents like Claude Code and Codex across multiple machines at home and work, with tasks scattered and code changes spread everywhere, making it hard to review exactly which files AI changed. Some have built multi-device agent orchestration, but review still requires manually switching devices.
Solution
Build a lightweight service that collects code change summaries from agents on multiple devices and pushes them to a unified review panel. Developers can see which files AI modified per device, whether tests passed, and any suspicious changes, and one-click mark items for manual review.
Helps small business owners map upcoming bills and receivables onto one timeline
Problem
Small business owners show a healthy profit on paper but often run into cash flow emergencies: materials due Friday, subcontractor payment next Monday, while customer invoices won't clear for two or three weeks. Existing accounting tools only record what happened and don't help users simulate cash gaps for the coming weeks.
Solution
Build a lightweight cash flow scheduling tool where users enter receivables and payables, and it auto-generates an 8-week cash curve, highlighting weeks likely to go negative. Supports filtering by business line and alerts which delayed payment will widen the gap.