tldr: yes. Shoutouts are one of the simplest distribution levers on Product Hunt.

Shoutouts are meant to pay it forward and highlight the tools that helped you build. But beyond goodwill, they create durable distribution for your product on Product Hunt and across LLM driven discovery.

When you shout out a product during launch, it becomes a founder review on that product s page. Founder reviews sit above regular reviews and include a link to both your profile and your product. That means your product is now attached to every future visit to that product s review page, long after launch day. For example, check out @timliao s shoutout of @Framer or @guymanzur s shoutout of @Base44

Cove has announced that they've been acquihired by Microsoft:

If you were a Cove user:

What this means for Cove

As part of this transition, the entire Cove team has accepted offers to join Microsoft, and the Cove product will be wound down on April 1. Existing users can continue using Cove until then, but we are no longer accepting new sign-ups.

We've built a data export feature so you can take your work with you. We recommend exporting as soon as possible all user data will be permanently deleted on April 1.

To export your data:

1. Sign in to your Cove account and go to your Account page.

2. Click the Export button.

3. You'll receive an email with a download link when your export is ready. The export will be a ZIP of HTML files containing all spaces you've created.

4. To export spaces created by others and shared with you, export each of those spaces individually.

Learn more in our Migration Guide.

Hey all,

I wrote a forum post not long ago on marketing as one of the rising in importance hires for all startups. This is all the things we've done, with some results and free resources.

Let me start from the creator s perspective:
I personally don t have a product (apart from hiring people for creative work or offering personal consultations).

But as a creator, I constantly share content, insights, and information, value that helps me build trust (for free). Based on that perceived expertise, people eventually decide to work with me (a paid service).

If you re still sitting on your launch, this is the push.

YC made a special exception for this community: one or more companies that launch tomorrow will get a YC interview and potentially funding. A YC partner will review every eligible launch.

With the advent of clawdbots, it's as if we've all lost our inhibitions and "put our lives completely in their hands."

I'm all for delegating work, but not giving them too much personal/sensitive stuff to handle.

There are so many launches on Product Hunt every day. How do you decide which ones are worth clicking into?

What s your #1 filter or shortcut?

It may feel like you ve considered everything:
product page, positioning, network support, social media content even day planning.

We thought we did too.

TL;DR: Anthropic refused to sign a contract with the Pentagon that would have allowed the U.S. military to use all of its models without restrictions. Anthropic insisted on an exception, and brace yourself, that its models cannot be used: 1) for mass surveillance of citizens, 2) for autonomous killing. Now the administration is threatening that if the founder of Anthropic doesn't change his mind by a certain date, they will come after him.

Google, OpenAI, and Musk (Grok) have all signed the contract.

Following Sam Altman's announcement over the past few hours, people have been speaking out massively about cancelling their OpenAI subscriptions and subscribing to Claude.

Road to 1,000,000 #Votap users Day 54 | Current: 1279

One recurring issue we ve been seeing with Supabase setups is not the database itself, but how credentials are managed across environments. The common pattern looks something like:

• credentials stored in .env files or secrets managers

• multiple environments (dev, staging, prod)

• manual propagation or duplication across those environments

It works, but over time it seems easy for things to drift:

• a key gets rotated in one environment but not others

• a redeploy misses an env var

• credentials get misconfigured during setup or migration

Hey PH community. Yesterday we launched ClawSecure and landed #2 Product of the Day

ClawSecure is the free security scanner for OpenClaw AI agent skills. But I'm not here to pitch. I just want to share real traffic numbers and what I actually learned from our Product Hunt launch, so it's useful for other makers planning theirs

I am a Computer Science student doing research into how solopreneurs and small startups create new apps and what their stack looks like. Particularly, I'm interested in how you handle things like authentication, billing, and permissions/authorization in your apps.

Let me know what you're working on below and how you're going about it -- I'd love to connect for some quick calls to learn about your product and talk about your process in building it!

