DevHunt — Open-Source Product Hunt Alternative for Dev Tools

TL;DR

TL;DR: DevHunt is an open-source, community-driven launch platform for dev tools — submissions are GitHub pull requests and voting requires a GitHub login, replacing the upvote-farming model of traditional directories.

Source and Accuracy Notes

⚠️ This section is MANDATORY. All links must be verified from actual source, not guessed.

• Project page: devhunt.org
• Source repository: github.com/MarsX-dev/devhunt
• License: MIT (verified via GitHub API license.spdx_id)
• HN launch thread: news.ycombinator.com/item?id=36420069

What Is DevHunt?

DevHunt is a launch platform for developer tools and open-source projects. Unlike traditional directories where anyone can create a listing with no friction, DevHunt requires submissions via GitHub pull request — the same mechanism developers already use for code collaboration.

The core idea: skin in the game through GitHub. To submit a tool you open a PR; to upvote you need a GitHub account. This gates voting to actual developer accounts rather than anonymous visitors, making the ranking more signal than noise.

The platform is built on:

• Next.js — frontend framework
• Supabase — database and auth (GitHub OAuth)
• Vercel — hosting

It is MIT-licensed and open to contributions via the standard GitHub PR workflow.

How Submissions Work

A valid submission is a PR to the DevHunt GitHub repo that adds a tool entry in the structured format the site expects. This means:

• No account creation on DevHunt itself — you need a GitHub account only
• Submissions are reviewed by maintainers through the normal PR review process
• Listings persist as long as the repo is active

# Clone and run locally
git clone https://github.com/MarsX-dev/devhunt
cd devhunt
npm install
npm run dev

Key Features

• GitHub PR-based submissions — no separate DevHunt account needed; open a PR to add a tool
• GitHub login voting — upvotes require GitHub authentication, reducing vote manipulation
• Open-source core — the entire platform is MIT-licensed and on GitHub
• Supabase-backed — self-hostable with your own Supabase project
• Community-driven curation — maintainers review PRs for quality and relevance

Setup

Prerequisites

• Node.js 18+ and npm/yarn/pnpm
• A Supabase project (free tier works)
• GitHub account for OAuth

Step 1: Clone and Install

git clone https://github.com/MarsX-dev/devhunt
cd devhunt
npm install

Step 2: Configure Supabase

1. Create a Supabase project at supabase.com/dashboard/projects
2. Restore the provided database dump:

psql -h db.<your-ref-id>.supabase.co -U postgres -d postgres < supabase/dump.sql

3. Copy .env.local.example to .env.local and fill in your Supabase credentials:

NEXT_PUBLIC_SUPABASE_URL=https://your-project.supabase.co
NEXT_PUBLIC_SUPABASE_ANON_KEY=your-anon-key
SUPABASE_SERVICE_ROLE_KEY=your-service-role-key

Step 3: Set Up GitHub OAuth

Follow the Supabase GitHub OAuth guide. Configure the OAuth provider in your Supabase dashboard under Authentication → Providers → GitHub.

Step 4: Run

npm run dev

Open http://localhost:3000. You can now submit tools via PR or vote on existing listings.

Deeper Analysis

Why DevHunt vs. Alternatives?

Product Hunt dominates tool launches but is closed-source, generalist, and plagued by vote-farming from shared communities. DevHunt’s GitHub-gated model is architecturally more resistant to manipulation — you cannot easily create 50 fake GitHub accounts to upvote your tool.

The PR submission model also means listings come with a code artifact (the submission itself), making it harder to launch vaporware. If the PR looks incomplete or the linked repo is empty, maintainers can close it.

For open-source projects specifically, being listed on a platform whose submission mechanism mirrors how open-source collaboration already works is a natural fit.

Limitations

• No native mobile app — the site is responsive but not a first-class app experience
• Supabase lock-in — while self-hostable, the schema is tied to Supabase; porting to a different backend requires schema work
• Small launch volume — as a newer platform, traffic is still growing; a launch on DevHunt alone won’t drive Product Hunt-level visitors
• PR review latency — submissions aren’t instant; a maintainer must review and merge the PR before the tool appears live

Security Notes

• OAuth tokens — GitHub OAuth tokens are handled by Supabase; ensure SUPABASE_SERVICE_ROLE_KEY is never exposed client-side
• PR-gated submissions — the platform trusts the GitHub account that opens the PR, but listing quality is enforced post-submission by maintainers
• Self-hosting considerations — if self-hosting, rotate your Supabase keys regularly and follow Supabase’s hosting security guidelines

FAQ

Q: Is DevHunt free to use? A: Yes, both to browse and to list tools. The platform is MIT-licensed open source. Self-hosting costs are limited to your Supabase compute and hosting (Vercel or self-hosted Next.js).

Q: Can I submit a closed-source or commercial tool? A: DevHunt is focused on developer tools and open-source projects. Commercial tools are allowed if they are developer-focused, but the PR-based submission means the source (or at least the listing PR) must be publicly visible.

Q: How does voting work? A: You must be logged in with GitHub to upvote a tool. Each GitHub account gets one upvote per tool. This is designed to prevent vote inflation from anonymous or multiple accounts.

Q: Is this a Product Hunt killer? A: No — DevHunt is smaller, more niche (developer tools only), and the GitHub PR model means lower submission volume. It is a complement, not a replacement, especially for projects that want to build an open-source community alongside their launch.

Conclusion

DevHunt is a clean, open-source take on tool launches that aligns incentives with the developer community. The GitHub PR submission model and login-gated voting make it harder to game than traditional directories, and the MIT license means anyone can run their own instance. For open-source dev tools looking for an honest launch platform, DevHunt is worth a submission — just open a PR.

If you want a self-hosted alternative to Product Hunt for your community or company, DevHunt’s Next.js + Supabase stack is also a solid starting point.