I see so many makers spending weekends setting up n8n, OpenClaw, or Postgres on a VPS. They think they're saving money.

But your time isn't free. SSL certs expire. Updates break things. Backups fail. One 3 am debugging session and you've lost any "savings."

Unless you have compliance reasons, just pay for managed hosting. Am I wrong? Tell me why self-hosting is actually worth it for you.

AI is incredibly good, I d even say almost perfect.

And for many people, that uniformity of perfect templates is starting to feel annoying.

People s motivations for wanting something of their own vary quite a lot.

So far, though, I ve most often heard these three answers:

• To make a lot of money.

• To work really hard until 30 so I can relax later in life.

• Time and location freedom.

I'll start.

Supabase. Found it here three years ago. Thought it was just another backend. Now I can't imagine building without it.

Here's what it does for us at Rankfender:

Auth that doesn't make you crazy. We have users across 120+ countries. Supabase handles sign-ups, logins, password resets, magic links, OAuth with Google and GitHub. It just works. We didn't have to build any of it.

I feel like a lot of product bloat starts with a request that seems totally reasonable in the moment.

Then it ships, and months later you realize it added more complexity than value more support, more exceptions, more maintenance, and one more thing the product has to carry forever.

Would love to hear examples from other builders. What s one request you wish you had handled differently?

I'll go first.

I still reply to every comment manually. Reddit, LinkedIn, Product Hunt, forums, Twitter, Discord. Every single one.

AI could do this. There are tools that generate replies, post on schedule, analyze sentiment, even mimic your brand voice. But I don't use them. Here's why.

A 2024 study on community engagement across 500 brands found that personalized responses drive 3.2x higher retention and 4.7x more repeat interactions than automated replies. People can tell when a response is copy-pasted. They can feel when no one actually read their comment. The average user only needs 2-3 automated interactions before they disengage entirely.

We all have that one tool that quietly changed how we build, ship, or market something we found way later than we should have. For me, it was a simple log monitoring tool that saved hours of debugging at 2 am.

What's yours? Could be for design, code, analytics, user research, or even project management.

Trying to discover some hidden gems the community actually uses (not just the popular ones).

This is probably a shared problem for a lot of people right now.

It s Monday (but honestly, it happens on other days too) many people try to sync up, you end up with endless calls scattered throughout the day, and:

Not gonna lie.

A topic like this was outlined on X, and many people were discussing it.

For years, I ve been hearing that we re a mobile-first (or even mobile-only) society.

Smartphones are portable. We spend the most time on them.
Distribution via App Store / Play Store is huge.

So logically You should build for mobile, right?

When AI entered the public stage in 2023, I was working as a copywriter. One client gave me a condition:

either I write more articles using AI for the same price
or I lower my rate per article

That was when I realised this job was starting to change significantly. (And I ended up.)

YC-backed @Mintlify (YC W22) just announced a $45M Series B round, bringing their total funding to $67M, to "accelerate [their] mission of building the knowledge infrastructure for AI."

Read in their blog announcement:

Mintlify now powers documentation for over 20,000 companies, with content reaching more than 100 million people every year. This round accelerates our mission to become the knowledge layer that makes products understandable, usable and discoverable by AI agents.

1. Y Combinator startup will pay humans to help AI agents when they get stuck. (This is what I read today.)

2. At the same time, I see how Indian employees in production have cameras on their heads, and the AI learns from their movements (practically filming their firing process).

3. In addition, there was already a site where AI agents hired human actions for stablecoins.

• First, AI worked for us.

• Now we are starting to work for AI.

• And eventually, will AI work (without us)?

I don t want to portray a Terminator scenario where people will have to unite against AI, but what future awaits us in terms of cooperation/non-cooperation with AI?

We re teaming up with @Vercel for a special launch day on Product Hunt.

If you re building on Vercel, schedule your launch for midnight PT on April 17 and tag it under 'Vercel Day' to be included in a dedicated leaderboard for the day.

Hey ProductHunt!

Trophy is now powering over 24M streaks which is kind of crazy to think about considering we only launched 1.0 here in January this year.
One of the parts I find most interesting about building horizontal infrastructure is that as you scale and power more and more products you get to see insights that most teams building in isolation will only see a part of, and you can use those insights to make the the infrastructure better for everyone.
For example, because we power streaks for so many users, Trophy can tell that 25% of all streaks are lost on a Friday, closely followed by Saturday (19%) and then Wednesday (18%).

Hey everyone

ClawOffice was a bit of a gimmick - a 3D virtual office for AI agents. It was fun to build and got some attention on launch, but let's be real: it didn't take off. People thought it was cool for a minute, then moved on. No real retention, no real problem being solved.

Here's what I actually learned from it:

• Novelty value. A cool concept gets you a launch day. It doesn't get you users who come back on day 30.

• I was building for the demo, not the workflow. ClawOffice looked great in a screenshot. It didn't solve anything measurable for anyone.

• "What gets tracked gets improved" is real. The founders I talked to afterward all had the same pain - they were shipping features and running experiments with no clue what was actually driving revenue.

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.

1. I've always been on the personal brand side. More and more founders are building it now (sometimes even before the product is ready while it's still in development, before seed fundraising). The CEO builds their position so the product sells more easily at the official launch.

2. But I have experience with people who built the product, scaled it, and only then did we discover who was behind it.

Honestly, with the first approach, I'd be concerned that people invest more in me as a person than in the product. People would idealise the founder and overlook the product's flaws (which could hurt development and constructive feedback).

+ I noticed the most common mistake that many people who started building a personal brand first, connected their product to their personal accounts (emails, social media, etc.) and started having a problem selling these things, because they cannot "give someone keys" to their personal profiles.

@Wispr Flow launched on Product Hunt back in 2024. Since then it has become one of those tools that quietly sticks. It's the AI dictation tool a bunch of us here use day to day (yes, there are still a few people committed to typing everything out). It works anywhere on your Mac or PC, so you can just talk and have clean text land wherever your cursor is.

For the next three days, it is showing up on the leaderboard in a different way. From April 14 to 16, you can upvote and comment on Product Hunt using Wispr Flow directly. If you use dictation, those upvotes and comments will carry a bit more weight. Try it out by clicking the Wispr Flow unit on the Leaderboard and telling it to upvote a product name

We just shipped v1.10.0, and this one is all about making prompt iteration feel a lot less painful.

You write a solid prompt but then only specific parts need changing.

Before rewrite the whole thing
Now just tweak the actual part that matters.