Connect with the Product Hunt community

If the agent writes the code who s actually testing it?

Do you still go through edge cases and user scenarios manually, or are you also delegating please break my app to another agent now?

We just added a Canary Channel to Everywhere.

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

Last summer, the idea for my SaaS, Xolora, started to take shape. Around the same time, the concept of vibe coding was blowing up. As a non-technical founder, it sounded like a dream come true. No coding experience? No problem, just let AI handle it.

The beginning was incredibly promising. Using Emergent made me feel unstoppable. I was seeing my idea come to life.

We had a comment in our codebase that said SQL Server doesn't handle pagination well, so we should just avoid pagination for now. And it did exactly that: shipped the entire result set to the browser and let it sort itself out. Same deal for Spanner.

A lot of Basedash is just "run the SQL the user wrote, show the rows." We support 10+ dialects (Postgres, MySQL, BigQuery, Snowflake, Athena, SQL Server, Spanner, and friends), and every query gets paginated because we can't stream a 12M row result set to a browser.

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?

Building Hayley has meant reading a lot of research on how people process decisions out loud.

The patterns that come up most: a relationship that needs a conversation you keep avoiding. A business decision that's already made but won't stop reopening. A version of yourself you're not sure you're living up to.

Curious what it is for the people in this community. Not looking for details, just the category.

"Data portability doesn't make money."

I heard this for years - from market leaders, from VCs, from people I respected.

"This is a regulatory problem, not a technical one." "This is a feature, not a product." "People don't pay for idealistic things."

<<Back story>>
In 2019, my team and I went deep into Self-Sovereign Identity: wrote research papers, ran experiments, and found ourselves at the intersection of data, identity, and web3. Right at that intersection lay data portability and sovereignty: the ability to own your data and take it anywhere on the internet.

It's nice to see that App Store reviews tend to move much faster after the initial approval.
48 hours for the initial review and just 8 hours for the latest update.
Anyway, Tamadoggo just got a new release, and starting today, Crib is now open to all cats!
If you're looking for a pet journal that happens to be pretty smart for your feline companion, I'd love for you to give it a try and share your feedback.

DemoDazzle is an AI-powered platform designed to transform traditional product demos into interactive and engaging experiences. It helps businesses create self-guided, automated, and personalized product walkthroughs without needing live presentations every time.

With DemoDazzle, companies can:

• Create interactive product demos and tours

• Use AI to explain features and answer user questions

• Deliver consistent sales and marketing presentations

• Track user engagement through analytics

• Improve conversions by offering a better product experience

It is mainly used by SaaS companies, startups, and sales teams to save time, scale demo delivery, and improve customer understanding of products.

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.

So far, the impression I have of this community and maker circles is that you work every day.

Which is great, it s one of the reasons I m here.

That's a lot of AGI, with some substantial firepower:

Anthropic has raised $65 billion in Series H funding led by Altimeter Capital, Dragoneer, Greenoaks, and Sequoia Capital, valuing the company at $965 billion post-money.

From Coatue, who lead the round:

...what s changed since three months ago (the last round was only three months ago, believe it or not)?

Three things:

1. We ve seen the shift from co-pilots that help make us more efficient to agents actually doing long-form work tasks on our behalf. This has meant an explosion in both productivity and ROI for customers.

2. Anthropic introduced Mythos Preview, a whole new model class that demonstrates a step change in intelligence level as seen in the METR chart below. It not only shows dramatic improvement to coding and long-running agents, it is also defining a new frontier for security.

3. And finally > use cases spreading from coding to everything else.

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.

For months, we celebrated our power users at Murror the ones journaling every day, sometimes multiple times a day. They had the highest session times, the most entries, the best retention curves. On paper, they were our success story.

Then we started reading what they were actually writing.

When someone journals on Murror, our AI doesn't just process text. It reads emotional weight. It picks up on patterns the user might not see yet -- the way their language shifts when they talk about work versus family, the recurring themes they circle back to every few weeks, the gradual change in tone that might signal something deeper.

We built this because it makes the product better. The AI can ask more relevant questions, create more meaningful reflections, and know when to give space versus when to gently prompt.

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.

Hey everyone, Elitza here, founder of own.page

A few days ago, own.page reached #2 Product of the Day on Product Hunt.

As a solo founder competing against products backed by much larger teams, this wasn't something I expected - but it was something I was determined to achieve. There were moments during the launch when I thought it would be incredibly difficult.

But this incredible community showed up.

Some of the most notable examples of today s wealthiest entrepreneurs started relatively later in life. (e.g. Jeff Bezos in his 30s)

But the speed of today s world (driven by technology and information) is changing that.

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

Six months ago, our team was obsessed with making Murror's AI more intelligent. Better pattern recognition, deeper emotional analysis, more insightful reflections. Every sprint, we'd ship something that made the AI sound smarter.

And our users started disengaging.

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?

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?

What motivates you to build your product? For me with @Bitgrain, it's my passion for creating with graphics. I needed a tool to make grunge posters myself, so I built one, and figured, why not share it with everyone else?
What's yours ??

For Bitgrain, we found that maximum users came from blog features! yes and to be exact, the new users spiked upto 8.8k on a single day (that was the highest) and all came from blogs! Currently the max source is organic search and ai responses.
Which channel is working the best for your brand?