How I verify
Built. Tested. Re-verified.
I ship every Base here myself. The point of this site is trust — so I'd rather list fewer things, slower, than dump AI-generated repos online and hope. Here's what makes the cut, what doesn't, and how often I re-check.
We accept
- Original implementations
- SaaS-inspired workflows (alternatives, not clones)
- Source-code products
- Local-first tools
- Mac apps, websites, internal tools, mobile prototypes
- Privacy-friendly alternatives
- Remixable small apps with a clear niche
We reject
- Copied source code, UI, branding, or assets
- Generic todo / CRM / chatbot listings with no niche angle
- Broken demos
- Listings making misleading comparison claims
- Hidden telemetry, adware, malware
- Unsupported "AI slop"
- Products that violate third-party service terms
My process
Five gates before a Base goes live.
- 01
Build
I ship the working version end-to-end. No "AI drafted, untested" hand-offs.
- 02
Live for me
It runs in my own setup for at least a couple of weeks. Bugs surface; I fix them.
- 03
Strip to scope
I cut anything that wasn't solid. The listing's does / does-not panels reflect what survived.
- 04
Publish
Badges issued (Live Preview, Source Build, Remix Ready). "Last verified" date stamped.
- 05
Re-verify
I re-check periodically and after upstream changes. Stale Bases get hidden until re-verified.
Anti-clone
We don't sell clones. We sell ownable alternatives.
Existing SaaS products are demand signals — not products to copy.
- REJECTED "Calendly clone"
- ACCEPTED "Solo clinic booking Base with intake forms, deposits, private notes, and CSV export"
- REJECTED "Notion clone"
- ACCEPTED "Private team wiki Base with markdown pages, search, and role-based access"
Honesty
Every listing shows free tools, paid SaaS alternatives, and a "should you just prompt this yourself?" section.
Limitations
Mandatory. If the limitations field is empty, the Base doesn’t list.
Last verified
A timestamp every buyer can see. Stale verifications get hidden until re-checked.