Connect with the Product Hunt community

From @eric_provencher 's announcement post:

A couple of months ago, I was approached by @romainhuet, OpenAI s head of developer experience, to join his team and help push my vision for building with these models on a scale that I could never achieve on my own. Of course, before agreeing to anything, my first request was to ensure the dedicated users of Repo Prompt, who supported my journey until this point, were taken care of. If you re reading this and you purchased an annual or lifetime license, check your inbox!

I've been an active user of Repo Prompt since I hunted it, and while I'm a little sad that it'll no longer be maintained, this bodes well for OpenAI Codex users.

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.

We keep hearing the same thing on repeat: enterprise AI token costs are exploding and the spend is largely focused on a single vendor (OpenAI, Anthropic etc.) One example: orgs that were spending $500K/year in December are spending $15M/year in May.

And CFOs are starting to ask the same question: do we cut back AI spend, or cut heads?

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

I've been working with LineageLens and just added a custom agent adapter so our internal CLI tool is attributed with prompts, model metadata, and confidence evidence. The registry design makes this surprisingly low-friction: implement a detect(input) that returns a NormalizedAgentContext (tool name, model, session ids, confidence, and evidence), register the adapter, then run the quickstart proxy to validate captures.

Why this matters: your team can capture private or bespoke tools without sending data to a vendor, and you get prompt code linkage in PR reviews and dashboards. I followed the recent repo changes (custom agents landed in late May) and found the adapter API predictable: detection should be conservative, emit evidence items, and choose appropriate ordering so your specialist adapter wins over the fallback.

If you ve extended LineageLens for an internal tool, what heuristics did you use to build confidence and avoid false positives?

On a Tuesday, the first enterprise question is usually not can you capture AI code? It s who can see the records, how long do they live, and what happens when a policy blocks a change?

That s the part LineageLens is built for. Base gives you local capture. Lite gives a shared team record. Plus and Max move the data into a backend where auth, permissions, retention, and policy live next to the provenance records instead of around them.

The useful thing here is not another dashboard. It s a self-hosted record of prompt, model, tool, file, and outcome that engineering, security, and platform teams can actually govern on their own infrastructure.

I keep seeing AI governance tools start with visibility, then discover that the real enterprise questions are identity, retention, and review. If the record cannot be scoped, retained, and exported on your side, it is not really governable.

Bitgrain is playing a bit off the field. We are aiming towards a "No AI" tool, whereas almost every other product currently targets the AI market.
This has been both, good & bad at the same time. Good because I found lots of like minded people willing to support this. Bad because again, a lot of people don't actually support this in the era of "AI Boom".
Yeah that's the direction Bitgrain is proceeding in. If it works, great. If it doesn't, then too great : )

A lot of people try to raise funding before they even begin.

And then sometimes I read those zero to hero stories. (Maybe they re a bit "polished" by the media to have publicity.)

In any case, building products has become much easier from a technical perspective, which also makes it cheaper especially for software startups.

There are founders you d love to NOT work for. And then there are founders whose company you wouldn t want to leave, no matter what.

A big part of that comes down to people, their values, and their character.

And often, that starts with the founder.

One thing that surfaced while tightening LineageLens this week: capture is not the hard part. Agreement is.

If the extension, backend, and MCP server describe the same AI edit with slightly different field names or status values, you do not have provenance, you have three believable stories about the same event. That matters because reviewers and assistants start trusting whichever surface they looked at last.

The question I keep coming back to is simple: if a record can look applied in one place and accepted in another, is that still a single source of truth?

@Bitgrain now has the option to export your studio images in HDR formats, so now that HDR enabled screens would glaze beautifully with your new hdr images! try it today at https://bitgrain.app

2 significant things are circulating on the internet simultaneously this week:

• A tweet about how a human beat a machine (a 10-hour livestream in which a human sorted packages and compared it to the productivity of a robot).

• Or an announcement of a Microsoft AI chief that predicts AI will automate most white-collar work within 18 months.

While I don't think there will be a complete replacement of humans in either case, I do think we will see mass layoffs. My guess is that it will be white-collar jobs first.

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

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

When I first added Dev Ports to Room Service, it felt like a small utility feature.

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."

Everyone's talking about how easy it is to build with AI right now.

Spin up an agent, write a prompt, ship. Done.

But if you've actually deployed something in the wild built mostly by AI, you know it's more complicated than that. Especially when you care about quality.

There seems to have two types of developers:

• Human in the loop: Those who like to control the behavior of their agents as it works, looking at the context usage, reading reasoning blocks, and approving individual file edits.

• Agent first: Those who prefer to review the output of agents, rather than individual actions, and run one or more sessions in parallel.

What type of developer are you when working with AI coding agents?

I went quiet here after 0.22. We're on 0.25.5 now, and most of what landed in between is the unglamorous stuff: speed, reliability, and getting out of your way. Here's what actually changed if you've been away.

I will go first.

"Do you do backlinks?"

Every week. Sometimes every day. From prospects. From agencies. From people who read one SEO blog post from 2018.

Backlinks are not the problem. Backlinks are a solution to a problem that has changed.

Yesterday s discussion about who is more likely to be replaced (white-collar vs. blue-collar workers) raised another question for me.

So I m asking:

What do we need to do to keep our jobs in the age of AI and robotisation?

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)

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

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 : )

We ve all been there: the engineering team ships an incredible feature, the marketing team blasts the launch, the metrics show a temporary spike in usage-and then... nothing. Silence. The feature slowly turns into product debt, and the actual value delivered to the user drops to zero.

As builders, we are constantly obsessed with shipping. We measure velocity, sprint completions, and launch dates. But somewhere along the way, we forgot to measure whether the things we build actually move the needle for our users bottom line.

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