A huge thanks to everyone who tried Pinnacle, commented, challenged us, and shared thoughtful feedback last week
We were excited to finish as the #4 Product of the Day. More importantly, the launch gave us a clear signal about what resonated most.
For anyone new here: Pinnacle turns your iPhone into an AI performance coach. It uses built-in phone sensors, conversation, and wearable data via Apple Health to help you improve focus, resilience, energy, and performance with science-backed tools.
You can download the app here:
https://apps.apple.com/us/app/pi...
A few things that stood out:
1. People want insight, not just more data
One of the strongest themes in the comments was that raw metrics alone are not enough. People don t want another dashboard full of numbers with no context.
They want to understand:
How am I doing right now?
What is driving it?
What should I do next?
That is a big part of how we think about Pinnacle. The goal is not to flood you with biometrics. The goal is to turn signals from your body and behavior into something actionable in the moment.
2. Low-friction measurement really matters
A lot of people responded to the fact that Pinnacle works from the iPhone you already have, without requiring extra hardware to get started. That convenience matters more than we expected.
Several comments also pushed on an important challenge: accuracy and calibration. They were right to do so.
If you are using phone-based measurement, the system has to adapt to the individual, establish a baseline, and avoid overreacting to noisy signals. That reinforced one of our core beliefs: relative progress from your own baseline is more useful than generic scores.
3. Personalisation has to reflect real life
One of the most useful questions we got was whether brain-performance baselines should account for hormonal cycles. The answer is yes.
If you want to understand focus, energy, and resilience properly, context matters.
Personalisation cannot stop at a single static baseline. It needs to reflect the realities of each user s life, including sleep disruption, parenting, pregnancy, postpartum recovery, and cycle-related changes over time.
This is an area we want to keep improving.
4. Coaching works best when it is personalised to state, not just prompts
Another theme was the difference between Pinnacle and a standard LLM.
People have already tried using general AI as a coach, and the common experience is that it still puts too much burden on the user to know what to ask.
What we are building is different: Pinnacle combines conversation with biometric and behavioral context, then guides the right intervention at the right moment.
That might mean breathwork, reflection, a micro-break, or a focused coaching prompt depending on what the system sees.
5. Trust, privacy, and product feel are part of the product
Some of the best questions were about privacy, camera use, and whether the experience feels helpful rather than intrusive.
Those are not side questions. They are central.
We want Pinnacle to feel like a calm, intelligent coach, not another noisy app demanding attention. That means being thoughtful about privacy, clear about how sensing works, and careful about when the product should guide versus when it should get out of the way.
What we re doubling down on now

• Better baseline calibration and more personalised scoring

• Stronger coaching flows based on both conversation and biometric context

• Continued work on attention measurement and training

• Better support for more diverse stress and recovery patterns across users

• Making the product feel lighter, clearer, and more useful from day one

Launch day was great, but the real value has been seeing which parts of the vision people immediately understood, and which parts we need to explain better.
If you have tried it already, I d love to hear: what clicked for you, and what still feels unclear?

We've spent the last few months building Genie, an AI analyst inside Databox. Tomorrow it goes live on Product Hunt.

The short version: you ask a question about your data in plain language, Genie finds the right metrics, runs the analysis, and returns an answer with a chart in seconds. No SQL, no waiting on someone else.

If you've been following along in this forum, thank you the conversations here genuinely shaped how we think about the product.

We go live at midnight PT. If you want to support the launch, the one thing that matters most: make sure you have a Product Hunt account before midnight. Votes from accounts created on launch day carry much less weight in the algorithm.

Meow world, welcome back to The Breakpoint, a weekly thread on all things dev tools on Product Hunt.

The latest

Recent dev-first products launched on the site

I recently saw a marketer with 10k+ followers launch and finish 6th with 348 upvotes. They followed a proper pre-launch and post-launch plan, did everything right, and still the outcome felt unpredictable.

Now I m launching @Curatora next week.

I m not a marketer. I have a little over 1k followers. Of course, asking for support helps. But I also keep hearing that a large part of the Product Hunt community shows up mainly for their own launch, then goes quiet until the next one.

That makes me wonder: how much of success here is strategy, and how much is timing and network effect?

As usual, Y Combinator came up with segments that are worth investing:

1. Cursor for Product Managers
2. AI-Native Hedge Funds
3. AI-Native Agencies
4. Stablecoin Financial Services
5. AI for Government
6. Modern Metal Mills
7. AI Guidance for Physical Work 8. Large Spatial Models 9. Infra for Government Fraud Hunters 10. Make LLMs Easy to Train

Most of my classmates from elementary school, high school, and university have been married for a long time and have had kids for at least 4  5 years.

But none of them started a business. They got jobs, their shift ends at 5 on Friday, and then they go enjoy their free time.

New AI models pop up every week. Some developer tools like @Cursor, @Zed, and @Kilo Code let you choose between different models, while more opinionated products like @Amp and @Tonkotsu default to 1 model.

Curious what the community recommends for coding tasks? Any preferences?

When you re-record a demo, it's rarely because the capture is broken. It's usually something small, maybe a line you didn't like, a weird pause, or the webcam overlay blocking part of your demo.

And at that point, you're either re-recording the whole thing or dragging the file into a separate editor just to fix one moment.

According to @RevenueCat 's State of Subscription Apps 2026 report, "hard paywalls convert 5x better than freemium, but with significantly wider variance."

Day 35 download-to-paid, freemium vs. hard paywall

Does access method impact download-to-paid conversion within 35 days?

Would love to get feature requests from active users. Thanks!

With tools like Claude Code, we re entering a world where products can be built end-to-end inside AI workflows.

But there s a problem I ve been thinking about: As building gets faster, user research risks getting left behind.

At Velozity, we ve been working on solving this by launching an MCP server that brings user research directly into these environments.

Now inside your coding workflow, you can:

You spent thousands translating your site.

French. German. Spanish. Japanese. Maybe more.

Here's the painful truth: Your site is translated. Your AI visibility isn't.

When a German user asks ChatGPT in German about your category, you're invisible. When a French prospect searches Perplexity in French, your competitor shows up.