Connect with the Product Hunt community

We're partnering with Vercel to bring Vercel Day back to the leaderboard

If you're building on Vercel, now is the time to get ready to launch. Schedule your product for June 16th, add the tag vercel-day to your launch, and you're in.

This could be related to your industry, or even a side project you're working on.

Here are my 5 (I couldn't function without them):

1. Grammarly proofreading my texts, not just posts, but also client communication

2. ChatGPT / Claude mostly brainstorming, help with copy, and summarising

3. Figma I can put the basic graphics together quickly.

4. Translator sounds incredibly old-school, but English is not my mother tongue

5. Gmail and not only for communication, but also for storing ideas and sending myself email reminders for posts

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.

Side note: We're live on Product Hunt today with our Slack Data Agent!

Export to Excel

You can now export to Excel (.xlsx) anywhere you could already export data. Charts, tables, markdown tables, and in-browser record views all get a native Excel option right alongside CSV, so the data you pull out of Basedash lands in a real spreadsheet formatted columns and all instead of a raw text file you have to clean up first.

OpenAI just made AI memory automatic.
The problem? you can no longer fully audit what it remembers about you.

Dreaming V3 (launched June 4) doesn't ask you to save memories anymore. It runs in the background, reads across years of your conversations, and synthesizes a profile of you, and automatically updating as your life changes.
It remembered your Singapore trip was in the future. Now it knows you went. You didn't tell it that. It figured it out.

The audit trail problem: TechTimes reported the update "limits" what users can actually see. You used to have a list of saved memories you could read and delete. Now you have a synthesized profile that's broader than that list, and you can only partially inspect it.
A CHI 2026 study called it the "personalization-convenience paradox": the feature users value most is also the one they can least control.

I've been running Claude Code, Cursor, and Codex pretty heavily for the last few months and I keep hitting the same loop:

1. Start a task in one agent

2. Switch to something else (Slack, Twitter, another terminal)

Hey everyone

We built OpenCut AI because we were tired of video editors that phone home. CapCut sends data to ByteDance. Descript uploads everything to AWS. Runway is cloud-only and credits-based. We wanted an editor that stays on your hardware.

Here's what you get:

AI that runs locally:

A question we get from customers (and occasionally from investors) is why we don't expose a model picker the way Cursor does.

The short answer is that we're building for a different user. Cursor's users are developers; picking between GPT-5 and Claude is a meaningful choice they're equipped to make. Our users include CFOs, sales leaders, customer success reps. For them, model choice is friction at best, and at worst a new vector for self-doubt. A marketing director second-guessing a revenue number because they're not sure whether they picked the right model is exactly the failure mode we're trying to design out of analytics.

We are shipping a major update to make scaffolding your architecture faster, smarter, and completely frictionless.

The biggest news? The Solarch Agent is now free for everyone.

Here is exactly what we just shipped to improve your workflow:

AI agents are becoming part of everyday development, but most repos still don t have a clear way to tell an agent what is safe to run, what needs to be checked first, or which commands are actually trusted.

That gap is what we re thinking about with Ota: making repo execution knowledge explicit enough for humans, CI, and AI agents to follow without guessing.

Every documentation task has a different audience and purpose. A user guide for customers reads nothing like acceptance criteria for developers or an SOP for operations.

We built Document Templates so you can tell Easy Scribe exactly what kind of document you need before generation even starts. Pick a template, record or upload your walkthrough, and get a draft structured for the right context from the very first pass.

I don t want to rant here (but I probably will a bit)...

Almost every ad visual, but also a lot of organic content on social media, is very generic and created by AI (I get it, it s a cheaper and more scalable way of promoting). But when everyone does it, it becomes really hard to stand out and differentiate yourself.

Starting June 1st, @Github Copilot moved to a usage-based billing model.

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

There are a lot of products being hunted, launched, and competing for attention here.

But I still see some makers missing the very basics.

If you ve been following along and want to support us, we d really appreciate a GitHub star:

https://github.com/ota-run/ota

A pull request can change more than code.

It can add a dependency, require a new env variable, change a setup step, or make a command depend on a local service.

We re live on Product Hunt today with our Slack Data Agent.

Basedash started as a way for teams to explore, query, and visualize their data in a shared workspace.

Hey everyone, Jane here from the Publora team

On June 10th, on a day when 700+ products launched and only 21 made it into Featured Publora hit #1 Product of the Day.

This update includes a few reliability improvements, including a fix for the AI Notifications setting, along with better background performance and battery efficiency.

And since we're here... a little sneak peek

SlimSnap ships a Claude Code skill that auto-loads your latest screenshot so the agent reads the structured JSON without you pasting anything. That's the "magic" version of the workflow.

For everything else (Cursor, Lovable, bolt.new, Replit AI, claude.ai), the screenshot spec works but you paste the JSON into chat manually. It works, just not as smooth as the Claude Code flow.

Where do you actually paste screenshots into AI tools today? Vote in the comments, ideally with one line on what your screenshot loop looks like there. That tells me which agent gets the next auto-loader.

Don't take this as a date promise. Just trying to figure out which one to start with after the current backlog.

Honestly, I sometimes feel a bit of internal pressure or even fear that if I miss something, it will be hard to get back into work, especially because I m strongly embedded in tech.

And you can see it when you disconnect for 2 or 3 days and don t follow the news, you feel mentally better, but at the same time you start losing that sense of overview that feels quite important for your career.

We re live on Product Hunt today with the new Intrascope update.

Intrascope started as a BYOK workspace for teams using multiple AI models.

Now we re adding managed AI usage as well, so companies can access top AI models without managing separate API keys, vendor accounts or billing dashboards.

The goal is simple:

One thing I've noticed with AI audit trails is that they tend to do a good job of recording events but not always the reasoning behind them.
Take a simple example: An AI-generated report goes through an internal review before being shared with customers or stakeholders. Someone makes edits, approves the final version, and the workflow moves forward. Months later, if you look back, the audit trail will usually tell you when the changes happened, who made them, and which version was approved.
What it may not tell you is why those changes were made in the first place. Maybe there was a compliance concern. Maybe someone spotted a factual issue. Maybe additional business context changed how the output was interpreted. The record captures the action, but not necessarily the thinking behind it.
The more I look at AI governance, AI accountability, and audit readiness, the more this feels like an important gap. Understanding what changed is useful. Understanding why it changed is often what helps teams make sense of a decision months later.
Curious how teams are preserving reasoning context across AI workflows today, especially when outputs move through review, edits, and approvals.
Lets chat

Since our May 31 launch (v1.6), we shipped two major releases:

v1.7 added OAuth 2.0 on the MCP endpoint and importance-score-aware smart merging, so high-value memories resist being collapsed by near-duplicates.

I absolutely love this platform.

The fact that I spend time here every single day is probably proof enough.