Connect with the Product Hunt community

We teamed up with Vercel and we want you shipping this Friday.
May 15 is Vercel Day. Launch your product on Product Hunt that day with the Vercel Day tag and you're on the official Vercel Day leaderboard alongside every other builder going live that day. Top launches win prizes and get serious visibility from a crowd that's already paying attention.
This is the move if you've been waiting for a reason to launch. You've got four days.
What are you building? Drop it below

Today we're announcing our $50M Series B, led by Peak XV, with participation from YC, M12 (Microsoft's Venture Fund), Kleiner Perkins, and our earlier investors. It brings our total funding to $72M. The round closed on the back of a year in which our enterprise revenue grew 10x, and our agents crossed 1,000,000,000 calls handled.

Read their announcement.

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.

The open-source file sharing tool for people who actually care about privacy.

Ever sent sensitive data through email? Or watched your files sit on someone's cloud forever? We built BurnLink because the alternative to privacy shouldn't be inconvenience.

The Problem

Last week, @Kilo Code launched for the fourth time on Product Hunt, introducing a new VS Code extension. The product ranked #1 Product of the Day and #1 Product of the Week.

I had the opportunity to work on this launch. Here's a breakdown of what we did and how to apply it to your launch.

We've teamed up with @Y Combinator or to give builders one more chance.

Launch on Product Hunt this Friday, tag your post "YC application" @gustaf will personally review the top launches. One or more will walk away with a YC interview, even though the official deadline has passed.

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

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

I'll go first,
During the launch of @Bitgrain , I thought maybe some 10 20 people might upvote or it can be even lesser, Surprisingly it got featured and the numbers went up crazy! I got mails from people who loved the product. It was unexpected but loved it!
btw do see @Bitgrain : )

I'll be honest I've never liked the feeling that someone "owns" me.

So being employed was very distant to me. [As if I had no power over my income.]

We thought we were ready.

Bigger deals. Fewer customers. Better margins. That was the dream.

So we built enterprise features. SSO. Advanced permissions. Audit logs. A whole new pricing tier starting at $2,000/month.

We spent 6 months. Three engineers. One dedicated product manager. Endless meetings about "enterprise readiness."

Hi community

Tomorrow we re launching Spellar AI

We built it because we were tired of leaving meetings with lost context, forgotten decisions, and action items scattered everywhere.

Spellar 3.0 is an AI meeting companion that records, summarizes, and remembers your meetings so you can stay present during calls instead of worrying about notes

Small update since launch day: I added a live interactive preview directly into the PanicMode website so people can instantly try the concept before downloading the desktop app.

You can now press /Ctrl + Shift + O anywhere on the website to trigger a browser-based overlay preview of PanicMode.

We re trying something new on Thursday: Alpha Day.

The idea is simple. If this is the first time you re launching your product anywhere, you can tag it alpha and get a boost to your points (and land on a special leaderboard).

VibeAround v0.5.15 is live.

This release is about making the local-agent workflow more reliable across more model providers and coding agents, especially if you use Gemini, Vertex AI, DashScope, DeepSeek, Kimi/Moonshot, or Codex with proxied third-party models.

Hey Product Hunt

It's been 10 months since we launched Mindly here, and a lot has changed.

We've been heads-down building, listening to your feedback, and shipping, and today I'm excited to share what Mindly looks like now after a lot of changes:

What's new in this update:

Tomorrow we're going to showcase one of the coolest products to date built with Openfort. It's for everyday users that are looking for better experiences when interacting with the investing world and trading assets! Looking forward to it!

A lot of makers come out with bold claims about their idea: THE NEXT BIG THING.

In most cases, surprisingly, it s not even the next small thing. People simply don t notice it.

We launched Shadow lat week and the response blew us away. Thank you to everyone who upvoted, commented, and shared. #2 Product of the Day means a lot to a small team building in public.

For those just discovering us: Shadow sits on your calls and gets the post-call work done while you're still talking. No extra time, no context switching, you hang up and the work is already in progress.

I will go first.

"Just launch. The market will tell you what it wants."

A senior founder told me that. He meant it as encouragement. Do not overthink. Ship. Learn from real users.

The problem at MindPal was pretty simple: we have hundreds of AI templates to share. We know videos of these templates work - some have gotten us tens of thousands of views. But actually making them was a total nightmare.
We tried everything. At one point, we even hired a freelancer, but the feedback loop was exhausting. It actually took longer to give feedback and wait for revisions than it did to just make the video ourselves. It was slow, expensive, and impossible to scale.
When we did it ourselves, it was a massive grind:
Record the screen of the behind-the-scene agent builder
Record a demo of the agent working
Write a script that didn't sound like a robot
Record a voiceover or an avatar
Spend hours editing everything together
If my co-founder or I were tired or busy, the videos just didn't happen. I assumed this was just the "manual tax" you had to pay for quality.
Last weekend, I got fed up and asked Claude if I could just automate the whole damn thing.
Turns out, I can.
So I spent the weekend cooking something - an internal AI SOP to turn any workflow URL (yes, from just a single URL) into a publish-ready use case video that passes all quality standards in ONE GO.
Here is the new setup:
Playwright: Records the screen and even moves the mouse like a human
@Claude by Anthropic: Writes the narrative based on our actual product info
@HeyGen: Creates the avatar and voiceover
@Remotion: Programs the entire edit - syncing everything into a final file
@Zernio + @Railway: Automatically publishes the video and saves the assets.
Now, I just give the system a URL and a finished video comes out. I don't even have to click "upload."
I just wrote a post sharing the full behind-the-scenes build, the architecture, and the logic behind of this AI video agent. Check it out here if you think this could be helpful for your company: https://mindpal.space/article/ai...

P/s: This is what I wake up to every day now

I like working (a lot of working), but sometimes I struggle with my time.
Understand that I am not able to manage/fit everything that I wanted to do in my schedule.

So I had to "re-organise" some activities and was able to learn something or make myself productive.

Every day, after launching, makers are contacted on LinkedIn and X by people offering to sell votes. As the Product Hunt team, we are very much aware of this and really hate it. We have systems in place to neutralize this type of gaming. Every vote counts for a different number of points on Product Hunt. A couple examples:

• An account with a recently created gmail address and no history of quality contributions on Product Hunt: this vote will count for 0 points. Yes, this might be a well intentioned user, but we take a conservative approach to protect the community. If the account has a company email or applies for verification on Product Hunt, that's a different story.

• An account with a company email address linked to a legitimate LinkedIn account with a history of meaningful contributions on Product Hunt: this vote carries significant weight.

A couple questions for the community:

• Are there specific accounts on Product Hunt that you suspect participate in vote selling? You can reply here or email report@producthunt.co

• What would you want to see us do differently here?

Terminal or editor-first UI? How do you prefer to work with AI coding agents?

For us, it started from something frustrating: creating content felt very annoying and time-consuming. We tried the classic way: scripting, memorizing, filming, editing. But none of it felt authentic. And honestly, it was eating time we needed to focus on other things.

At the same time, we kept reading the same advice everywhere:
"founders should build in public and create content consistently". Easy to say but harder to do in reality. So instead of forcing ourselves to create content from scratch, we tried something simple: recording our own calls and using those moments as content.

We analyzed the codebases of 100 startups that hit a scalability wall (*)
The goal was not to find the most exotic bug. The goal was to find the most common, expensive, and preventable patterns of failure.

The results were almost identical across 85% of them. Here is what the data says.

The Timeline to Failure

Months 1 6: Everything worked. Fast releases. Happy customers. No time for architecture.