Connect with the Product Hunt community

Hi everyone!

I'm super excited to share our new visual launch editor. It's built to make launching on Product Hunt a lot easier.

We teamed up with @GoogleCloud for a Cloud Run Hackathon October 14th!

To kick things off, we're celebrating on the leaderboard so you can meet the people behind Cloud Run.

I am delighted to let you know that the next official release of the Mantra Meditation Timer is now available for download from the Apple App Store. 

This release introduces the following updates.

One thing we've been focusing on while building Dots is performance.

Dots turns your Mac's notch into a customizable workspace, where you can access apps, websites, shortcuts, and even developer tools.

But here's something we've been thinking about: what's the point of building a productivity app if it ends up slowing down your Mac?

For us, RunEvr is the environment where we actually build RunEvr =)

For me, that s one of the most beautiful parts of having a product - using it while continuing to build and improve it.

We do our everyday calls there, share ideas, chat, store files, do reviews, complete tasks

And all of this is happening inside the same environment we re building to help other teams do exactly that!
Kind of a mirror within a mirror =D

Hi everyone, Roy here, one of Radar's makers.

We first launched here in May, and since then Radar has been installed more than 25,000 times. Today we're back with AI investigations: click Investigate on a failing Kubernetes workload and the agent you already use (Claude Code, Codex, Cursor or OpenCode) digs in, read-only, and comes back with its findings and the evidence behind them. Our upgraded MCP server gives any agent the same view of your cluster.

Quick build-in-public update from Sponkly (real-time voice translation for chat, calls and meetings in 32 languages).

This week, as a solo bootstrapped founder:

• NVIDIA Inception: accepted

• AssemblyAI Startup Program: accepted

• AWS Activate: $10,000 in credits

• LiveKit Startup Program: approved today, $17,000 in credits + a year of the Scale plan

What I will use it for: Sponkly's calls and meetings are peer to peer today (WebRTC mesh). Great for 1:1, heavy beyond 5 6 people. Moving meetings to LiveKit rooms means one upload per person, so translated meetings can grow, and the live interpreter can join as a LiveKit agent that hears each speaker directly and translates once per language instead of once per listener. 1:1 calls stay peer to peer (cheapest, end-to-end).

I m trying to separate more features from workflows that genuinely remove friction.

The most useful ideas are often ordinary: authenticating to a server, moving a file, recreating a session, checking a coding agent, or running one command across several panes.

What terminal task still makes you open another app or repeat the same setup?

I m building xtty around the idea that the capabilities developers regularly need should already work smoothly together not as a toolbox of disconnected tricks.

Single agents are manageable. The moment agents start handing work to each other, failures stop being traceable. One bad output becomes the next agent s trusted input, and the break shows up far from where it started.
If you ve got a multi-agent system running reliably in production, what made it work? Narrower tool scopes, strict handoff rules, better tracing, fewer agents?

We've been working on Dots, a macOS app that turns your Mac's notch into a customizable workspace.

One of the features we've added is drag and drop.

The idea is pretty simple. Instead of opening another app or switching windows, you can just drag files into your notch and access tools like file conversion right there.

We built Dots natively using Swift and SwiftUI because we wanted it to feel like a natural extension of macOS rather than another window sitting on your desktop.

A Semrush analysis of 1,094 US commercial categories found that only 15.2% had a clear brand leader in ChatGPT recommendations.

The study also found that 89.3% of estimated search demand belonged to categories where no single brand consistently led recommendations.

0.3.21 is out. The envelope that held finished sub-agents is a little green book now. When a sub-agent finishes, the book on its session's row says how many are new. Open it and each one is a document named like a .md file, with who wrote it, how long ago and the first two lines. Read all shows what it was asked and everything it handed back.

We recently saw a bump in churn and assumed our pricing was off. But when we looked deeper at the canceled accounts, most of them were users who bought on impulse during a promo and never really fit our core use case in the first place.

It made me rethink whether price sensitivity is the real issue or if we re just attracting the wrong audience.

When your churn spikes, how do you determine if it's a value fit problem or a pricing structure issue?

Not the dramatic stuff that gets blocked. The quiet things you only notice an hour or a week later

Mine was two agent sessions working in the same repo. One of them went to clean up its own background process by matching the name and killed the other session's run too. No error anywhere. I just found a half finished job later and had to figure out why

Making a product is one big challenge. But shifting your mindset from building to marketing it might be an even bigger one.
As makers, we spend so much time improving the product. Then comes the question: How do we get people to discover it - and ultimately turn that attention into real customers and sales?
I'm not sure traditional approaches like email marketing and constantly posting on social media are enough anymore. The way people discover products is changing.
So I'm curious:

How do you approach marketing your product?
And for the marketers here:
What would you consider a modern marketing approach in 2026-2027? What would you advise an early-stage founder to focus on?
I'd love to hear different perspectives...

Hey makers

In March we launched Tobira here and you got us to #1 of the day. Thank you again!

I believe that visualizing our dreams and goals can make them come true.

We set a point where we want to be, and naturally start drawing lines toward it. We create sub-goals, sub-dreams =D and step by step, finally get where we wanted to be.

we've been testing websites for agent readiness while building Dedica, and one thing we're noticing is how many sites still struggle with basic agent interactions.

curious if anyone here is actually tracking AI agent traffic yet?

Something I started to understand better is that fortune might be the result of the steps we take.

From a young age, I always believed I had some kind of fortune - passing exams, getting license or verified somewhere... Somehow, things worked out for me =D

But getting older and, hopefully, wiser, I started looking at it from another perspective.

I think that fortune comes from the steps we took earlier.

Quick poll for founders (and anyone who tests out new SaaS tools): do you ask for a credit card upfront, or let people straight in?

We went with requiring a card for k dlo. The thinking was pretty simple: fewer signups overall, but higher intent people actually kick the tires instead of bouncing after two minutes. Without a card, you get a flood of accounts that log in once and ghost.

But I m genuinely torn here. A card wall definitely kills casual curiosity, especially when you're an unknown product. On the flip side, no-card trials often just give you vanity metrics that don't convert.

Two quick questions:

Hey everyone :)

We've been experimenting with AVP, the tool I launched recently... kind of a GitHub for coding agents.

I opened our invoices this morning... and closed them right away hehe

Claude Max for the whole team, the API on top for our agents, a few other tools here and there...

TL;DR: every fact in our graph is its own node, with properties on it. The vocabulary behind those nodes is RDF/OWL. Neither camp would call this clean, and Wikidata is not strictly one or the other either.

Here is why we ended up there.

What forced it

Our facts need to carry things that are not part of the fact: where it came from, how confident we are, whether a human has reviewed it, and when it was true. Not this document mentions X , but this specific assertion came from page 4 of this version of this document, confidence 0.8, reviewed by nobody yet, valid from March .

Every session of Claude Code or Codex re-reads CLAUDE.md, AGENTS.md, what they import, the rules and the memory index before your first prompt. And pays for it again, every time.

Lancetta's Maintenance pane lists those files, shows what a start costs against the size where Claude Code warns, and runs two dozen checks: