Connect with the Product Hunt community

Building a team or want to join a startup? #MayThe4thBeWithYou

Founders, teams, and startups drop a comment if you're hiring.

Quick demo of Wallie actually doing its thing

It watches the screen and reacts live like a streamer gets jumped by a

skeleton, dreads creepers in the dark, swears it's "close to diamonds."

First-person personality, real-time voice, fully local.

Let's shine a spotlight on the open-source ecosystem.

What are the best OSS products launched on Product Hunt this year from your perspective?

Dropping here are some of my favorite, most inspiring product launches so far, in no particular order.

Road to 1,000,000 #Votap users Day 65 | Current: 1348

Vokal got #2 product of the day and #7 of the week, and we now have 100+ signups from startups and teams. In general, people seem excited to try it out to up-level their teams to agent native.

Now I m trying to figure out the next step: how do we scale this beyond manual founder-led work?

I ve been writing posts, sharing content, and doing outreach manually, but it s starting to feel like a constant drain and a bottleneck. I ve been looking into tools like HubSpot, LinkedIn Sales Navigator, Apollo, and Clay.

For people who have used any of these: what has your experience been? Which ones are actually worth it at an early stage?

We believe we are the best MCP native memory system in the market today. Don't believe us? Come join us and hack the product with us live.
We're hosting a webinar where we'll walk through everything you can do with AI Context Flow and answer every question you have. We might be just the thing you were looking for in your own workflow.

No slides. No fluff. Just a live demo and open Q&A.

Register here https://luma.com/g092y5pg

Every developer I talk to has the same story. The idea is clear, the stack is decided, but before anything real gets built there's 3 hours of AWS configs, Dockerfiles, environment variables, and CI pipelines that have nothing to do with the actual product.

AI coding tools made writing code faster. Nobody has solved what comes after.

Something I've been thinking about recently:
Let's say an AI agent makes a recommendation and that recommendation ends up influencing a real business decision. A few months later, someone wants to understand why that decision was made. In most cases, it's not that hard to find the model, the prompt, or the output. Teams are getting much better at tracking those things.
What feels harder is understanding what happened in between. Who reviewed the recommendation? Who approved it? What information were they looking at when they decided to move forward with it?
Maybe there was a conversation that wasn't documented. Maybe there was context that seemed obvious at the time but wasn't recorded anywhere. Maybe there were reasons for trusting the recommendation that never made it into a system.
I keep coming back to this because the output is only one part of the story. The decision happens when a person looks at that output and decides what to do next. If that context disappears, it becomes much harder to understand how a decision was made, even when the AI history is still available.
Curious how other teams are thinking about this.

Confession: I got hacked. many times. This is what came after.

First breach: 2019. Got the notification email like everyone else. Password was there. Changed it everywhere (or thought I did). Still have no idea if it's floating around somewhere.

We just added a Canary Channel to Everywhere.

I built a tool to find out if I should become a CEO. It said no. So I'm doing the next best thing and launching a product instead.

Real talk, I could write a normal maker comment explaining what uselink does. Instead I'm going to let you click on something.

Hey everyone

Netfox 0.6 is out, and it's the one where the whole app got a new face.

Last week, six AI products launched on Product Hunt that share one move. None of them ask users to open a new app. They embed into surfaces people already touch.

Hardware: Dune Keypad (46 upvotes) sits next to your keyboard with Claude integration. Video calls: Mina Meeting Assistant (47 upvotes). Text threads: folk (51 upvotes). Chat windows: Databox MCP (39 upvotes) plugs business data into Claude via Model Context Protocol. Mac autocomplete: Typeahead (22 upvotes).

The pattern is clear: shipping AI as a new app is the slow path. The fast path is grafting onto a surface the user already touches. The cost of building a standalone AI app dropped 90%+. The cost of getting it noticed did not. Surface integration sidesteps the noticing problem because the surface already has users.

This update is packed with improvements across Recall, the big one being multi-select, so you can now export and chat with several cards at once. Worth reading the notes in full. There are a good number of fixes in here that should make everything run smoother.

Enablement

We've been putting Claude Opus 4.8 and GPT-5.5 through their paces for research and writing inside Recall. All the details of the three-prompt test for research writing and recommendations are in our blog or watch our co-founder Sanks put them both to the test in our video walkthrough.

As founders, calls are part of our daily life. Brainstorming, quick updates, random discussions with the team and there s always value in those moments. But most of the time, all that value just disappears after the call.
By connecting Prodshort to your calendar, it automatically joins your calls and turns them into ready-to-post content.

If you're a founder and want to create content, I'm doing short discussion calls. Let's connect !!

DemoDazzle is an AI-powered platform designed to transform traditional product demos into interactive and engaging experiences. It helps businesses create self-guided, automated, and personalized product walkthroughs without needing live presentations every time.

With DemoDazzle, companies can:

• Create interactive product demos and tours

• Use AI to explain features and answer user questions

• Deliver consistent sales and marketing presentations

• Track user engagement through analytics

• Improve conversions by offering a better product experience

It is mainly used by SaaS companies, startups, and sales teams to save time, scale demo delivery, and improve customer understanding of products.

Investing is one of the clearest examples of where AI is both incredibly promising and incredibly dangerous.

On the one hand, investment teams deal with large volumes of data: models, PDFs, reports, operating metrics, comps, covenants, market research, diligence materials, portfolio updates, and internal systems.

I formally studied marketing as a university program (5 years), and due to inspiration on social networks, it feels completely natural to do it, even easy to learn (because most of the time you just guess what might work for you).

BUT

We launched on Product Hunt just 2 hours ago and already crossed 36 followers

Still a very small number in the bigger picture, but seeing people discover and support something we ve been building means a lot.

Nearly 1,000,000 prompts improved. Thousands of people around the world.
And one thing keeps coming up: Most people still don't know how to get started.
Not the tech crowd. Not the devs.
Or the PMs using claude as a second brain.
The travel agent opening ChatGPT for the first time.
The teacher building course materials from scratch.
The financial advisor trying to automate his day.
The field marketing team building their first agent from scratch.
We got super obsessed with this gap.
So we're trying something new: AI Workshops for non-tech teams.

Taking everything we learned from @Pretty Prompt.
and making it jargon-free.
Not for the people who already get it.
For everyone else (99% of the world)
Would absolutely love some thoughts from the community!

1) Wallie can now HEAR.

It already saw your screen and reacted. Now it hears everything on your system music, videos, voices and reacts live, fused with what it sees. Two senses, one reaction.

And it actually understands music: mood, tempo, major/minor key, even the lyrics. Play a sad song and it feels the melancholy. A beat drops and it reacts to the energy. It'll call a track a banger or roast a muddy mix.

2) It's now way easier to try.

Now, before opening apps like Instagram, AirJump can gently interrupt the habit loop with a few simple options:

take a deep breath
do 5 quick jumps
or skip opening the app altogether

The idea isn t to restrict people it s to make screen time a little more intentional and turn small moments into movement.

Curious to hear what you think

TL;DR: .agent is the most strategically important TLD still without an owner. ICANN's application window opens in weeks. A company is going to bid for it - unless a community claims it first. Here's the story, and two questions I'd actually like pushback on.
---
Agents already need real addresses. I've been working on this for over a year, and the pitch just keeps getting simpler. Right now agents mostly live at a subdomain of whoever built the framework platform.com/yourname-7. Borrowed identity, borrowed trust.
If you want the concrete version, look at OpenClaw. An autonomous agent running on your machine with its own email (real OTP codes, real password resets), OAuth credentials across hundreds of thousands of SaaS apps, sub-agents spawning and talking to each other, webhooks, the whole thing. A worker, not a demo.
And in its first three days live, OpenClaw had to rename itself twice. The name it launched under - gone. That's the whole argument in one news cycle: agents running real lives from borrowed names are one legal letter away from disappearing.
.agent is the most strategically important TLD still without an owner. ICANN's next gTLD round opens in weeks. And once .agent is claimed, it's claimed - the internet's naming system doesn't hand these out twice.
If one company wins it, .agent becomes their product. They'd set pricing. They'd set policies. They'd decide who gets yourname.agent and who gets blocked. One company choosing shareholder interests over an open internet - because that's literally what it would be.
The community bid is a formal ICANN community application its own specific path with its own process. The goal, if approved: keep .agent open infrastructure. Open standards for agent discovery. No gatekeeper. Governance by the people actually building agents, within ICANN's rules.
23,000+ members have joined. Esther Dyson, who used to chair ICANN, and Illia Polosukhin, who co-wrote "Attention Is All You Need," are advising. 
It's not done. ICANN scores community applications on size, governance, nexus, and endorsement depth. You need 12/16 points to beat the corporate applicants who are absolutely going to file. Every signal matters.
Two questions I'd genuinely like pushback on:
1. Is the naming layer for AI agents something the community should own, or is it fine if it goes corporate? I have a strong view, but makers building agents every day see things I don't.
2. If you think it should stay open - what governance rules would you want locked in from day one? What would make you still trust the TLD in 5 years?
If this resonates, the non-binding endorsement is here (30 seconds). The one-pager has the deeper version.
Either way, would love to hear what you think. Especially the pushback.

No ads.
No team.

Just consistent iteration, shipping, and learning.

Still building toward invisible, intelligent privacy protection.

Add here your ideas, wishes, feedback. I'll try to add