Connect with the Product Hunt community

Here's a marketing problem no one prepares you for: what happens when your product's success means people stop using it?

At Murror, our best outcome is when someone works through what's been weighing on them and doesn't need to come back for a while. They journal, they process, they gain clarity and then they go live their life. That's the whole point.

Two releases since split panes landed. Here's what shipped.

v0.27 Pins & Notes

You know the "found this, not ready to fix it yet" pile? Now you can pin any terminal output to a per-project rail and work it as a checklist. Title + body per pin, drag to reorder, done items collapse. Works inside full-screen TUIs like Claude Code, not just plain shells. A notes scratchpad sits under it and autosaves per project.

Tomorrow is Alpha Day

Same deal as before. If this is the first time your product is going anywhere public, launch by midnight tonight (PT time), add the Alpha launch tag, and you'll be put on a special leaderboard. Alpha launches also get a boost on the leaderboard

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

SQL definitions: reusable snippets across your queries

You can now create SQL definitions scoped to a database connection versioned, named SQL snippets that you can reference inline in any query with {{ definition("name") }}. Definitions get their own home in the Data page sidebar where you can create, edit, describe, and preview them, and the expansion is applied both for human-run queries and for queries the chat agent runs on your behalf.

The chat agent understands definitions too, so when it writes SQL it can reach for your team s definitions automatically. Admins can also let the agent propose and save new definitions when it spots a pattern worth keeping around so the SQL your team relies on becomes a real, reusable building block instead of something everyone re-types.

Spotify started the disco ball party last week. Notion, MoonPay, Uniswap joined. Even Lovable showed up late with a tool to discomorph any logo. 

I feel like the weird lonely dude on the Product Hunt dance floor.

If you're launching soon, drop your disco ball logo in the comments
Use: https://discomorphism.lovable.app

AI has undoubtedly made our work easier and faster.

An article that would have taken me several days before (defining the topic, doing research, interviewing experts for unique insights, validating data, and writing the final piece) can now be turned into a solid article in under two hours. (in my case, when I publish a weekly newsletter)

People always say they want simple products. Bloat is a big reason people dislike products and migrate away from existing tools. But I don't think that bloat comes from having too many features. Instead, it's mostly a UI/IA problem.

This is something we think about a lot at @Basedash. Analytics and BI can get complicated quickly: permissions, SQL, charts, dashboards, filters, joins, data sources, teams, sharing, alerts, and so on. We can t remove all of that complexity, because real teams eventually need it. Instead, we're trying to figure out how/when to reveal that complexity. Filters only appear if you ask the AI. Access controls can get super fine-grained, but only if you start inviting more teammates.

If I could sum up building in public in two words, it would be: course correction.

We launched AI Context Flow on Appsumo a few weeks ago, and turns out, managing AI context across tools is more nuanced than we thought. Thousands of people tried our product and one piece of feedback kept recurring: users needed more control over memory curation.

The demand was clear, but our product had missing features. So we did what any startup team does: we course corrected and went to our cave to build out what users needed.

Here's what we just shipped:

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.

This Monday, The Incident Challenge is back.

New challenge. New product updates. Built directly from your feedback.

Last time, only 20% reached the correct fix.

Hey Product Hunt community

It s been a week since we launched Ovren - and I just want to say a genuine thank you.

We built Ovren because every team has backlog work that never makes it into a sprint.
Not more ideas. Not more AI suggestions.
Real engineering work that needs to get shipped.

So we launched Ovren as an AI engineering execution product for real backlog tasks:
AI frontend and backend engineers that work inside your real codebase, execute scoped work, and return reviewable code updates.

Hey PH community

We're in the middle of our AppSumo launch for AI Context Flow, and I wanted to start a real conversation here rather than just drop a link.

The problem we're solving: most people using AI tools daily are paying what I call an "AI context tax", the time spent re-explaining your project, background, and goals every single session, to every single tool.

ChatGPT doesn't know who you are. Claude doesn't know who you are. Gemini doesn't know who you are. And if you're jumping between them (like most power users are), you're paying that tax multiple times a day.

Last quarter, we built a feature at Murror that our engineering team jokingly called "the empty room." After a user finishes a journal entry, the AI doesn't immediately respond. It waits. For 30 seconds, the screen shows nothing but the user's own words and a gentle prompt: "Sit with what you just wrote."

No analysis. No reframe. No pattern recognition. Just silence.

Hey Product Hunt

Almost 6 years ago, @Mailwarm launched here.

Back then, the idea was simple: help teams warm up their inboxes and build sender reputation before scaling email.

That launch changed a lot for us.
Mailwarm became #1 Product of the Day and Product Hunt helped us get our first real wave of visibility, users, and feedback.

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.

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.

Greg Isenberg (https://x.com/gregisenberg/statu...) asked what every SaaS tool looks like if it was built purely for agents.

That question stuck with me because I think collaboration is one of the biggest categories that needs to be rebuilt.

Most tools today are still human-native:

• Slack is for humans messaging humans

• Linear is for humans managing work

• Notion/Obsidian are for humans organizing knowledge

• agents are still trapped in terminals, browser tabs, and private chats

We're back on AppSumo, for Sumo Day! I'm equally excited and terrified

5,000+ people bought Pretty Prompt on our last run on AppSumo

Broken only by my trip to Burning Man in 2023 after which I got back on Product Hunt on September 8, 2023 I just hit my 1000 day streak again.

Which is a curious milestone, given that there was a day back in April where Product Hunt hit over 1000 products launched in a single 24 hour period.

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.

Building a team or want to join a startup?

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

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.

Building in public is important today. It helps you build a community, get feedback, and create traction around your product. But creating content to share every day shorts, posts on X, LinkedIn, Instagram can quickly become boring and very time consuming.
By recording your meetings with Prodshort, you get content ready to share: Shorts, X posts, LinkedIn posts... You keep things authentic, because the AI documents what you actually do and doesn t create fake content from scratch. Your real progress, your real discussions, your real decisions become things you can share.

It makes build in public much easier. You can share updates about your project directly from your calls: progress, ideas, feedback, small wins... Stay consistent with your build in public without adding extra work to your day !!

The funds will boost open-source / Postgres tools, grow the platform, and liquidity for the employees.

Two months ago, @Supabase announced 8,000,000 developers building with the platform. [1] They're now nearly 10 million, with databases launches growing by 600% over the past year.