WALDrill

Who it's for

Solo developers and indie SaaS operators running SQLite/PocketBase/Turso databases who already back up with Litestream, manual sqlite3 .backup, or object-storage snapshots; today they cope with ad-hoc sqlite3 CLI restores and Litestream restore commands.

The problem

Time: monthly manual restore tests take 1-2 hours and get skipped; legal: after customer-data loss they lack proof of restorability for incident response or breach diligence.

How to build it

Hosted dashboard plus read-only S3/GCS/Litestream snapshot connector and Slack/email webhook; no live-database agent and no write access to production DB.

How it makes money

Solo SaaS owners pay $29/month per database for scheduled restore drills and certificates; they pay to avoid hours of manual testing and to show diligence after an incident; free sqlite3/Litestream commands do not schedule, isolate, or certify restores.

Why it doesn't exist yet

Incumbents skip it because backup vendors focus on enterprise Postgres/MySQL and treat SQLite as a free embedded niche; indie gap is selling a narrow proof-of-restore certificate layer on top of existing backups without building storage.

First users

Developers in the HN Tailscale SQLite WAL-corruption thread and Litestream/PocketBase GitHub/Discord discussions who are already asking how to verify SQLite backups.

Build size

1 person x 8 weeks; includes snapshot fetch, disposable restore runner, integrity/smoke checks, certificate, Slack/email alerts, Stripe; excludes live writes, non-SQLite engines, data recovery, and on-prem support.

Biggest risk

Litestream, Turso, Fly.io, or SQLite itself ships a native scheduled restore-verification command, making a separate drill service unnecessary.

Conditions for a hit (all 3 required)

• Accepts a read-only S3/GCS bucket path or public URL to a SQLite/Litestream snapshot and, for databases up to 5 GB, completes a restore in a disposable VM within 15 minutes.
• Runs PRAGMA integrity_check plus up to 10 user-supplied SQL smoke queries and outputs a JSON/PDF certificate containing SHA-256 checksum, SQLite version, restore duration, pass/fail, and a unique drill ID.
• Can run on a daily schedule, posts the certificate to Slack or email, and lets the user retrieve each certificate by drill ID for at least 30 days.

How it's judged (in 6 months)

A public GitHub repo implementing this shape reaches 1,000 stars, or a hosted implementation reaches Product Hunt daily top 5.(judgment date 2027-02-13)

AI self-confidence 40/100 — self-reported likelihood of meeting the criterion, not a business success rate