Directory of AI-free alternatives to FOSS tools

What to build

A curated, crowdsourced directory website listing FOSS projects that have added AI/LLM features (chat assistants, AI-generated docs, AI code-review bots) alongside human-maintained, AI-free alternatives, with category tags, a public submission form, and a simple 'no AI in the codebase or workflow' vetting badge for listed alternatives.

A vocal segment of FOSS users and maintainers push back whenever popular projects add AI/LLM features, but no directory currently tracks AI-free alternatives for them to switch to — a narrow but clearly signaled niche a solo builder could own early.

Demand

Open-source purists, privacy-conscious developers, and maintainers who reject AI-assisted contributions want this now, visible in recurring backlash threads whenever a popular FOSS project ships AI chatbots, AI-generated changelogs, or AI review bots.

• Hacker News (open-slopware, codeberg.org/ethical-foss/open-slopware)Discussion

  34 points and 17 comments on Hacker News for a proposal naming the 'slopware' trend and suggesting a directory of AI-free FOSS alternatives as the response — high engagement for a niche naming/framing post.

• GitHub issue trackersReport

  Recurring issues and discussion threads on GitHub repos objecting to maintainers merging AI-assisted contributions or enabling AI-powered features by default, citing licensing, provenance, or code-quality concerns.

• Hacker News / Lobsters / Reddit r/programmingDiscussion

  Recurring comment backlash and requests for non-AI forks whenever a popular FOSS project announces AI chatbot integration, AI-generated changelogs, or AI code-review bots.

Stack

• Next.js
• Supabase (Postgres + auth)
• Vercel
• Typesense or Algolia for tag/category search
• GitHub API (repo metadata, commit/contributor activity for badge checks)
• Tally or a custom form for submissions

Solo + AI difficulty

The directory shell itself (listings, tags, submission form, static badge) is a straightforward week-long build for one person with AI coding help — the hard, ongoing part is verifying and enforcing the 'no AI' badge, since AI-assisted commits are difficult to detect and false claims would quickly erode trust in the whole site. Time-to-MVP is roughly 1-2 weeks; sustaining it afterward is a curation and moderation job, not a coding one.

Entry threshold

Very low barrier: a static directory or lightweight CMS/Next.js site with a submission form and tagging system, buildable solo in days; monetization options (sponsorships, donations, 'verified human' badge) require no capital or licences.

Window

6-12 months

Where to find first users

• Hacker News launch post
• Lobsters
• r/opensource and r/programming
• Fosstodon / Mastodon FOSS community
• Product Hunt launch

Competitors

• AlternativeTo

Counter-signals & risks

• The anti-AI developer niche may be too small and fragmented to sustain ongoing traffic or a viable business model, since most developers are indifferent to or actively welcome AI features for productivity gains.

• Verifying and enforcing a 'no AI in codebase or workflow' badge is difficult in practice because AI-assisted commits are hard to detect, risking false claims and credibility loss for the directory.

• Many high-quality maintainers are adopting AI tooling deliberately to manage maintenance burden, so the fully human-maintained alternatives listed may be lower-resourced, slower-moving, or eventually adopt AI themselves, undermining the directory's premise over time.