Product Hunt 每日热榜 2026-04-09

PH热榜 | 2026-04-09

#1
Brila
One-page websites from real Google Maps reviews
1069
一句话介绍:Brila是一款通过AI分析Google Maps真实评论,自动生成一页式网站的工具,为缺乏营销能力或网站内容空洞的小微企业,解决了网站文案千篇一律、无法传递真实客户价值的核心痛点。
Website Builder Artificial Intelligence Alpha
网站生成器 AI内容创作 小微企业营销 Google Maps评论分析 Jobs to Be Done 数据驱动 一键建站 本地商业 口碑营销 内容优先
用户评论摘要:用户普遍认可其“内容优先”理念及生成效果,尤其对多语言支持感到惊喜。核心反馈集中在编辑功能薄弱(如缺乏设计自定义、编辑体验像填表)、对少量评论业务的处理效果,以及关于数据来源(API限制与爬虫风险)、订阅取消后服务持续性等实际运营问题的担忧。
AI 锐评

Brila的锋芒在于其“逆向思维”:在AI内容生成陷入同质化泥潭时,它选择回归真实世界的数据金矿——Google Maps评论。其宣称的“严肃AI系统”并非空谈,核心是将经典的“Jobs to Be Done”理论工程化为自动化分析流程,从碎片化口碑中提炼出驱动客户决策的深层动机。这使其超越了“又一个模板建站工具”,升维为一种“市场洞察即服务”产品。

其真正价值有三层:对小微企业,是零成本将沉睡口碑资产转化为最具说服力的销售页面;对营销者,是提供了绕过主观臆测、直接获取客户视角真实语言的工具;对行业,则示范了如何将战略框架(JTBD)与具体数据源(评论)结合,实现AI应用的深度化。

然而,其犀利优势也伴随锋利风险。重度依赖第三方爬取评论,存在政策与数据断供风险,构成业务“阿喀琉斯之踵”。当前MVP阶段功能极度精简,编辑体验被诟病,反映了团队“内容至上”的偏执,但也可能成为早期用户流失的漏斗。它巧妙避开了与 Squarespace 等在设计上正面交锋,却在“真实性”这个维度建立了壁垒。能否在保持内容生成质量优势的同时,快速补齐用户期待的灵活性与功能性,将决定它是成为一个利基市场的神器,还是能颠覆传统建站流程的明日之星。

查看原始信息
Brila
Website generators give you a template with made-up copy. You rewrite it for hours – still sounds generic. Brila does content first. It reads your Google Maps reviews, finds why customers actually choose you using Jobs to Be Done, and builds a one-page site from real patterns, real wording, real photos. When a business has enough reviews, the results often surprise even the owners. Not a single prompt – a serious AI system behind every website. Free plan gives you a fully generated site.

Hey Product Hunt 👋

We made Brila. It audits your business based on your Google Reviews – and shows you exactly how to market it.

The problem: every website generator gives you a template stuffed with placeholder copy. Then you're stuck rewriting it by hand – big effort, bad result. You still end up with "quality service" and "customer-first approach" that nobody believes.

Our approach: content first, design second. Google Maps reviews are an incredibly rich data source – people describe the exact situation they were in, what they needed, and why they chose this place. With enough reviews, the patterns often surprise even the business owners.

The methodology is Jobs to Be Done – the same framework billion-dollar companies use to understand their customers. Brila automates it. It's not a single prompt – it's a serious AI system we've been building for months.


Paste a Google Maps link, try it free. We're giving away 100 promo codes for a year of Pro: PHBRILA100
If it’s already gone by the time you try, leave a comment on PH and we’ll send you a code.


Thank you!

54
回复

@visualpharm Great idea!

Finally, not just another templated builder stuffed with fake copy, this is real content-first magic pulled straight from Google Maps reviews and Jobs-to-Be-Done. Exactly what small businesses have been missing.

what’s the most surprising insight or result you’ve seen from a business’s reviews so far?

0
回复

@visualpharm  This is genius, love how lean and effective it is. Congratulations on the launch!

0
回复

@visualpharm Congrats, just a quick que; for service businesses like coaches or consultants with fewer reviews (under 50), how does Brila handle pattern detection, and any tips to boost review volume fast?

2
回复

it's really gonna be interesting for small businesses. Are there any options to customise the design? change colors, fonts etc.

15
回复

@alexander_khristoforov not yet! This time we focused mainly on content editing. But layout editing is definitely on our roadmap

13
回复

@alexander_khristoforov Yeah, that's definitely the next step. Our current MVP is super minimal indeed.

1
回复

This has real potential if the editing controls get better

11
回复

@marina_green we're working on it! 🫡

7
回复

@marina_green It's intentionally limited so far, but we will definitely need a cursor-style chat for editing. Will do.

1
回复

Does Brila work well for businesses with only a few Google reviews, or do you need a lot of reviews to get a good result?

7
回复

@alina_anitei Great question! Brila works with as few as 5-10 reviews - that's usually enough to pull out real advantages, popular items, and a couple of customer quotes. The site will be thinner (fewer sections, shorter tips), but it'll still be authentic and specific to your business. With 50+ reviews the magic really kicks in - we can do deeper JTBD analysis, find patterns across customers, and fill every section with strong content. But even a handful of genuine reviews beats AI-generated marketing copy any day. If a business has very few reviews, we lean more on photos and business data (hours, location, category) to fill the page - so it still looks complete, just less review-driven.

19
回复

@alina_anitei It generates meaningful results starting from 5 to 10 reviews , but the more, the better.

Thank you for asking such a great question.

2
回复

What a creative idea, congrats on the launch! 👏

I tested it with a location where the reviews weren’t in English, and honestly, I didn’t expect the output to be this good. That was a really pleasant surprise.

If I could suggest one improvement, it would be the content editing experience. Right now, it feels a bit like working through a long form, which can get tiring. It would be great to have more flexibility, for example, the ability to add custom sections (beyond just editing the ones Brila generates) and a more dynamic, modular editing interface.

That said, I’m genuinely impressed. The approach feels fresh, and the results speak for themselves. Congrats again on the launch! 🚀

6
回复

@matheusdsantosr_dev wow, thank you so much!!

Yep, we know about the editing moment – thanks for noticing it. We have a few ideas how to improve it without building another visual editor. Initial philosophy here was simple – generate best result so users won't need to edit it. But I get it, obviously you can't make everything perfect.

BTW, would love to see what you've generated! Feel free to share!

7
回复

@matheusdsantosr_dev  So glad the multilingual part clicked! About editing, yeah, we went back and forth on this a lot. We wanted it to be flexible but also make sure you can't accidentally break your site. That's why it feels a bit rigid right now. Custom sections and a more free-form editor are coming though 👍

5
回复

@matheusdsantosr_dev Thank you, Matheus. Our very first research prototypes included the pizza place and a gym in Argentina.

Our next features would definitely concern editing and functionality. After all, businesses need custom content and functionality, such as managing bookings, accepting payments, invoicing, and stuff. It all could be integrated in a website, and it could be made better using the same user research methods that we already use.

5
回复

Great concept! Using real reviews from Google Maps instead of template text.

6
回复

@new_user_17102732de thank you, Nick. Would love to see your results.

2
回复

@new_user_17102732de Thank you. That's an idea that could create many startups more: instead of waiting for users to provide information, thinking where to get one.

0
回复

Congrats on the launch, looks amazing!

Some questions:

How are you sourcing the reviews and photos? The official Google Places API caps reviews at 5 per place, so the 1,000-review tier on Agency suggests you're either running your own scraper or using a third-party provider. Curious how you're thinking about long-term resilience here if Google tightens enforcement?

Are the photos in generated sites served via Google's photo endpoint (with your API key) or rehosted on your own infrastructure?

Also:

Looking at the Agency plan for a local agency play and want to make sure I understand the mechanics before committing:

  1. Is "30 websites" 30 hosted sites concurrently, or 30 lifetime generations?

  2. When I use HTML export, do the photos come through as downloaded files or as hotlinks back to Google/your CDN? In other words, if I export a site and host it on my own Vercel, will the images still load a year from now?

  3. Do auto-updates and regeneration work on exported sites, or only on sites hosted by you? (I guess the latter)

  4. If I cancel my subscription, what happens to sites hosted on the agency subdomain. Do they go offline immediately?

Thanks! Trying to figure out whether to position this as recurring (hosted) or one-shot (exported) for my clients.

Anyway, amazing stuff you've built here!

5
回复

@antoniob_dev wow, thanks for the detailed questions, these are exactly the right things to check before committing!

Alright, so:

  • Reviews: We use a third-party provider (Apify) to pull reviews beyond the Places API cap. It's a known tradeoff – we're dependent on a scraping layer. If Google tightens enforcement meaningfully, that's a real risk. We're watching it and have contingency options, but I won't pretend there's zero exposure here.

  • Photos: Rehosted on our own CDN, not served through Google's endpoint. So no API key exposure and no dependency on Google's photo URLs staying stable.

  • 30 websites (Agency): That's 30 active sites in your dashboard at any given time – not lifetime. If you generate a site, export it, and delete it from the dashboard, that slot opens up again next billing cycle. So in practice it's more flexible than a hard cap if you're doing one-shot exports for clients.

  • HTML export + photos: Photos come as hotlinks to our CDN, not as downloaded files. So if you host the exported site on Vercel, the images will load as long as our CDN is up. Worth factoring in if you need fully self-contained exports.

  • Auto-updates: Hosted sites only. Exported HTML is a static snapshot – regeneration won't propagate to it.

  • Cancellation: Hosted sites aren't deleted immediately when you cancel, but we do reserve the right to remove them. We don't have a published grace period yet – if that's a hard requirement for your client contracts, I'd recommend either exporting before cancelling or reaching out and we'll figure something out.

The recurring vs. one-shot question is a good framing. For clients who want a live URL that you can update – hosted makes more sense. For one-off deliverables where the client hosts themselves – export works, just with the CDN dependency on images.

Feel free to Join our Discord if you want to discuss more:
https://discord.gg/uQ97scyNTX

7
回复

@antoniob_dev Hey Antonio, thank you for all the questions.

Scraping the reviews is an industry. There are players like Apify and BrightData to start with.

We do copy the images to our servers. You won't wake up with broken images on your website one day.

For the agency plan:

  1. 30 hosted sites concurrently.

  2. photos come through as downloaded files.

  3. auto-updates only work on sites hosted by us.

  4. We didn't implement it yet (Lean Startup classic move ), but we will give some grace period. Still, the idea is to incentivize our customers to keep there monthly subscription as long as they don't outgrow our features.

Thanks again for making us think with your questions. I don't know if you will choose us, but serious customers speak exactly like you.

4
回复

Tiny details, big difference

5
回复

@eugeny_weiss That's what my ex kept telling me, haha. Thank you for a cheer up.

0
回复

Is the research summary available on its own, outside the page?

4
回复

@daria__andrea not yet. Right now the research is embedded in the one-page site. We’re considering a standalone export (JTBD report / PDF / doc) for people who want to use it directly in marketing – if that’s your use case, what format would you prefer?

4
回复

@daria__andrea This is our next step. Create the research dashboards with multiple sources and live updates.

Awesome idea. Thank you, Daria.

3
回复

Congrats on the launch!

4
回复

@danshipit thank you, Daniil!

3
回复

@danshipit Thank you, that's kind. Appreciate it.

0
回复

Hi Brila team! Congrats on the launch! 🚀

I signed up and tried creating a website for a nearby shopping center, it actually looks quite presentable.

Considering that many local shops and small businesses don’t even have websites (just social media), this is really cool. Thanks for the great idea!

4
回复

@julia_zakharova2 thanks Julia! Yes, that's the point! Would love to see what you got!

3
回复

@julia_zakharova2 Thanks for your warm words and thank you for trying. I wonder if your website for your nearby shopping center will index in Google and appear in the search results.

Maybe we can give websites even to the businesses that don't want it.

2
回复

Such a cool tool! And it's pretty easy to use. Is it possible to add a reservation tab?

4
回复

@novikyysha thank you! Brila usually pulls it automatically if there’s a booking URL on the Google profile, and you can edit the CTA to point to your reservation page (or WhatsApp/phone) in the editor

4
回复

@novikyysha That's the next step: generating the typical functionality tailored to the business needs. So far, the workaround is to use third-party SaaS like OpenTable and customize our action button to lead there.

1
回复

Very clean, easy to get. Congrats!

4
回复

@sergey_mikolaitis thank you, that means a lot.

4
回复

@sergey_mikolaitis thanks (i'll take it as a complement to UI 💅)

2
回复

@sergey_mikolaitis Thank you. That's the very best thing to say to a UX designer.

0
回复

Could work even for businesses that already have a site and just need better messaging

4
回复

@terno totally, that’s a common use case. Even if you already have a website, Brila can pull the “why people choose you” patterns from reviews so you can upgrade your messaging (homepage, bio, ads etc) without guessing

11
回复

@terno That's definitely the next feature or one of the next features. Thank you for highlighting it. Another great idea of yours is to create a report, not necessarily a website.

1
回复

Looks fantastic, can't wait to test!

3
回复

@andrew_b12 How was your test, If you had a chance? Did we get the customer value right?

0
回复

This looks super interesting

Turning real Google Maps reviews into one-page websites is such a smart idea, feels like a fresh take on social proof and local marketing.

Curious to see how far this can go 🚀

3
回复

@mmossa11 thanks! That’s the idea – turn existing social proof into something you can actually share as a site.

We’re starting with one-page because it keeps it grounded and fast, and we’ll keep expanding what we can pull from Google data (menus, booking links, etc.). If you try it on any local business, let me know what it surfaced that you didn’t expect.

2
回复

@mmossa11 My dream is Brila becomes the replacement of Linktree in the social media profiles. Thank you, Michele.

3
回复

Simple concept, real utility ✨

3
回复

@polina_golubeva Thank you. The hardest part indeed was keeping it simple with all the features we are anxious to add.

3
回复

It's awesome Ivan! A simple killing feature but what truly blowed my mind is this about making it based on what actually happens there. Just one challenge for business are starting up, but feel it's another target audience

3
回复

@german_merlo1 Right, we are laser sharp on well-reviewed businesses here. Next step is getting information from most sources, including interviewing owners and studying the competition.

2
回复

This is a neat starting point

3
回复

@crypteed thanks! Our roadmap just got bigger today 😄

1
回复

@crypteed Right. You are right. It's only a starting point, the really minimal MVP. Tomorrow, these comments turn to the backlog.

0
回复

I like the ambition behind it. Many tools claim to increase productivity, but they still rely heavily on manual input.

3
回复

@1mirul Hum

0
回复

@1mirul Good point

0
回复

@1mirul Thanks! That was exactly our thinking. If the owner still has to write all the copy and pick the photos, the AI part isn't doing the heavy lifting. We wanted zero manual input :)

1
回复

Congrats with the launch! Really liked the product, I think small cafés, restaurants without a dev team can really benefit.

3
回复

@ekulianova thank you! Would love to see your examples 👀

4
回复

@ekulianova I hope so. In other words, I don't recall any small cafe or restaurant with a dedicated dev team, so we have a chance, haha.

1
回复

congrats on the launch! Do you plan to add reviews/info from other platforms like Foursquare or similar?

3
回复

@alena_korpula hmm, maybe
@paul_malaj , should we?

3
回复

@alena_korpula Adding more data sources is definitely a priority. Speaking of Foursquare, is it still alive? Which platforms are trending now? TripAdvisor, Booking.com/Airbnb, Yelp, Trustpilot?

0
回复

Can this pick up category-specific language without getting too generic?

2
回复

@artyom_zhuravlev It must be quite good at it. We pick up the language from the customer's reviews, which matches the rule of usability: use the language your users speak.

And we definitely have an allergy toward marketing talk superlatives and vague claims. Foundation LLMs are notoriously leaning toward it, so we've spent months teaching them out of this.

1
回复

Clear positioning from the start! Nice job makers

2
回复

@solodnev I really appreciate your compliment. We founders like to speak about our products in great lengths, listing every possible feature and benefit. It took us months to compress it to the single sentemce with the latest edits done just two days ago.

1
回复

looks useful for SMB. congrats on the launch!

2
回复

@a_6 💛 Appreciated!

0
回复

Congratulations with the launch! Wish you guys good luck with your product!

2
回复

@alina_valyaeva Appreciated. Thank you so much for your kindness.

0
回复

This is THE launch guys! Congrats! 🎉

2
回复

@sutarmin Oh boy, that's the founder's euphoria. Thank you for sharing the moment.

2
回复

congrats on the launch, guys! How do you handle categories where customers care about atmosphere as much as the actual product?

2
回复

@nastassia_k Thanks! Those are actually great for us. We treat atmosphere as a first-class theme when it shows up consistently in reviews, and we translate it into concrete situations and outcomes (e.g., quiet place to work, cozy date night, family-friendly) using the wording customers use, not generic adjectives

1
回复

@nastassia_k We highlight the atmosphere if it's mentioned in the reviews. In fact, this is the majority of the businesses we serve. Places where they know your name, support you throughout the workout, and are located somewhere cool like a forest. We definitely highlight all of this.

1
回复

Hello, is theming/design customization something you plan to do?

2
回复

@antoninkus Definitely. What we have is a pure mvp so far.

3
回复

This feels closer to research than generic AI content generation, which is why it works. Congrats on the launch!

2
回复

@a_hryshchenia thank you! That’s exactly what we’re going for – more "pull patterns from real reviews" than generic AI copy. If you try it on any business, I’d love to hear what insight it surfaced first

3
回复

@a_hryshchenia Absolutely. Nobody needs generated text if it doesn't convey information. The current state of affairs of the generative AI is it didn't generate any fiction that somebody would like to read. Why would website generators create generic AI Lorem ipsum is beyond my understanding.

1
回复
#2
ProdShort
Turn meetings into ready-to-post shorts and posts
596
一句话介绍:ProdShort 是一款通过自动录制并剪辑线上会议内容,将其转化为可直接发布的短视频和社交媒体帖子的工具,解决了创始人及创作者因内容制作耗时费力而无法持续进行“创始人主导营销”和“公开构建”的痛点。
Social Media Meetings Alpha
会议内容转化 短视频自动生成 创始人营销 内容创作效率 AI剪辑 公开构建 社交媒体管理 真实内容 营销自动化 SaaS工具
用户评论摘要:用户普遍认可其解决真实痛点(内容耗时、真实性)。主要问题集中于:如何处理长会议提取亮点、口音或多人交谈的识别准确性、隐私与数据安全、内容是否重组影响真实性、与播客等平台集成可能性。开发者回复积极,强调内容保持原貌、处理快速(5分钟内)及隐私考虑。
AI 锐评

ProdShort 的核心理念“我们不生成内容,我们捕捉内容”是其最犀利的价值主张,它精准刺中了当前AI内容生成领域的普遍软肋——虚假感和过度加工。产品本质上是一个“内容采矿机”,它将用户已有的、高价值的对话(会议)视为富矿,通过自动化剪辑降低开采成本。这并非简单的效率工具,而是一种内容哲学的重塑:它试图将“内容创作”从一项独立任务,还原为工作流程的自然副产品。

然而,其面临的挑战同样深刻。首先,“真实性”在知晓被录制时可能已打折扣,用户评论中“是否会为录制而表演”的质疑直指核心悖论。其次,技术天花板明显,长会议精华提取、复杂音频环境处理是衡量其是否“可用”到“好用”的关键,目前回复略显模糊。最后,其商业模式隐含风险:它高度依赖会议平台生态(如Zoom、Meet),且核心处理的可能是商业敏感信息,数据安全和隐私合规将是不可逾越的红线,绝非“仅作为笔记工具”的轻描淡写所能化解。

它的真正价值或许不在于产出最精良的视频,而在于构建一个“以内容输出为导向”的创始人行动框架。通过降低发布门槛,它可能促使创始人更积极地进行有价值的对外沟通(如社区通话),从而形成“沟通-记录-发布-反馈”的增强回路。如果成功,它售卖的不是剪辑软件,而是一种“持续公开构建”的行为习惯和随之而来的增长可能性。但前提是,它必须跨过技术可靠性与信任关这两道硬门槛。

查看原始信息
ProdShort
Founders fail at content because it's time consuming and AI just still feels fake. Prodshort fixes that. We don’t generate content. We capture it. Everything you say in meetings is already valuable. We cut it, refine it, and turn it into ready-to-post shorts, Linkedin, Twitter... Automatically. No scripts. No fake voice. No overthinking. Just you, turned into content.

I struggled with content creation. Scripting, memorizing, filming, editing. None of it was enjoyable. Especially when it ate into time I needed to build my product and find customers.

But founder-led marketing and building in public are key to brand, sales, and fundraising. I couldn't skip it.

So I started recording calls and turning them into Reels. It worked incredibly well. I went from not posting at all to one Reel a day. The content is authentic, people love it, and I hit a million views with minimal effort posting stuff I actually enjoy, that aligns with my values.

If you're a builder and you want to create content around your niche, join us. Our mission is to help you do exactly that with minimum effort.

Prodshort helps you record calls and transform them into Reels easily. And with the community, we do calls together, improve our workflows, and support each other.

14
回复

@bengeekly How well does Prodshort handle pulling key highlights from longer sales calls (like 45+ mins) to make snappy Reels without losing the genuine vibe?

2
回复

@bengeekly Hi! How does it handle meetings with heavy accents or people talking over each other? Still turns into clean shorts without extra fixes?

3
回复

@bengeekly very cool idea. which types of companies are getting most value of this right now?

0
回复

a hitting a million views by just recording stuff you actually enjoy is the dream. we spend way too much time on production and not enough on the actual product. how long does the 'transformation' into reels usually take with prodshort? @ProdShort @amraniyasser @bengeekly

5
回复

@amraniyasser  @vikramp7470 The million views is not guaranteed yet, but we got 50k views in new accounts, and soon including some viral hacks to grow faster :)The reels are ready in less than 5mins after the call ends.

2
回复

@vikramp7470  production eats way too much time that should go into building 😅
With Prodshort, the transformation usually takes less than 5 minutes, so you can go from call to ready-to-post reel really fast.

2
回复

Hey PH Community 👋


Creating content takes too much time and effort. You need to script, memorize, record, edit, add subtitles, resize…
And most builders simply don’t have time for all that.

Some of the best content (discussions, ideas, team calls, sharing advice...) happens live on calls, and then disappears once the call ends. There’s a lot of valuable content there.

Prodshort records your calls and turns them into ready-to-post content (shorts, LinkedIn, X...). No scripts, no editing. Just real moments turned into content.

Join the community and start creating content. We do calls together and fully support each other.

5
回复

This nails a real problem. I'm a solo founder building a Mac-native video editor, and the hardest part of building in public isn't the building — it's turning the work into content.

The idea that your meetings are already the content is powerful. Most founders overthink content creation when they're already saying valuable things every day.

Quick question: do the generated shorts preserve the natural flow of conversation, or does the AI rearrange segments for better hooks? As someone who works with video daily, that distinction matters a lot for authenticity.

4
回复

@cyberseeds The video is not rearranged, just cut in the right moment. For the Hook, we generate a title that we add. It's really a simple tool to document what you do, not the best edited video ever.

2
回复

@cyberseeds The “meetings are already the content” is the main purpose of Prodshort !! The video keeps the original flow, it’s only trimmed at the right moments .

0
回复

Cant wait to become an Tiktok influencer just by arguing with my developers on zoom)

4
回复

@eugene_chernyak ahhahahahahah. It wouldn't shock me, my first buzz was when I got a bit angry and made spelling mistakes. Social media still love Drama.

2
回复

@eugene_chernyak Hahaha honestly, dev arguments might become the best content category 😄

1
回复
Wow! Such a cool product! How to try it?
4
回复

@dmitry_zakharov_ai Sign up, and add it to your first call. If you don't have with who to chat, we have a community of builders that you can Chat with, and collaborate on the post.
I would love to interview you about Naoma for example :)

3
回复

@dmitry_zakharov_ai Thanks a lot! 🙌 You can sign up and add Prodshort to your first call !!

1
回复

Much needed and useful! But since meetings can be sensitive, how are you handling privacy, consent, and data storage etc?

3
回复

@lak7It should be treated as a note taker and is visible in the call from everyone. Then the content is not shared, we just create it for you and suggest it. You still need to check it and post it yourself.
Of course from our side, we prompt in a way that will suggest content that respect your privacy.

2
回复

So basically, if you create e.g. 120 videos, it will "scan" those videos and will pick from each those top moments and merge them into one video output?

3
回复

@busmark_w_nika It's the opposite way around, you do your Meeting and from every meeting, we scan it, and suggest you 3-5 shorts depending on the Call + Linkedin, Twitter post from what you say. Content is authentic because you got the idea and spoke about it, not the same AI ideas.
In the future we are planning to use memory, and combine content.
Your feedback is valuable as you are in social media, so please roast us

3
回复

@busmark_w_nika Can be very useful for building in public 👀

0
回复

I also don't like to organize content, it looks good and saves a lot of time

2
回复

@yuqingteck Let us know when you try it

0
回复

@yuqingteck Absolutely !! Its save a lot of time, and everything feels natural !!
How many calls a week do you have (average)?

0
回复

nice! i created something similar locally - a massive need!

2
回复

@andrew_uxpin Thank you!! a real need, absolutely !!

1
回复

@andrew_uxpin Oh woow

0
回复

This is really cool! Could this work with podcast recording platforms like Riverside? I'd love to be able to turn the highlights from my long form podcasts into clips for social.

And by the way, how did you make the hero images (in your PH post)? They're really good! Well done 👏

2
回复

@sfoscar We can connect to Google meet, Zoom and Teams we might include other platforms but our focus will always be meetings.

We used Figma for the images! so made by a human designer 🧑‍🎨

2
回复

@sfoscar thank youu

1
回复

This is a great idea! As a founder this has been one of the challenges of trying to keep up with the need to post on Socials. Pulling from existing conversations is so much more honest and natural!

Congrats on the launch!

2
回复

@sarah_andrabi  Thank you, we really want to keep Founder focus on building while Prodshort create authentic content for them

2
回复

@sarah_andrabi Thanks a lot !! Yes, you become the content !!

1
回复
Can I invite ProdShort mid call ? If something interesting come up unexpectedly ?
2
回复

@moussa_toure1 Yes you can 🫡

0
回复

@moussa_toure1 Yes!! just past the link and it join !! Or connect it to your agenda, so you're sure to not miss anything

1
回复

This is exactly the kind of tool I didn't realize I needed! I’ve had so many great moments from calls that simply get lost and forgotten. Quick question—when you record your own calls with it, do you notice yourself speaking differently because you know it could turn into content, or does the conversation still feel natural? I’m curious about how “authenticity” holds up when you’re aware that you’re being recorded. 👀

2
回复

@bacelyyorobi In the majority of the calls we just forget about it. But still sometimes there is some moment where you think. This part was soo interesting but let me repeat it for Prodshort in another way...

1
回复

@bacelyyorobi The first seconds your are like: ''ok, i am recorded..". But once the conversation starts, your quickly forget about it and speak naturallyy !!!

1
回复

I never post content from my meetings because editing takes forever. The auto join on Zoom/Meet is key because I'd forget to record otherwise. Honest question though, Any plans for a lighter tier?

2
回复

@kailesk_khumar The free plan is actually very generous and enough, would you need more than the free plan ? I would be happy to adapt the plan for people that give feedback

1
回复

@kailesk_khumar the auto-join changes everything !!

1
回复

Congrats on the launch! As a builder, the 'mental block' of scripting and filming is usually what kills my consistency so this sounds like a really interesting approach to founder-led marketing and staying in the flow

2
回复

@gayatri_sachdeva  Exactly the problem we are targeting! Thank youuu

1
回复

@gayatri_sachdeva Thanks youu !!! That's what Prodshort solves !!!!

1
回复
You’re a genius! After going to a few podcasts using Riverside, I was hoping someone could build this for zoom or similar. I’m among the founders who feels like I’ll never be able to post content otherwise, cause there’s already all this work for 12+ h/day. I hope your tool would make me closer to my content goals.
2
回复

@maria_sergeeva1 I would love to have a call with you, I used Riverside previously, and appreciate what they do. I built Prodshort because I can't predict in advance if something interesting to share will be shared. And Google meet is just more convenient for everyday calls.

1
回复

@maria_sergeeva1 That’s exactly the problem. Most founders don’t lack ideas to share, they lack time to create content.

1
回复

This is a smart angle. Most founders already say valuable things, it just gets lost.

2
回复

@artem_baygot This is exactly why we built Prodshort. I tried to create content, I found no idea! I asked Chatgpt, at felt like someone else.
I went one day to speak on a Podcast, and found out that I can take 5shorts out of it.
So I decided to transform all my calls into content.

1
回复

@artem_baygot Absolutely !! That's why you cant connect Prodshort to you agenda, and make sure everything is content !!

1
回复

I like the idea here. Not just another AI bot that will send meeting notes, but something that will allow you to promote your product (or service). I'm still a little worried about AI bots in calls but it's becoming more and more common.

I prefer Nextcloud Talk for my meetings (I'm an own cloud sort of person) but I think I could use it a bit with Google Meet to try it out.

2
回复

@houbsta Never heard about Nextcloud Talk, we support Gmeet, Teams and Zoom, and might add others in the future.
Let us know your feedback when you test it

1
回复

curious what the edit step looks like - does it give you one output per meeting or multiple angle cuts? wondering how much manual curation you still need before it's actually postable.

2
回复

@mykola_kondratiuk 5 mins after the end of the call. You have 5 AI suggestions. They are ready to post. But you can change the title, captions...
We also have a simple timeline if you really want to be picky, you watch the video with a higher speed, and select the moment you want. The videos and text post are generated automatically following this step too

2
回复

Definitely a time-saver. I want to post as much content, such as Reels, but I don't want to spend too much time on it. If I were on calls I'd definitely use this tool.

2
回复

@rob_vb I feel you, we built a community with other builders to get on calls together if needed. I'm happy to chat with you :)

1
回复

@rob_vb Join us !!

1
回复

@rob_vb yes, its a big time-saver because editing takes a lot of time too !! and it extremely boring 😂

1
回复

This is super helpful !! I always find excuses to not record content ! Does process videos and recommend clips ? That would be a killer feature.

2
回复

@hamza_boulaala That's exactly what we do, we process them and suggest ready to post clips

2
回复

@hamza_boulaala Yes, no effort. We suggest content reaady to post !!

1
回复

Super cool concept. Is there a way to batch export multiple clips from one long call?

2
回复

@ermakovich_sergey Actually we batch create, multiple clips for you, but you need to export one by one. But we can add this fast.

3
回复

@ermakovich_sergey Thank youu !!

1
回复

huge congratulations on the launch! I genuinely love the content it created for us at Crossnode. It’s been incredibly impressive to see the quality!!! I had a quick question as I continue exploring its capabilities. Would it be possible to turn it on without being in a meeting, so it can record my interactions independently? Specifically, I’m interested in capturing both my screen activity and what I’m saying, even outside of a live meeting setting :))

2
回复

@rania_rimali Stay tuned for what is coming! The next step is not to do a call alone, but Prodshort will be able to interview you! He will ask you questions that will help you generate content and interact with you!
But If you need a human, you will always find people ready to do calls with you in the community group.

1
回复

@rania_rimali Thank youu!!

1
回复

Amazing product ! Best content is usually the one that wasn't intended for social media, can't wait to put it in my brainstorming sessions

2
回复

@gonzaguedb Please do and give me your feedback! Happy to see you here, it reminds me on our first launch together from Station F ❤️

1
回复

@gonzaguedb Thank you !! waiting for your feedback !!

1
回复

I do weekly accountability calls with @bengeekly to stay productive. One day he announced that our calls will also get us content and I loved it.

You just forget about it, until it suggests you some content.

2
回复

@mustaphachqoubi  hahahaha, thank you for your support and all the feedback.

2
回复

@bengeekly  @mustaphachqoubi That why we built Prodshort. Creating content naturally !!

1
回复

Love the demo! 👌🏼

Thought about something like this before, not for corporate stuff but for when indies call each other for example. It's usually always a cool moment you'd like to turn into content!

Congrats with the launch, good luck guys!!! and nice to see @floors.js 😎

2
回复

@vynsedev Ooooh, our main target is actually builders, solo-founders, and small teams. We actually do calls together, and build content from it. Also I try to invite Builders for interviews, and I would be happy to get on a call with you to chat and create content.
Would you add yourself in a directory of indies to collaborate and build content with ?

1
回复

@vynsedev Really appreciate the support 🙌 And yes haha, always nice to have Floors.js around !!

1
回复
Amazing idea! I usually feel very frustrated to not be able to share some great momentum conversations during meetings. Whether it’s demos or internal calls, some situations are 10 times better than every staged video done later, congrats on the launch!
2
回复

@egbennis I know exactly how you feel. That's why I went from recording only some calls with Prodshort to connecting it to my agenda, and having Prodshort in all my calls. I don't create content. I am the content 😂

0
回复

@egbennis Thank youu !! The best moments usually happen live, not in polished re-recordings.

1
回复

I always think “this could be a post” while talking to someone… then forget about it 10 minutes later.

Does it suggest clips by itself or you choose them?

2
回复

@alina_anitei  That's exactly why we built it. Sometimes when Prodshort is not in the call and a moment like that happens, we add it, and redo the moment. It suggest clips by analyzing what is said, but we also made it simple to rewatch fast X2.5 and choose the best moments at once if you need a human in the loop.

2
回复

@alina_anitei so many good moments just disappear after the call 😅
Yes, Prodshort suggests clips automatically, so you don’t have to review everything yourself. You can still adjust or pick your own if you want more control.

3
回复

I do a lot of demo calls, and sometimes I explain things in a way that would make great short content!! Will give it a try !!

2
回复
@rania_rimali please give me your feedback, we still have a long way to make it better
0
回复

@rania_rimali Waiting for your feedback 🤝

1
回复
#3
Offsite
Build teams of humans and agents, watch them work.
462
一句话介绍:Offsite 是一个将人类员工与AI智能体(Agent)整合进实时组织架构图的协同平台,解决了在多AI工具并存的场景下,工作流割裂、协作不透明、缺乏统一管控的痛点。
Web App Artificial Intelligence Alpha
人机协同 智能体编排 组织架构可视化 工作流自动化 多智能体系统 实时协作 AI代理管理 MCP协议 低代码/无代码 人类在环
用户评论摘要:用户反馈积极,认可其将人机协作可视化的创新性。核心关注点集中在:人机指令冲突的解决机制、智能体长时间运行的“漂移”控制、成本管控、与现有开发框架(如AutoGen)的差异对比,以及产品当前对日历/Gmail强制集成的顾虑。
AI 锐评

Offsite 的野心不在于成为又一个智能体编排框架,而在于试图定义下一代人机协作的“操作系统”界面。其核心价值并非技术突破,而是产品哲学上的转向:通过“组织架构图”这一极其传统且人类熟知的管理隐喻,将抽象的、黑盒的多智能体交互,强行拉入一个可视、可理解、可干预的平面。这本质上是一种“降维解释”,用组织管理的逻辑来封装技术复杂性。

它聪明地避开了“重造轮子”的陷阱,选择成为连接既有智能体(如Claude Code)的“协议层”和“控制面板”,这使其生态位更偏向于协同入口而非底层基础设施。其宣称的“人类与智能体节点可互换”的设计原则,是极具前瞻性也极具风险的一步,它试图模糊人机边界,但现实中人类决策的模糊性与AI的确定性之间的鸿沟,绝非一个界面所能弥合。

目前来看,产品通过“审批收件箱”和全链路对话追溯实现的“默认人类在环”模式,是一种务实的妥协,也是当前阶段获取用户信任的关键。然而,这恰恰也暴露了其核心矛盾:当一切行动都需要人工批准时,“观看他们工作”的自动化愿景就大打折扣;若未来放开管制,其宣称的“防漂移”和冲突解决机制能否真正智能化,将是检验其从“可视化管控工具”蜕变为“自主协同系统”的试金石。它的成功,不取决于能连接多少智能体,而取决于能否在“控制”与“自治”之间,找到那个精妙的、可规模化的平衡点。

查看原始信息
Offsite
Offsite is a new paradigm for work: bring your humans and agents into one team. Organize them in a live org chart and watch collaboration unfold in real time. No more agents siloed in tabs or terminals, they work alongside humans, talking and coordinating as a system. See every conversation, approve real-world actions, and run your team with full visibility and control. Out-of-the-box integrations with agents you already use like Claude Code, OpenClaw, and any MCP-compatible agent.

Look, if you want humans and agents to play nice together, they're eventually going to need go on collective Offsites together.

30
回复

Hey Product Hunt! 👋

I’m Stefano, co‑founder of Offsite. This is my first Product Hunt launch and I’m very excited to be sharing this today :)

Offsite is a shared space for hybrid human-agent teams.

Agents are getting really good. But the way we work with them still feels wrong.

Right now, agents live in tabs and terminals. We copy-paste between them and stitch together brittle workflows. They’re not part of our teams, and they don’t work together.

We think the future of work looks different: humans and agents share responsibilities and coordinate like a real organization.

That’s why we’re building Offsite.

How Offsite works:

  • Bring your team Offsite
    Treat Offsite like a place. You bring humans and agents Offsite, and they show up as nodes on an org chart. We integrate with popular agents like Claude Code, OpenClaw, HeyGen, and any MCP‑compatible agent, or you can spin up agents directly in Offsite.

  • Get your team talking to each other
    Once everyone is on the org chart, drag an edge to connect them. Agents immediately start talking and understand how they fit into the team.

  • Watch them work
    Send a message to any agent and watch collaboration unfold in real time. Conversations move across the org chart, and you can click on any edge to see what’s happening. Offsite becomes a living map of how your team operates.

What Offsite handles for you:

  • Coordination
    when an agent joins Agents learn to work together based on how you structure your team, not as isolated tools.

  • Full visibility
    See every conversation, decision, and action, and trace how work flows across your team.

  • Human‑in‑the‑loop by default
    By default, agents can’t take real-world actions without approval. Offsite surfaces the full chain of conversations behind each action so you stay in control.

  • Works where you work
    Talk to agents in Slack, iMessage, Notion, and the tools your team already uses.

  • You don’t need to have every agent
    Offsite lets you quickly spin up new agents with memory, guardrails, and access to 800+ real‑world tools- filling in the gaps wherever your existing agents fall short.

Who is Offsite for?

Founders running lean teams. Operators managing complex workflows. Solopreneurs stitching together a dozen tools. PMs coordinating across teams and systems. Anyone who’s tired of copy‑pasting between agents and wants a real agentic workforce.

P.S. Offsite was built with 30+ agents supporting our 3‑person team ;)


🎁 For the Product Hunt community:

In light of Alpha Day, we’re opening up access to the alpha version of Offsite

Take your agents Offsite at teamoffsite.ai :)

10
回复

@chrismessina this I agree! getting on to planning on next offsite now!

3
回复

@chrismessina clever comment - I see what you were cooking with that - LOL!

3
回复

Hey Product Hunt! 👋

I’m Stefano, co‑founder of Offsite. This is my first Product Hunt launch and I’m very excited to be sharing this today :)

Offsite is a shared space for hybrid human-agent teams.

Agents are getting really good. But the way we work with them still feels wrong.

Right now, agents live in tabs and terminals. We copy-paste between them and stitch together brittle workflows. They’re not part of our teams, and they don’t work together.

We think the future of work looks different: humans and agents share responsibilities and coordinate like a real organization.

That’s why we’re building Offsite.

How Offsite works:

  • Bring your team Offsite
    Treat Offsite like a place. You bring humans and agents Offsite, and they show up as nodes on an org chart. We integrate with popular agents like Claude Code, OpenClaw, HeyGen, and any MCP‑compatible agent, or you can spin up agents directly in Offsite.

  • Get your team talking to each other
    Once everyone is on the org chart, drag an edge to connect them. Agents immediately start talking and understand how they fit into the team.

  • Watch them work
    Send a message to any agent and watch collaboration unfold in real time. Conversations move across the org chart, and you can click on any edge to see what’s happening. Offsite becomes a living map of how your team operates.

What Offsite handles for you:

  • Coordination
    when an agent joins Agents learn to work together based on how you structure your team, not as isolated tools.

  • Full visibility
    See every conversation, decision, and action, and trace how work flows across your team.

  • Human‑in‑the‑loop by default
    By default, agents can’t take real-world actions without approval. Offsite surfaces the full chain of conversations behind each action so you stay in control.

  • Works where you work
    Talk to agents in Slack, iMessage, Notion, and the tools your team already uses.

  • You don’t need to have every agent
    Offsite lets you quickly spin up new agents with memory, guardrails, and access to 800+ real‑world tools- filling in the gaps wherever your existing agents fall short.

Who is Offsite for?

Founders running lean teams. Operators managing complex workflows. Solopreneurs stitching together a dozen tools. PMs coordinating across teams and systems. Anyone who’s tired of copy‑pasting between agents and wants a real agentic workforce.

P.S. Offsite was built with 30+ agents supporting our 3‑person team ;)


🎁 For the Product Hunt community:

In light of Alpha Day, we’re opening up access to the alpha version of Offsite

Take your agents Offsite at teamoffsite.ai :)

13
回复

@stefano_delmanto What's one unexpected workflow breakthrough you've seen from connecting agents like Claude Code and HeyGen in Offsite?

0
回复

@stefano_delmanto  Congrats to the team

0
回复

@stefano_delmanto Hi! If a human and an agent give opposite instructions at the same time, how does it sort the conflict?

3
回复

congrats to the team!!

3
回复

@andrewchen Lets go!! Thanks so much for the support Andrew, we love a16z.

1
回复

@andrewchen Thanks Andrew!!!

0
回复

Huge congrats @stefano_delmanto @naveensharma on shipping this - the live org chart visual is really clever for making agent coordination actually understandable.

3
回复

@naveensharma  @syed_shayanur_rahman Thanks so much! Really appreciate it.

We spent a lot of time on that interface, it forces humans and agents to operate on the same plane, which ended up being a pretty interesting design challenge (even from a backend perspective) for how they communicate.

We put a lot of care into how it feels to create and run these teams, glad it resonated. Hope you enjoy using it 🙂

3
回复

@stefano_delmanto  @naveensharma  @syed_shayanur_rahman  Appreciate it! The org chart was honestly born out of the team's own frustration trying to debug multi-agent runs. Super curious what the team thinks at ConnectMachine about this – and would love to know what visibility gaps you guys are still hitting.

3
回复

Building this has been so much fun. We've seen so much value with the features we've already shipped but there's a lot more on the way. To name a few:

  • Build teams entirely with AI

  • 100+ template organizations

  • Simulation Mode: A/B test different teams against each other

    If you have any more feature ideas you'd like us to add to the roadmap please comment below!

3
回复

looks really cool! but where does offsite draw the line b/w human in the loop and agents going all in?

2
回复

@jesai_tarun  we enable "slow-mode" by default - what that means is that all write actions agents try to take are sent to an inbox first. Humans can review the inbox to see actions awaiting their approval as well as the lineage of agent conversations that led to this decision. This feature is really helpful when you need to diagnose a problem and quickly course correct your org!

0
回复

@jesai_tarun hey!

great question. we have a page called the “inbox” where all the actions agents want to take show up for approval. by default, agents always require human approval before anything actually happens.

you can click into any action and see the full conversation and reasoning that led to it, then approve or deny. if you deny, you can steer them in the right direction based on where things went off.

0
回复

the 'watch them work' bit is where I'm curious. most agent teams I've seen drift after a few hours without human checkpoints. how do you handle mid-session drift or conflicting outputs between agents?

2
回复

@mykola_kondratiuk great question. most agent teams do drift without checkpoints.

today, “watch them work” is less about passive monitoring and more about control + visibility:

  • every action is proposed before it is taken in the real world

  • you see the full lineage of agent/humans conversations that led to this action

  • you approve / deny and steer based on that lineage

So teams run, but nothing commits without you in the loop. that lets you catch drift early and correct it at the source.

We default to that “slow mode” for exactly this reason. Once things are stable, you can relax the guardrails and let parts run more autonomously.

For conflicting outputs, the same idea applies, you can trace where agents diverged and nudge them back into alignment.

Longer term, we’re exploring supervisor-style agents that sit on top, watching for drift and coordination issues in real time, not just quality but how agents are interacting with each other.

3
回复
If you compare Offsite to building a multi-agent workflow in a framework like AutoGen/CrewAI/LangGraph, where do you see the biggest practical advantage today (debuggability, observability, coordination, integrations), and what did you intentionally choose *not* to build yet to keep the product focused?
2
回复

@curiouskitty There are two guiding principles here:

1. at an early stage we set a design principle where every node in an Offsite graph should be interchangeable between a human and an agent. This is not the case with any other multi-agent framework out there. To achieve this, our agent conversations are string-in-string-out: just like the way humans interact! The result is a fully human understandable framework which does not force a world where your agents can only interact with each other. Now that agents and humans can interact in the same plane, everything is a lot more visible.

2. There is no code required to spin up an Offsite team. We put a lot of love into our UX to make human-agent teams as accessible as possible for everyone.

2
回复

@curiouskitty Re. your second question:

Deciding what not to build was one of the hardest parts. It turns out it’s very easy to over-engineer orchestration so it looks great in a demo, but isn't defensible in medium/long term. We went down that path a few times and thankfully course corrected early.

The biggest thing we learned not to build was our own agents / harnesses. It’s tempting because everything works nicely when you control the runtime, but then you realize you’ve basically become an agent builder and need to worry about things like memory, building great coding/finance/sales agents, and a bunch of other pieces that could be companies of their own.

What we focused on building instead is the protocol that lets these siloed systems talk.

3
回复
This might finally make MCP actually usable for non-devs
1
回复

@odeth_negapatan1 Exactly!!! I would even say make agents and frontier AI so much more accessible too.

0
回复

How do you handle cost control when agents start talking to each other continuously?

1
回复

@nuseir_yassin1haha good question. literally the first issue we ran into was agents thanking each other in loops and never stopping.

two things we do now:

  1. behavioral guardrails
    when you plug an agent into Mercury, it learns how to collaborate in a team context, not just respond blindly. that cuts most of the infinite back-and-forth loops early.

  2. hard cost controls
    you can cap token usage per agent. if it crosses the threshold, we pause it and surface it to you. from there you can step in, adjust the prompt, or reconfigure how it interacts with others.

0
回复

Awesome stuff. Great work guys.

1
回复
@yotam_segal thanks Yotam! Glad you liked it
0
回复

sounds like a future that I want to be part of (as user). right now is it built mostly for dev org or the whole company operations?

1
回复
@michael_shang hey Michael, Awesome! Works for all types of orgs. Right now we have some super cool Product (pm/growth/sdr) and also Eng teams (multiple claude codes / devin).
0
回复

Love it. Super cool. I'll get back to you with a feedback shortly.

1
回复
@artinbogdanov Thanks Artin! Please let us know- would love your feedback
0
回复

Looks interesting! Since you support MCP-compatible agents, is there a way to set up custom workflows where one agent's output automatically feeds into another? Like a chain -- researcher finds info, writer drafts something, reviewer checks it. Or does a human need to manually pass things along?

1
回复

@antoninkus Hey Antonin, yes! That's exactly what Mercury is built for. You can set up the chain you described, but it's actually more flexible than a chain. It's a graph. In your example, a researcher feeds output to a writer, an editor, and memory simultaneously. Each agent is specialized, and you decide which ones surface for human approval versus run on their own.

The bigger thing though: these teams are always-on and not run-once pipelines. They're persistent: always responding, always alive.

Let me know if you want me to run through another workflow or if you have more questions!

1
回复

Interesting product, Stefano. The entry barrier is a bit high with obligatory calendar / gmail connection, but overall - looks good and useful!

Congrats!

1
回复

@marcin_uchacz1 Thanks Marcin! Fair point — we made it mandatory in the alpha to show off some real use cases out of the box, but you'll be able to skip it in future versions. Noted. Sign up for the waitlist and I'll make sure you're first in line for the full app (promise we have a skip button)

Also though, would you prefer starting from a blank slate or you have other default integrations in mind?

0
回复

I've been using Claude Code and it's great but completely disconnected from how my team communicates. Having agents show up in the same workspace as humans makes so much more sense than switching between 5 tabs. Do agents share context with each other or are they siloed?  

1
回复

@kailesk_khumar Hey! Awesome to hear you like it :)

Good question. Offsite has a shared memory layer that agents can query, so context isn’t siloed. As agents collaborate, they build on that shared memory, which means the system improves over time instead of resetting every interaction.

Here is a pretty cool picture of the memory one of our teams created!

2
回复
Huge respect for building this with 30+ agents internally… dogfooding at its finest 🚀😃
0
回复

@stefano_delmanto Very cool! Question: if I give your agent access to my Notion workspace, what prevents another user’s agent from indirectly accessing or inferring my data through shared tools or orchestration layers?

0
回复

It is very interesting to present the agent orchestration in the form of visualization, is this product for individuals, or can it be aimed at multiple users in the enterprise

0
回复

Congrats on shipping. The human-in-the-loop default is a really smart move 👍

0
回复

But what happens when one agent hallucinates and misleads others in the chain?

0
回复

This feels like Zapier + org design + LLMs had a baby. Congrats on launching the alpha.

0
回复

Not sure I fully buy the “agents as teammates” framing yet, but I do like the visibility layer

0
回复

lowkey feels like this is what tools like Slack tried to become but for humans only… this is the next step. Congrats!!!

0
回复

@stefano_delmanto Congratulations. And happy product launch.

0
回复

How does Offsite handle documents and attachments? Can it read elements of a large PDF or company SOPs? When Offsite ingests an attachment, does it automatically ingest and upload it to the shared memory graph? I understand that work completed over time grows and expands the graph, but what about the truckload of documentation you may already have and want to instill across your organization?

0
回复
#4
Show Me a Leaderboard
Use friendly competition to build and strengthen community
349
一句话介绍:一款通过定制化排行榜、徽章和论坛等功能,帮助公司、非营利组织和朋友群体轻松发起友好或激烈竞赛,以利用竞争关系构建和增强社区凝聚力的工具。
Games Community Alpha
社区互动 排行榜竞赛 团队建设 用户参与 SaaS工具 游戏化 社群运营 轻量级应用
用户评论摘要:用户认可其利用熟人竞争激励参与的“简单但粘性”核心逻辑。主要反馈集中在UI需优化、功能细节(如并列处理、防作弊、Slack集成)以及适用场景探索(远程团队、家庭、健身社群)。创始人坦诚产品技术门槛不高,定价也基于此。
AI 锐评

“Show Me a Leaderboard”精准切入了一个微小但普适的人性痛点:在熟人圈层中,微不足道的“网络积分”能激发出超乎想象的胜负欲与参与度。其真正价值并非技术壁垒,而在于将“构建竞赛社区”这一行为产品化、傻瓜化,降低了从想法到实践的门槛。

产品定位清醒得近乎“自黑”——创始人承认技术复杂度有限,并以此作为其5美元/年/竞赛的定价依据。这种坦诚反而成为一种信任资产,它明确告知用户:你支付的不是高深代码,而是即刻可用的便利性与时间成本。当前,其核心用户画像清晰指向已有强社交关系的群体(朋友、同事、兴趣俱乐部),用于管理那些自发、琐碎却充满动力的非正式竞赛。

然而,产品的天花板与风险同样明显。首先,其“工具”属性大于“平台”属性,增长严重依赖组织者(Admin)的运营创意与执行力,平台本身对C端参与者的留存能力弱。其次,当竞赛涉及实质奖励或长期运营时,公平性核查、反作弊、动态激励(防止中下游参与者流失)等需求将浮出水面,而产品目前将大部分责任抛回给组织者,这可能成为规模化时的隐患。评论中关于UI粗糙、缺乏预览的反馈,也暴露出其作为标准化产品在用户体验上的短板。

长远看,其发展路径可能有两种:一是坚守利基市场,作为一款极简、廉价的“竞赛创建器”,服务于海量小型、临时性需求;二是逐步深化,通过API、集成、更丰富的游戏化机制(如个人最佳记录、子群组排行)和自动化管理工具,向更严肃的企业团队建设与社群运营场景渗透,但届时将面临更复杂的需求和更激烈的竞争。其成败关键在于,能否在保持极致简单的同时,微妙地平衡组织者的管理负担与参与者的竞赛体验。

查看原始信息
Show Me a Leaderboard
Show Me a Leaderboard helps companies, nonprofits and friend groups easily launch friendly (or intense!) competitions, with custom leaderboards, badges, forums, and notifications.

I started a micro-niche competition website for my friend-group and over the past 6 months it has slowly grown to be a very vibrant community. This was surprising to me!


I now frequently find myself saying "Show me a leaderboard and I will show you an unreasonable amount of time trying to get to the top of it", based on the lengths I saw people go to win my 2025 contest (hence the name). People really love internet points, even more so against their friends! Show Me A Leaderboard allows anyone to host a competition, and gives you the tools to make it fun.

There is not a ton of technical sophistication here, and most PH users can easily vibecode something like this very quickly, so feel free to do that! Our pricing of $5/year (per competition) is reflective of that.

As an example, I made this contest, where you can compete to see who can leave the most comments on PH during launch day :)

7
回复

@catt_marroll Kudos on the launch, one que: have you seen any unexpected group types like remote teams or hobby clubs turn into the most obsessed leaderboard chasers?

0
回复

@catt_marrollCongrats on the launch!! What happens if two people tie for first place or someone quits halfway? Does the leaderboard update smoothly?

1
回复

"5$ because u can code it urself" is the most honest saas pricing in history😅

4
回复

@kostfast glad you appreciate lol! What probably surprises me the most is that people do pay!

1
回复

What's the best way to use it for a Slack community? @catt_marroll

2
回复

@sayanta_ghosh good question. i haven't built a slack integration yet but i can imagine both exposing an API so you can build whatever bots you want or having a slackbot you can add to record entries and post updates around the contest. I'd be happy to build something specific if you have a community that you think can be served with it!

0
回复

Simple idea, but super sticky.
Leaderboards tap into something people never get tired of: competing with friends 😄

1
回复

Congrats on the launch! I did give it a try, I felt UI needs a bit of more work (a bit overwhelming at the moment)

Would love to try it out for my gym buddies community.

1
回复

@porush_puri thanks for the feedback!! I agree the in generally the UI is pretty rough. i've seen some overflows and other things today that are not ideal. will continue polishing for sure! thanks for raising. lmk if i can help at all with you and your friends!

0
回复

Me and my friends are pretty competitive in like the most stupid things.

One thing though, I'm missing a preview of what it would look like on the website. Atleast I can't find it.

1
回复

@rob_vb oops yeah my assets are pretty slim on this launch:

here is a screen shot of a test competition i made for today!

0
回复

Anyone wants to build a leaderboard who will gain more MRR in a month?

1
回复

@igor_martinyuk  yes, this is great use case! i will need to build a stripe API integration so we can verify the entries.

1
回复
How do you handle fairness and anti-cheating in practice (e.g., photo proof, edit history, moderator approvals, rate limits), especially for prizes or longer-running competitions?
1
回复

@curiouskitty This strictly falls on the moderators of the contests themselves. I give contest admin tools to remove entries, makes edits, etc. In generally these are meant to be friendly competitions that are self policed. That said, we have rich input types on the forms -- so if you wanted everyone to upload a photo of their receipt for your 'who is the best super coupon-er' contest, you can do that.

0
回复

such a cool idea man, how do u come with such good ideas, (loved ur last product purposeful poop)

1
回复

@gamifykaran haha thank you, i'm impressed you remember that!

a while a go a friend asked me to help him build a leaderboard for this random event. that sort of grew into it's own site that people really enjoyed using, so I figured maybe it was generalize-able and built this!

1
回复

@gamifykaran i actually built this about two months ago and almost killed it without ever launching it. I was literally in AWS on the server about to terminate it, and decided to let it ride a bit longer. Then somehow, someone found the site, and built a contest. they also paid the 5$ with no faff. seemed like maybe there was something there and saw the 'alpha day' and decided to launch it.

1
回复

I want this for my family. Are there rewards ? How do you confirm stats? ie can participants share proof of what they did

0
回复

Congrats on the launch! Very appropriate with this alpha day leaderboard! what is the most common type of competition people create leaderboards for that you've seen

0
回复

@mukunda_jha mainly fitness challenges! but im hoping people start using it for things that are super esoteric.

0
回复

this is interesting — leaderboards can either be really motivating or really discouraging depending on how they're set up. do you have any mechanics to keep it fun for people who aren't at the top? like personal bests or smaller group boards? i've seen communities where the leaderboard kills engagement for everyone except the top 3.

0
回复

@keith_hiyamojo your leaderboard formula could simple be, whoever has done { } most recently is in the lead. So not all contests necessarily have to be hard to go from last to first.

Beyond that, on my most successful contest we have badges for various tiers of achievement. I.e you got over this bar. We also give people irl stickers based on the tier they got to over the year. I think that helps make it fun either way.

1
回复

How are you keeping engagement going over time, especially once the novelty of the leaderboard wears off?

0
回复

@becky_gaskell that’s up to you :) if you host a really fun contest for your friends they will be engaged. But you know them better than me!

Really I just want to empower you to make a fun place for your community. We have email notifications that event admins can send to their contestants as well.

0
回复

Congrats on the launch! Very appropriate with this alpha day leaderboard! what is the most common type of competition people create leaderboards for that you've seen?

0
回复

@tinyprojects so far, fitness contests seem to be the most dominant. In my friend group we have one related to climbing that is over 1000 entries (we've recorded enough meters to make it 3.5% of the way across the continental US)

0
回复

Its a cool idea, and i personally see it as an team building activity for any business.

May i know if there is any limit on participants right now? I have a team of 220.

What is the most easiest way for me to add those 220 people?

Thanks

0
回复

@arjun_gigledger you would need to pay the 5$ to get onto the paid tier.

if you wanted to remove our branding entirely from the site and just have it look like your own, we can white-label for 100 per year!

0
回复
Congrats on the launch! It’s a cool idea. Can I ask, do you need to be contacts/friends with people to join a contest, or can you freely search and join contests that others are hosting?
0
回复

@leah_dyke good q! There is no public directory right now, but maybe if there was pull for that I would add it.

In generally I think of these as like micro social media sites for your {friends | coworkers | whatever} and so at a minimum I would want a way to keep them private if someone wanted.

You could always make a contest and put a public link to it in a billboard!

1
回复
#5
riffle
An infinite, collaborative playground for music creation
282
一句话介绍:Riffle是一个基于网页的无限协作音乐创作平台,通过简化工具、集成AI辅助和实时协作功能,解决了非专业音乐人在传统数字音频工作站(DAW)面前因操作复杂而难以将创意落地的痛点。
Web App Music Alpha
在线音乐创作 实时协作 AI辅助创作 低门槛音乐工具 网页DAW 创意协作平台 音乐社交 创作者友好 反AI同质化 流状态创作
用户评论摘要:用户普遍赞赏其易用性、协作乐趣和“Figma for music”的体验。反馈问题包括:播放延迟、新手术语(如“bars”)理解困难、需加强引导。创始人积极回应,承诺优化性能、增加新手引导和评论等功能。
AI 锐评

Riffle的野心不在于颠覆专业DAW,而在于重构音乐创作的入口逻辑。它精准刺中了当前创作工具的两大悖论:一是专业DAW功能过剩形成的“驾驶舱恐惧”,将感性创作异化为工程学习;二是文本生成式AI音乐走向另一个极端,用统计平均抹杀了创作中的人格与特异性。

产品将“协作”与“AI辅助”定位为“游乐场”的双引擎,是明智的差异化。实时协作借鉴了Figma等设计工具的成功范式,将音乐创作从私人工作室拉入共享画布,契合了音乐固有的社交与即兴属性。其宣称的“AI副厨”角色更具洞察力——AI不作为主导的内容生成器,而是隐于后台的分析、诊断与建议工具,旨在维持用户的“心流状态”。这试图在“全手动”的复杂与“全自动”的平庸间,开辟一条“增强创作”的中间路径。

然而,其挑战同样清晰。首先,体验的“轻量化”与创作的“深度”之间存在天然张力。当用户越过新手阶段,产生更精细的混音、编曲需求时,平台能否提供足够的进阶能力而不重蹈复杂覆辙?其次,“副厨”AI的实际效能与智能边界将是关键。它能否真正理解音乐情感意图,提供不打断灵感的精准建议,而非沦为鸡肋?最后,其商业模式与生态构建尚未提及。如何汇聚优质音源、样本,并形成可持续的创作者经济,将是其从有趣玩具成长为必备工具的关键。

Riffle的价值,在于它试图将音乐创作的工具理性重新让位于人本价值。它不是又一个功能堆砌或AI炫技的产品,而是一次对创作本质的回归实验:让人与人、人与灵感更直接地碰撞。成功与否,取决于它能否在“简单易用”与“专业深度”、“AI赋能”与“作者主权”之间,找到那个精妙的、动态的平衡点。

查看原始信息
riffle
Riffle is an infinite, collaborative ecosystem for music creation, where every idea has the space and support it needs to find its shape. Cook up a riff, add your friends and collaborators to it, and build it out with sample packs, instruments, audio, and some help with the resident sous chef who can create, analyze, critique, and guide you. Go make some noise.

‘sup. i’m deo - one of the founders of riffle.

i’ve been making music my whole life and i’m telling you man, we’ve lost the plot.

me and my co-founder suffered for years under the tyranny of tools built by engineers for engineers, not for the kid who plays three instruments by ear and freezes the second he opens a DAW, not for the singer with a hundred melodies in her head and zero finished songs, not for any of us who just had music in us and wanted it out.

the problem nobody solved

there has never been a consumer-grade music creation tool built for people who are actually musical. DAWs are powerful, sure, but they hand you a cockpit when all you wanted was to play. and then text-to-music AI companies show up and go even further the wrong direction and take the wheel completely. from a text prompt they generate statistically average songs trained on billions of hours of human expression that contains exactly zero percent of you or your weird taste, your specific sadness, or your particular joy - the irreplaceable things.

we’re anti-slop. we believe in authorship. we believe music is the rawest, most ancient, most communal act of human expression. it’s always lived in people first and tools second, and somewhere in the last few decades that got inverted. we just want to flip it back.

riffle is the playground we always needed

riffle is a playground. an ecosystem for music creation on the web - sounds, samples, instruments, simple tools, real-time collaboration, and the right amount of AI acting as a sous-chef in the background - it's brilliant and present and knows exactly when to step in and when to disappear - so that you can stay in flow state, that gorgeous messy magical state where the idea is still hot and alive and you’re not stopping to learn something, you’re just making.

this is early. genuinely, honestly, gloriously early. bugs exist, there are missing pieces, stuff we haven’t figured out yet. but it’s the first version of something we’ve genuinely needed for a long time. so use it. break it. send it to a musical friend who's sitting on a hundred ideas.

go play today: https://app.riffle.studio/

27
回复
0
回复

@deoeven let's go!

5
回复
@deoeven so good to see this
2
回复

yooo, the other founder here.

building riffle has been quite the journey. like @deoeven mentioned, we wouldn't be doing this if we weren't solving our own problems in creating, sharing, and collaborating with others.

if any of y'all wants to make some sick beats together, comment/dm! can't wait to see what y'all make.

13
回复

@deoeven  @an5rag been using riffle for the past hour. ITS AWESOME GUYS

4
回复

I love music and I play guitar myself. It's fun to come up with new stuff, but you made it even more fun to collaborate with others. Creating music together is 10x better.

13
回复

@rob_vb come let's make a board together!

6
回复
@an5rag I’ll join too!!
2
回复

we're launching more features as we speak!

  • figma-like comments on boards

  • sous chef should be able to be able to diagnose musical/mixing errors on your tracks

  • you'll be able to merge stacks vertically

  • an onboarding experience

6
回复

this is so sick, ive watched so many beat making videos and this is the first time it felt doable myself, so excited for more!

3
回复

@vamsi_vadlamani ayeee love it. share your board w me, would love to listen! anurag@riffle.studio

1
回复

I absolutely love this as someone who has slowly been getting into music creation myself

I love how accessible the whole app is. It feels like Figma but for music creation, and I love that!

The only thing that I had an issue with was that there seems to be a bit of a lag whenever I add an instrument to the space in terms of the playback speed. But other than that, this app seems very solid. I really love the experience, everything down to the landing page. It's truly an amazingly immersive experience.

3
回复

@itskarelleh thanks for the praise @itskarelleh! We're working on performance on the daily - will def try to look into your session to spot what was up. Please keep the feedback coming :)

0
回复

Am a fan of the seventy’s music scene—now looking to create some of that myself. The first attempt itself was super cool.

3
回复

@samir_deokuliar love that!

1
回复

Wow riffle, I love music! This app is amazing i am super novice about music , I love music but I never learned how to make music with AI tools. There was AI chatbot how to make each stack connected to one another, but it was hard to understand. If there is more specific guideline or music words that I have to know before making then it will be more better! I don't know even what is 'bars' is, so okay I was like 4bars hmm, what is different between 2bars, Auto, 8bars etc. However it was fun and fresh experience how to play with music for super beginners in music! Great work!

2
回复

@jihwankim55 made our day Jihwan! We're making a bunch of onboarding experiences + help sections for exactly this. Keep an eye out and continue to make music!

1
回复

Making music has always been a solo thing for me. The idea of jamming in a browser with friends in real time is genuinely exciting. Congrats.

1
回复

@kailesk_khumar thanks man. did you manage to make something?

0
回复
#6
Grass
Gives your coding agent a dedicated VM that's ready 24/7
267
一句话介绍:为AI编程助手提供一个24/7待命的专属云端虚拟机,让开发者能从手机等设备随时随地、无间断地异步协同和监控编码任务,解决了跨设备工作流中断和本地资源消耗的痛点。
Developer Tools Artificial Intelligence Alpha
AI编程助手 云端开发环境 异步协作 移动编程 开发者工具 虚拟机即服务 BYOK架构 无信用卡试用 多代理支持 工作流连续性
用户评论摘要:用户普遍认可跨设备异步协同的核心价值,并对BYOK架构和免费试用表示赞赏。主要问题集中于会话连续性、VM规格与计费、文件传输、Git集成等具体实现细节,并探讨了产品未来是偏向执行层还是协作层。
AI 锐评

Grass的野心不在于提供一个更强大的VM,而在于试图重新定义开发者与AI编程助手的关系。它将AI助手从“需要手动操作的工具”定位为“可异步协作的同事”,其真正价值是构建了一个持久化的“数字同事”工作空间。

产品巧妙地用“10小时免费VM”作为钩子,但核心卖点是“工作流连续性”这一体验层创新。它瞄准了开发者灵感与工作场景流动化的痛点——在通勤、休息时突然想继续或检查编码任务。然而,其当前方案存在内在矛盾:宣传“无缝切换”,但官方回复承认桌面与云端VM目前仍是独立环境,会话无法自动继承,“同步”功能尚在开发中。这暴露了其MVP状态与宏大愿景之间的差距。

安全上,BYOK架构是明智的信任基石,符合开发者心理。但作为“执行层”,其长期挑战在于如何平衡控制的粒度与流畅性。评论中关于“审批触发机制”和“防止代理停滞”的问答,已触及到核心矛盾:过于频繁的审批会打断流程,而过于宽松则可能引发意外后果。未来竞争力可能取决于其风险感知与自动化策略的精细度。

从生态看,其“代理无关”的定位和快速集成计划是正确方向,但需警惕成为单纯的中继管道。用户将其类比为“Slack for AI agents”的评论点明了潜在演进路径:从执行层生长出协作层,形成基于共享上下文的团队工作流。这或许是比单纯提供VM更大的想象空间。

总之,Grass在正确的时间点切入了一个敏锐的痛点,其理念领先于当前实现。成功与否取决于能否稳健地弥合“无缝体验”的承诺与技术现实之间的鸿沟,并在执行控制与流程自动化中找到最佳平衡点。

查看原始信息
Grass
Grass gives your coding agent a dedicated VM that's always ready. No setup, no config, no burning your laptop. Point Claude Code or OpenCode at it and run. Monitor progress from your phone, steer mid-session, push changes, all without touching your machine. Every new account gets 10 hours free. No credit card needed.

Hey PH!

We built Grass because we noticed something weird. We message our teammates from anywhere, on the train, at lunch, from the couch. But the moment we want to talk to our coding agent, we need a laptop and a terminal open.

That felt broken. Coding agents aren't tools you operate anymore. They're colleagues you work with. Grass is how you stay in touch with them.

What Grass does today:


→Thread continuity across your phone and laptop. Start a task on Claude Code or OpenCode on your machine, pick up the same conversation on your phone. Same context, nothing lost.
→ Free pre-configured VM. We sponsor 10 hours of Daytona compute. No credit card, no DevOps setup. Your agent has somewhere to work in under a minute.

→Bring your own API key. We never see it, never store it. Your keys stay on your device.

→Agent agnostic. Works with Claude Code and OpenCode today. More agents coming.

On security: Grass runs a BYOK architecture. Your API key never touches our servers. We're building for developers who care about this, because we're developers who care about this.

Why we made it free to start: Every developer running coding agents should be able to try cloud compute without a credit card form in the way. 10 hours is enough to have your first "my agent finished while I was away" moment. After that, you'll know if Grass is for you.

A bit about us: Raunaq previously built Elemential (enterprise infra, shipped to NSE) and has trained 3,000+ developers on AI agent infrastructure. Anil built the core architecture, real time sync, SSE-based event buffering for mobile reliability, and Daytona VM orchestration. I lead design and creative, everything around how Grass shows up in the world.

We'd love your feedback, especially on what agents you want us to support next and what your ideal mobile coding workflow looks like. We're in the comments all day.

9
回复

@sunnyjoshi As someone building projects on the go, what's the top agent feature request you'd prioritize next for mobile steering, like mid-task tweaks or multi-agent handoffs?

0
回复

@sunnyjoshi Hi. Does the VM stay ready 24/7 even if I close the app or switch devices? Any downtime?

1
回复

One of the coolest launch today for sure! Do you see Grass evolving into something like Slack for AI agents or more of an execution layer behind the scenes?

3
回复

@lak7 Appreciate it! Grass is more of an execution layer now. Agents actually run, maintain context, and interact with real codebases.

Once you have persistent agents working in shared environments, a collaboration layer naturally emerges. Threads sharing, team workflows, etc. So it could look a bit like Slack for agents over time, but grounded in real execution rather than just messaging.

1
回复

Very cool, does this mean I can finally touch grass? 😄

Jokes aside, how are you thinking about session continuity and memory when there’s a disconnect or the user switches devices?

3
回复

@jon_dalgir Haha, that’s the goal 😄

Right now, your local machine (tethered) and the cloud VM are treated as separate environments, so sessions don’t automatically carry over between them.

We’re working on ‘Grass Sync’ next, which will persist both the codebase snapshot and agent threads, so you can switch devices or reconnect without losing context. That’ll also open up sharing and collaboration across teammates.

2
回复

Pretty cool launch guys! How does this differ than claude code remote control? Is it the fact that it's part of a hosted VM instead?

3
回复

@aryanranderiya Thanks! Yeah, it's part of a hosted VM. Grass is a persistent hosted workspace. Your agents run in a sandbox that stays alive, so you can jump in from your phone anytime (no laptop needed).
It’s multi-agent Claude Code, OpenCode today. Adding Codex, pi next. Which ones would you want to try?

1
回复

honestly the VM angle is secondary for me. the real unlock is async handoffs - start on desktop, check in from phone. I already do this mentally, I just hate the context switching to do it.

2
回复

@mykola_kondratiuk totally! that's a pain point we wanted to solve for ourselves too. The reason we're excited about the VM is that sometimes when the lid is shut and inspiration strikes, it's a real life saver :-D I'm curious, do you find yourself reviewing threads more than the code itself these days?

0
回复

Congrats on the launch @sunnyjoshi + team! Looking forward to trying this. Any hints as when the App Store version is shipping?

2
回复

@gabe Thanks! The App Store version is currently under review, we’ll share the link as soon as it’s approved.

We’re opening up TestFlight and the PWA version over the weekend. The GitHub repo is already live if you want to try it today.

1
回复

Interesting, how does it connect to the VM from iPhone? does it ssh or just a message relay?

2
回复

@sayuj_suresh It’s a message relay. The Grass server runs the session and handles communication between your phone and the VM no direct SSH from the iPhone.

2
回复

The BYOK architecture is the detail that matters most to me. I've avoided cloud agent tools specifically because I didn't want my API key sitting on someone's server. Good to see this addressed upfront rather than buried in the docs.

1
回复

@jay_morzaria This is exactly why we built it that way. Your key, your model access, your bill. We never see it, never store it. Felt like the only honest way to build something in this space.

0
回复

Congratulations on the launch. This looks like something I’d use. I use my agents from different places and it’d be cool to keep on developing from my mobile for example.

1
回复

@rob_vb Thanks Rob! That's exactly the use case. Pick up where you left off, from your phone, without losing any context. Good luck with @brag.fast today too.

1
回复

Hello!

Does this work if I'm not on wifi? Like can I actually check in on my agent from anywhere?

1
回复

@shubham_mandge Yep, works over mobile data too!! The VM runs on our end so your phone just needs any internet connection. No laptop, no wifi dependency

0
回复

Okay the 10 free hours with no credit card is such a smart way to get people to actually try this. Most tools gate everything.

1
回复

@archita_sindu That's exactly the thinking. If someone has to pull out their card before they've had the single 'wow moment' moment, we've already lost them.

1
回复
How does your tool-execution approval flow work end-to-end in practice—what exactly triggers an approval, what context does the user see (command, diff, risk signals), and how do you prevent “agent stalls” when someone is away?
1
回复

@curiouskitty Great question. We gate execution at the tool level. Anything that mutates state (file writes, shell commands, installs, etc.) triggers an approval.

When that happens, we show the exact command/diff, along with relevant context (what the agent is trying to do and why). We’re also starting to layer in simple risk signals (e.g. destructive commands, wide file changes) to help users make quicker decisions.

To avoid stalls, we support session persistence + async approvals. So you can approve from your phone, or set scoped auto-approvals for low-risk actions. We’re also exploring fallback behaviors (like safe retries or partial execution) when a user is away.

1
回复

Hi, I'm an OpenClaw user and it looks like a very convenient version of OpenClaw to me.

BTW how can I transfer files to and from the VM?

0
回复

Cool idea but whats the plan when a session just keeps going and burns through hours? Some kind of cap would be nice. Also what specs do the VMs have, Claude Code gets pretty hungry on larger projects ...

0
回复

The "no burning your laptop" part sold me haha. Being able to just point Claude Code at a remote VM and watch it work from my phone sounds like the dream setup. How does the git integration work -- does it push directly to my repo or do I review a PR first?

0
回复

The environment setup tax on coding agents is real. I waste so much time getting the right dependencies installed before the agent can actually do anything. How fast is the cold start?

0
回复

Running a local coding agent usually ends up chewing through all my RAM and crashing my active dev environment. Spinning up a persistent VM specifically for this is a brilliant way to handle long-running background refactors. I would love to know if you offer pre-configured images for different agent frameworks out of the box.

0
回复

I love the idea of having a dedicated VM to do work and maintain context. This sounds like having the claude code app, but running 24x7. What kind of VM is being generated and persisted in the background (i.e. EC2s, docker container etc?)

Best of luck on your launch day, I'm running mine as well! I'm using claude and will give this a try.

0
回复
#7
Morsel
Strava for cooking
216
一句话介绍:Morsel是一款烹饪社交应用,通过让用户关注好友、分享烹饪成果,解决了人们在日常饮食中缺乏灵感、不知做什么菜的痛点,构建了一个基于真实社交关系的食谱发现场景。
Cooking Social Networking Alpha
社交烹饪 食谱分享 美食社区 生活灵感 好友动态 烹饪记录 食谱发现 兴趣社交 生活方式应用
用户评论摘要:用户反馈积极,认可其社交灵感价值。主要问题集中在:1. 核心功能是分享还是像Strava一样追踪数据?2. 如何通过游戏化(如排行榜、挑战、投票)维持长期活跃度?3. 技术问题(如食谱页面加载慢)。建议包括增加营养统计、月度挑战、好友投票竞争等功能。
AI 锐评

Morsel精准地捕捉到了一个细分但普适的需求:在信息过载的时代,我们更信任熟人网络的真实推荐。其“Strava for cooking”或“Letterboxd for food”的定位,本质上是将已验证成功的“兴趣垂直+社交图谱”模式迁移到烹饪领域,这比泛美食社区更具粘性潜力。

然而,其面临的挑战远大于运动或电影赛道。烹饪的高门槛(耗时、耗材、需技能)与记录的低频性,是它无法像记录一次跑步或标记一部电影那样轻松跨越的鸿沟。评论中反复提及的“如何维持活跃度”直指核心矛盾。目前依赖的“排行榜”机制略显单薄,可能只激励少数核心用户,却对大多数普通用户形成压力而非动力。

产品的真正价值不在于成为另一个食谱数据库,而在于构建一个“烹饪行为社交网络”。它记录的不是完美的摆盘,而是好友今晚真实的餐桌。这种真实性带来的信任感、陪伴感和轻度炫耀欲,是其护城河。开发者回复中透露的“将食谱与用户成品关联”的思路是正确的——它让静态食谱因社交互动而鲜活。

未来成败关键在于:能否设计出贴合烹饪行为本身、而非生搬硬套的游戏化体系(如基于食材的挑战、合作宴客活动);以及能否将“记录”动作简化到极致(如语音输入、图片自动识别食材)。若仅停留在“分享美好瞬间”,它可能沦为另一个小众秀场;若能深入解构“烹饪”这一行为,并将其数据化、游戏化、社交化,它才有机会成为厨房里的“数字灶神”。

查看原始信息
Morsel
Morsel is the social networking app for cooking. Follow your friends, see what they are making, get inspired!
Hey folks, thanks so much for checking this out. Jack and I made Morsel over this past holiday season while we were with our families cooking meals. I was using Letterboxd to find a movie for my family to watch, and I thought that we should have a similar app to see what recipes my friends were making. It's just been some close friends using it for a while as we worked on our main business, but we decided to post it out to the world today. We'd love for you to try it out and we'd welcome any feedback for what you'd like to see in an app like this. Our hope is that this app might inspire all of us to cook more!
7
回复

@blacob Hi. Does it track my cooking like Strava tracks runs, or is it more just for sharing recipes?

1
回复

@blacob Congrats on the launch!
Does the app also track nutrition stats?

0
回复

Interesting, I love to cook and I'm always sharing recipes with friends and family.

I see some people sharing their recipes on Instagram, but good to see an app that just focuses on this.

3
回复

The Letterboxd comparison immediately makes this make sense. Does the feed show the recipe itself or just that a friend made something? Curious whether it's more of a "what are people cooking" discovery layer or closer to a shared cookbook. Nice job !

2
回复

@ikalimullin Thanks! The feed is targeted towards "what are people cooking", and then we have an explore page with recipes that works as a shared cookbook! We tie the meals with the recipes that people used to make them and then for different recipes we show how it turned out for your friends and other users.

0
回复

really like the "strava for cooking" framing. curious how you handle the motivation side — do people actually keep logging meals after the first week or does it drop off? with running apps the streaks and stats are what keep people coming back, wondering if you've found something similar works for cooking.

2
回复

@keith_hiyamojo We have been testing out some different ways to keep it fun, interesting, and exciting to come back! The leaderboard was the first thought, but streaks and shared weekly recipes for everyone to share will be coming soon!

0
回复

I always struggle to figure out why to cook and either end up delivering or standing in the middle of whole foods wandering around until something inspires me. I’ve been a huge fan of morsel since the beginning- seeing what people are cooking has helped inspire many of my dinners every week

2
回复

@jeffrey_tsaw Glad to hear :) Thats exactly what were aiming for!

0
回复

Looks super fun! Kind of the same vibes as Belli also a bit, excited to try this out.

2
回复

@krishnam_goel Belli was an inspo! I wanted the same kind of experience but couldn't afford eating out that often!

0
回复

This looks like a fun app for families or a friend-group. A potential future feature could be to have weekly/monthly challenge to use different ingredients or to try different cooking styles. Everyone likes a little competition!

1
回复

can you add voting so me and my friends can compete to be the best chef? morsel is awesome, loving it!

1
回复

@brendan_ashworth Chef of the week is coming!

0
回复

I forgot to say, follow me on morsel! https://morselapp.fun/app/cob

1
回复

I love the sense of community kitchen cooking, I can see what my friends are making with some of the same ingredients I have. Sometimes I love to show off some of the most inventive meals i make while working in the kitchen. There's only so much you can do with grilled chicken breast but when you combine it with some wild combinations you end up with some amazing dishes, that I can save and share with members of my own cooking community. Great flex for those secrect recipes that everyone asks about.

1
回复

Hello, looks nice, is there any gamification model to encourage people to share on regular basis?

1
回复

@antoninkus right now, we have a leaderboard for both your friends, and everyone on the app, for who has shared the most over all time. We've heard rumors of little rivalries emerging between some of our friends over this leaderboard. We have some ideas to make it even more game-like. Is there anything you'd like to see in that regard?

0
回复

very cool! I appreciate that you included a leaderboard mechanic!

I hate recipes primarily because of the insatiable ad slop, so whenever someone sends me a recipe that we like, we hand-write it down. maybe having a directory within the app of the heavy hitters that people like and a recipe would be cool. I do think the single best source of good recipes is people you know directly.

1
回复

also not sure if just server load, but the recipes page in the app feels very slow / broken maybe? when i try to view recipes from morsel users at the bottom of the page, im not able to click into any of them.

1
回复

That’s fun—totally hooked me, even though I can’t cook at all.

1
回复

How are you encouraging people to keep sharing regularly, rather than it becoming something they use once and forget?

1
回复

@becky_gaskell we have a leaderboard, which we know encourages some people to post. We have some notifications, though we really don't want to be annoying. I think more games, like the leaderboard, is probably the way to make the app fun enough that folks just naturally tend to return

0
回复

Congrats on the launch! When you post a meal, does it break down the recipe into ingredients / nutrition / steps to create? would be cool to explore other peoples meals and know how to actually create them & learn new things.

1
回复

loved the idea, is it limited to my network or i can explore other people near me or something else. as i recently started cooking so i love the idea :)

1
回复

@gamifykaran  encourage a friend to join with you! You can share a direct link to your profile via the person icon tab in the app.

Or for now, check out the "everyone" section of the leaderboard for super active people to follow.

1
回复

been looking for something like this actually. I take pics of everything I cook but never do anything with them. Can you add ingredients or a quick recipe to posts or is it photos only for now?

0
回复

I cook almost every day but never share it. Something casual and social just for food could actually get me posting.

0
回复
#8
Onform.work
Build forms with Claude
212
一句话介绍:Onform是一款MCP原生的对话式表单构建工具,允许用户直接在Claude、Cursor等AI助手或兼容工具中通过自然语言创建、管理表单并收集数据,解决了用户在传统拖拽式表单构建器中频繁切换上下文、操作繁琐的核心痛点。
Productivity Marketing Alpha
对话式表单构建 MCP原生应用 AI生产力工具 SaaS替代方案 自然语言交互 低代码平台 团队协作 数据收集与管理 内部工具开发 成本优化
用户评论摘要:用户普遍认可其对话式构建表单的理念和MCP集成带来的流畅体验。主要问题聚焦于:通过自然语言处理复杂条件逻辑的能力目前有限;关心与Typeform等产品的功能对比;询问团队协作方式和学习曲线。创始人回应了定价优势和发展路线。
AI 锐评

Onform的价值核心并非“又一个表单工具”,而是作为“AI智能体与真实业务系统的连接器”。它敏锐地抓住了AI助手(如Claude)能力溢出的趋势——当聊天界面成为新的生产力入口,如何让其直接操作复杂业务对象?Onform将表单这一最高频、结构化的数据收集场景,变成了AI可理解、可操作的“技能”。

其真正颠覆性在于工作流的重构。传统表单构建是“设计-配置-发布”的线性过程,需要用户具备界面逻辑映射能力。而Onform将其转化为“描述-对话-迭代”的协同过程,将构建心智负担转移给了AI。这看似是交互方式的改变,实则是开发范式的迁移,与“vibe-code”理念一脉相承,即用意图而非指令来生成应用。

然而,其面临的挑战同样尖锐。评论中反复提及的“复杂条件逻辑”问题,恰恰暴露了当前自然语言处理结构化业务规则的边界。表单逻辑的严谨性与自然语言的模糊性之间存在天然张力。产品目前采取的折中方案——简单逻辑用对话,复杂逻辑用仪表盘——可能成为体验断点,削弱其“完全对话式”的宣言。

此外,其作为“SaaS替代平台”一部分的定位,揭示了更大的野心:以对话式开发为楔子,切入企业内部工具市场,用可拥有的软件替代租赁的SaaS。这一定位使其直接对标的是高昂的垂直SaaS和低代码平台,其长期竞争力将取决于模板生态的丰富度与“自然语言到复杂应用”的编译可靠性。若成功,它开启的将不是一个新表单时代,而是一个“对话即开发”的新范式。

查看原始信息
Onform.work
Onform makes form creation, data collection, and management fully conversational. It's MCP-native so you can build and manage forms directly from Claude, Cursor, or any MCP-compatible tool using plain language. Build forms through natural language via MCP, or use the dashboard if you prefer. Onform is built by Founding Dev, an AI-powered SaaS replacement platform helping teams vibe-code complex internal software from customizable templates — cutting build time and maintenance headaches.

Hey Product Hunt! 👋

Talha here, Founder of Founding Dev.

With Numan Shaikh - @numan_shaikh2 taking full ownership and lead, we built Onform because form tools haven't really changed in years. You open a UI, drag fields, configure logic, repeat. We wanted to see what happens when you just... talk to your forms instead.

Onform is MCP-native from day one. Create forms, add fields, and manage submissions directly from Claude or Cursor using plain language. No clicking around a dashboard unless you want to.

Onform is part of Founding.dev - An AI-Powered SaaS replacement platform helping internal teams build highly customizable complex software and replacing expensive SaaS subscriptions without maintenance headache's or long build cycles.

We're just getting started and would love your feedback — especially from anyone already building with MCP. What would make this a must-have in your stack?

7
回复

@numan_shaikh2  @masoodtalha7 Hi. Building forms with Claude, does it handle complex logic like conditional fields well?

1
回复

@numan_shaikh2  @masoodtalha7 How does this compare to Typeform or Tally in terms of logic complexity?

0
回复

@numan_shaikh2  @masoodtalha7 How does its MCP-native approach work with tools like Claude, Cursor, or other MCP-compatible platforms? In what ways is it more flexible and efficient than traditional form builders or spreadsheets?

0
回复

Can multiple team members collaborate via prompts or is it single-threaded? Congrats on launching!

1
回复

@himani_sah1 This is an interesting idea. Do you have any use cases in mind for this? What are some of the scenarios where multiple team members would want to colloborate?

0
回复

What’s the learning curve like? Do users need to know specific prompt formats?

1
回复

@zerotox Thanks for the question. Curious, what do you have in mind. What use cases are you trying to target here?

0
回复

@zerotox No need for specific prompts, you can talk to claude in natural language for getting things done on Onform.

0
回复

Congrats on the launch!

1
回复

@danshipit Thank you! We're on a mission to help companies replace expensive and bloated SaaS with the tools they own and control

0
回复

Building forms inside Claude instead of switching to a separate tool makes a lot of sense. The context switch is what kills my flow every time.

1
回复

@kailesk_khumar Exactly! That was the point of it all.

0
回复

You have a really rich portfolio of templates! :) Like it!

1
回复

@busmark_w_nika Thanks Nika!!! And thank you always for your support.

0
回复

Many congrats @samuel_taiwo1 @muhammad_ans_khan @aima on shipping this. I'm curious about the MCP integration - does it handle complex conditional logic well when you're just describing it in natural language to Claude?

1
回复

@syed_shayanur_rahman As of now the claude mcp connection can handle building simple form without condition but we can add it to handle complex conditional logic.

0
回复

I love the idea of building forms through Claude and Cursor. Moving away from drag-and-drop UIs to a conversational, MCP-native workflow feels like a huge productivity win. Awesome Product!

1
回复

@samuel_taiwo1 Yes absolutely agree! Onform provides connects seamlessly with your favorite AI chat interfaces.

1
回复

Hey Product Hunt 👋 Numan here, I led the build on OnForm.

Honest story: I didn't set out to build a form tool. At Founding Dev our mission is to help companies replace expensive SaaS with software they actually own. We'd already shipped templates for DocuSign, Calendly and others. Forms were the obvious next gap.

Typeform and Jotform both start at $39/month, and that's just to get through the door. Webhooks, Google Sheets sync, unlimited responses, custom branding? That's another tier up, another bill.

OnForm starts at $12/month with all of that included. Teams pay $29/month. No tiers designed to nudge you up, no features held hostage.

Your core tools shouldn't be rentals. You should own them.

Would love to know what you're replacing, and what we should build next 🙌

1
回复

@numan_shaikh2 Love your story and thanks for being such a great part of the team

0
回复
This might make traditional form builders feel ancient. :D
0
回复

@priyankamandal We realy feel bad for them :)

0
回复

Can it handle conditional logic well? Like multi-branch workflows?

0
回复

@nuseir_yassin1 Curious to know what workflows do you have in mind?

0
回复

@nuseir_yassin1 If you go through UI yes we have conditional logic and multi branch workflow but with MCP you can build forms without logic but we can add those soon to MCP!

0
回复

We are very excited about Onform as it plugs natively to claude desktop and you can create and manage forms through chat.

Looking forward to all the feedback you have!

0
回复

@aima 100%

1
回复
#9
brag.fast
You ship features and they deserve to be seen
204
一句话介绍:brag.fast 是一款为开发者/独立创业者设计的自动化内容生成工具,通过多种集成方式,将代码发布或功能更新自动转化为精美的社交媒体图文与视频,解决了他们“只开发、不宣传”的痛点。
Social Media Marketing Alpha
开发者营销 发布说明自动化 社交媒体内容生成 AI设计工具 无代码工具 SaaS 产品增长 独立开发者 GitHub集成 REST API
用户评论摘要:用户普遍认可其解决“开发后不宣传”痛点的定位。主要问题集中于:AI如何从复杂更新日志中提取重点、生成模板的灵活性与控制度、与第三方工作流(如Typefully)的集成深度、对私有仓库的支持以及实际发布后的传播时效性。建议包括增加多平台帖子变体、优化定价信息清晰度。
AI 锐评

brag.fast 捕捉到了一个精准且普遍存在的市场缝隙:开发者的“宣传惰性”。其真正价值并非在于替代专业营销,而在于充当了“开发工作流”与“宣传义务”之间的自动化粘合剂。产品通过四种集成方式(厨房UI、API、AI MCP、GitHub App)构建了一个分层策略,本质上是在不同技术栈和用户习惯的入口处“拦截”发布意图,并将其转化为标准化视觉资产。

其犀利之处在于对开发者心理的把握:将宣传的道德压力(“你的工作值得被看见”)转化为一个可一键完成的、近乎游戏化的“烹饪”动作,降低了心理和操作门槛。然而,其深层挑战也随之浮现。首先,评论中关于“AI如何从混乱日志中选取重点”的提问,直指其核心AI能力的黑盒与可靠性问题——生成内容的“营销友好性”可能与技术更新的“准确性”产生冲突。其次,它试图标准化一种非标准化的东西(功能发布),当默认模板无法满足时,用户是否愿意投入额外精力创建自定义模板,这可能重新引入它试图消除的“设计摩擦”。

从商业模式看,其定价策略(大量免费额度搭配高额企业计划)暴露了其目标客群的两极化:用免费吸引大量独立开发者创造案例和流量,而真正的收入则押注于能高频发布的大型技术团队。这要求其AI能力必须同时服务好“小而美”的独立应用和“大而杂”的企业级产品,难度不小。总体而言,brag.fast 是一个巧妙的价值搬运工,但其长期护城河将取决于AI内容生成的“审美一致性”与“上下文理解深度”,而非仅仅是集成的便捷性。

查看原始信息
brag.fast
Developers ship features but never announce them and brag.fast fixes that. Four ways: Kitchen UI (no code), REST API, via AI (MCP), or Github app. 30 free credits (no card required).

Hey Product Hunt! 👋 I'm Rob, the maker of brag.fast.

The problem: I kept shipping features but I never showed them (well maybe just a text post now and then). Not because I didn't want to, I just didn't have time (aka I liked to build more).

What I built:
Kitchen UI
Fill in your feature details in the dashboard, click Cook, get images and video in seconds. No code required.

REST API
POST your release notes to `/api/v1/cook`, get landscape + square + portrait images back. Add `"video": true` for MP4. Simple as that.

AI (MCP)
Install the MCP server, say "make me release images for v2.1" or "/bragfast" and it just works. If you're already building in AI, this is the easiest way to get your visuals.


GitHub App
Publish a release, and AI reads your changelog to generate images or videos. Review in your dashboard or auto-approve.

Who it's for:

Indie Hackers, Solopreneurs, Vibe Coders, basically anyone who ships apps but never gets around to making social content for them. Your hard work deserves to be shown (in a cool way).

Pricing:

10 free credits, no card needed. Paid plans from $29/mo.

I'd love to hear:

Do you skip social posts on features? What would make this fit your workflow? Drop a comment!

6
回复

@rob_vb Love the layout and idea! Great for dev visibility, good work!

0
回复

@rob_vb Yes, sending it to Typefully/Buffer as a draft seems like the best course of action. Instead of auto-posting, which is probably what most people want for launch stuff, it keeps you informed. Allowing users to create several post variations for each release so they may select the one that best suits X, LinkedIn, etc. would further strengthen it.

0
回复

@rob_vb Hi. After I ship a feature, how quick does it actually show up so people notice it?

2
回复

i like the positioning. it is not trying to replace marketing, just making it easier to actually show what you built. That feels practical

2
回复

Thank you@lakeesha_weatherwax !

That's exactly what I'm trying to achieve. People like to build, and I think their features deserve to be seen in a cool way. I'm doing my best to make that as easy as possible.

0
回复
In practice, releases are messy: long titles, varying screenshot sizes, no screenshot, multiple bullet points. How does your template system handle auto-layout (wrapping, truncation, font scaling, safe areas) and what control do users have when the default render isn’t perfect?
2
回复

@curiouskitty The templates handle long texts by auto-sizing fonts. If the text doesn't fit the container, it'll reduce the font size automatically, so the user doesn't have to think about that.

Most importantly, the user can create custom templates so it everything looks exactly like they want it to. I've spent alot of time getting things right for the user without them needing master's degree in design.

1
回复

Very neat! It wasn't clear to me from the video + slides that you're also doing AI summaries, so the pricing came as a surprise. Also 40k credits feels like a lot of releases in a month, but I'm excited for your ambition!

2
回复

@hex_miller_bakewell Thanks for your feedback! What was the surprise, did you think the pricing wasn't right?

Yeah, 40k is meant for organizations, although I must say I can ship alot as a single person with AI these days 😁

1
回复

Oh, this is an interesting way to handle release notes and blog posts. Pretty cool idea. Does it just compile everything for you to release manually or is there some sort of way to direct the output to say the backend of a website?

That cook is a star, love the visual side of it -- looks really polished.

1
回复

Thank you @vallar !

Good question. In your admin area there's a tab History.


You can download a .zip of your files. If you want to output anywhere else, you can use the webhook so it can post the images and videos to your website for example.

1
回复

Hey @rob_vb ! Congrats on launch.

The GitHub App angle is clever – reading the changelog to generate visuals removes the last excuse for skipping the post. One question: how does the AI decide what to highlight when the changelog has 10+ items? Does it pick the most impactful-sounding ones, or does it use everything?

1
回复

Thanks @ikalimullin ! Congrats on your launch aswell!

Great question. It doesn't try to use everything, and it checks available objects of the templates. It picks the most impactful items and rewrites them as short, marketing-friendly copy (think "catchy headline + a few bullet points" not "raw commit log"). You can also control how many slides it generates, so if there's a lot of good stuff it'll spread the highlights across multiple slides instead of cramming it all into one. That said, it's still early and I'm actively tuning the prompts, so if anyone tries it and the AI makes a weird choice, I genuinely want to hear about it!

0
回复

This is timely for us. We're always shipping new features and never post about them!

1
回复

@bblalock  Your features deserve to be seen by potential users!

0
回复

looks genius tbh, tired of making feature announcements in Figma, gonna try this tool and comeback with the review. Good luck with the launch!

1
回复

@igor_martinyuk Thanks! Really curious what you think of it. I'm open to all kinds of feedback, I want to make this as easy as possible for every user.

0
回复

<3<3<3

1
回复

@damjanski <3 to you too!

(Dancing Dogs app is really fun btw!)

0
回复

The GitHub app angle is the one I'd actually use. Triggering visuals from a release means it happens automatically instead of being another thing to remember after shipping.

Also launching today with Grass, so I know exactly how much mental overhead launch day already has. Good luck @rob_vb

1
回复

@sunnyjoshi good to hear, definitely a time-saver!

Good luck with Grass! I’ll check it out immediately.

1
回复
Hey Rob, that line about never showing features because you liked building more is so relatable. Was there a specific feature you shipped that you were genuinely proud of but just never posted about?
1
回复

Oh yeah, definitely.

I had sooo much fun building this:


The cook actually animates every step you take in the form.

Before I wouldn't take the time to post this, but now it took me a few seconds to make a nice post about it.

1
回复

@vouchy I am curious about the GitHub integration. Does it work well with messy or very technical changelogs, or does it need clean input to generate good content?

6
回复

Teams known for shipping are often the best at showcasing their work (e.g. think about how many new release tweets you've seen from the Claude Code team). "Work like hell and advertise." mantra. Love you've really reduced the friction between shipping and communicating to users. Cool aesthetic, too!

0
回复

I'm guilty of shipping features and never telling anyone about them. The GitHub app catching it at merge is smart because that's the exact moment I've already moved on mentally. Does it work with private repos?

0
回复
#10
ScreenSmooth
Beautiful Screen Recordings in minutes
203
一句话介绍:ScreenSmooth是一款Chrome扩展,通过平滑鼠标轨迹、自动点击变焦、添加动态模糊和精美背景,快速将原始录屏转化为高质量宣传视频,解决了创作者在跨平台制作专业演示内容时流程繁琐、效果不佳的痛点。
Design Tools User Experience Alpha
屏幕录制工具 Chrome扩展 视频美化 自动变焦 光标平滑 动态模糊 演示制作 跨平台 一次性付费 效率工具
用户评论摘要:用户普遍认可其“快速美化”的核心价值,尤其赞赏其跨平台和一次性付费模式。主要问题集中于自动变焦和动态模糊在快速操作下的处理效果、与非Mac系统的兼容优化,以及与竞品(如Screen Studio)的核心质量差异。
AI 锐评

ScreenSmooth的聪明之处,在于它精准地切入了一个被“平台特权”和“订阅制”所割裂的细分市场。它没有试图在功能广度上挑战Screen Studio等成熟产品,而是以Chrome扩展这一轻量化、跨平台形态,将“快速产出观感专业的录屏”这一核心诉求产品化。其宣称的“从0到915美元营收”和吸引到的早期用户,验证了市场对“一次性买断、全平台可用”方案的渴求。

然而,其深层挑战也由此浮现。首先,技术天花板显著。作为浏览器扩展,其处理性能和对系统底层图形信息的获取权限必然受限,这直接关系到评论区用户关切的“快速鼠标移动处理”和“最终输出质量”能否真正比肩原生应用。所谓的“AI变焦”若缺乏细节阐释,易流于营销话术。其次,商业模式暗藏风险。79美元的终身定价在启动阶段是强大的增长钩子,但长远来看,可能难以支撑持续的开发、维护和云服务成本,容易陷入“卖得越多,负担越重”的陷阱。

它的真正价值,或许不在于技术颠覆,而在于提供了一种“足够好”的平权体验。它降低了制作“美观录屏”的门槛,满足了Windows/Linux用户、独立创作者、中小团队对性价比和易用性的即时需求。但若想从“有趣的工具”进化为“可持续的业务”,它必须解答:如何在轻量化架构下实现媲美原生的核心体验?如何构建超越一次性售卖的长期价值?否则,它可能只是用户逃离订阅制过程中的一个临时驿站,而非终点。

查看原始信息
ScreenSmooth
ScreenSmooth makes your mouse movement smooth, automatically zooms in on clicks, applies cinematic motion blur to all the animations, and adds beautiful background around your recording. In a minute your recording becomes a high-quality promotional. (Avaliable as Chrome Extension so work on MacOS, Windows, Linux)
Hey Product Hunt! 👋 I'm Sayyid. few months ago I started building ScreenSmooth with $0. Today: $915 revenue, Marc Lou become user, etc. What it does: - Records your screen - Auto Zooms on your clicks/typing - Smoothing your cursor - Makes demos look professional Why I built it: Because Screen Studio is Mac only and subscription but ScreenSmooth is working on Windows/Mac/Linux, and $79 lifetime Happy to answer questions! - Sayyid X: @Sayyidalijufri
3
回复

@Sayyidalijufri For someone using it daily for LinkedIn demos like quick branding tips, any pro tips on tweaking auto-zoom sensitivity or cursor smoothing for crisper results on non-Mac setups?

0
回复

@Sayyidalijufri This looks awesome, Sayyid! Love that it’s cross-platform and makes screen recordings look cinematic in minutes.

Curious—how does the auto-zoom and motion blur handle fast mouse movements or rapid clicks? Does it just “figure it out,” or do you tweak settings?

Also—huge congrats on hitting $915 revenue from a $0 start! Excited to see how this evolves.

0
回复

@Sayyidalijufri Hi. How good does it look when I record something with lots of fast mouse movement or scrolling?

2
回复

Just went through the pain of recording a product demo — multiple takes, inconsistent zoom levels, awkward cursor movements. The "beautiful in minutes" promise is real for anyone who's tried to make a raw screen recording look presentable. Question: does it handle zoom/highlight animations automatically or do you set those manually?

2
回复

@sagaiq_coo its handle both auto and manual

0
回复

Cool Product! How do you use AI to zoom compared to pure algorithmic screen recorders?

1
回复

@visualpharm oh... should i make it open source instead?

0
回复

My screen recordings look terrible because my cursor moves like a caffeinated squirrel. Auto zoom on clicks + cursor smoothing in a Chrome extension? Trying this today.

1
回复

@kailesk_khumar i would love to answer if you have any question

0
回复

Great launch. Congrats.

We need to record a new launch video (we also just launched today!) and will def be using this instead of screen studio.

1
回复

@stefano_delmanto really? thanks soo much

0
回复

tibo just upvote it🤯

1
回复

its already at 8 place🥹

1
回复

Great app, actually a Chrome extension. It works perfectly, and it’s the only tool I use to create beautiful demos! Thanks you!

1
回复

@thisiswhyibuilt Thanks you Andrey!

0
回复

Looks awesome! Great work, Sayyid!

1
回复

@wahabshaikh thanks a lot brother

0
回复

Looking good. I just cancelled Screen Studio and I'm looking for an alternative. It looks like a found something worth checking out! Also cool that some top people commented on X and see the value.

1
回复

@rob_vb thanks

dm me on X if you have any question

1
回复
When someone is deciding between ScreenSmooth and Screen Studio (or Loom/Tella), what’s the most important *quality* difference you’d want them to notice in the final video—and what did you have to build differently to get that result in a Chrome extension?
1
回复

@curiouskitty its clearly answered on the ScreenSmooth.com landing page comparison section

1
回复
#11
AgentMail
Email Inboxes for AI Agents
202
一句话介绍:AgentMail为每个AI智能体提供独立邮箱,让开发者无需处理OAuth、共享邮箱等复杂问题,即可实现智能体自主收发、线程管理和语义搜索邮件,解决了在客服、文档处理等自动化场景中构建邮件交互能力的核心痛点。
Email API Developer Tools
AI智能体基础设施 邮箱API 邮件自动化 无服务器邮箱 语义搜索 实时Webhook 附件解析 开发者工具 企业自动化 智能体身份隔离
用户评论摘要:用户认可其解决了Gmail API的OAuth、速率限制和共享邮箱难题。高频问题包括:与SES/Sendgrid的区别、2FA验证支持、自定义域名、安全性及语义搜索实现。开发者分享其在客服、投诉处理等场景的成功集成案例。
AI 锐评

AgentMail的实质,并非在“邮件”红海中做增量优化,而是为即将爆发的AI智能体经济铺设身份与通信基础设施。其核心价值在于将“邮箱”从一个沟通工具,解构为智能体的标准化“输入/输出接口”和“记忆外挂”。

产品巧妙避开了“用AI增强人类邮件效率”的拥挤赛道,转而定位“为AI提供邮件服务”,这一定位差异构成了其壁垒。它直击开发者用传统邮箱API服务智能体时的三大死穴:一是身份绑定难题(无需人类OAuth,实现智能体身份隔离);二是状态管理缺失(内置线程、语义搜索,让智能体具备对话记忆与上下文检索能力,而非每次重新解析原始邮件);三是实时性瓶颈(WebSocket支持将邮件流转化为事件流,尤其适合2FA等需即时响应的交互场景)。

从评论中的真实用例——从处理公用事业投诉到医疗客服,再到供应商谈判——可以看出,产品正卡位在“智能体需要与人类进行异步、长线程、带附件复杂交互”的关键工作流节点。其风险在于,这仍是一个早期市场,需求依赖于智能体本身能力的普及与成熟。同时,作为管道层服务,它需持续面对“能否自己搭建”的质疑,其护城河在于将邮件协议、送达率、搜索索引等脏活累活打包成简洁API与实时接口的工程能力与体验完整性。若智能体交互范式真成为主流,AgentMail有望成为智能体时代的“Twilio for Email”。

查看原始信息
AgentMail
AgentMail gives every AI agent its own email inbox. Your agent sends, receives, threads, and replies to emails on its own. No shared mailboxes, no OAuth per inbox, no human in the loop. Real-time webhooks and websockets. Semantic search across inboxes. Built-in email parsing and attachment extraction. Developers, startups, and enterprises are already deploying email agents with AgentMail. Free to start.

Hey Product Hunt! We're Haakam, Michael, and Adi. We're building AgentMail, the email API for agents.
We're not talking about AI for your email. This is email for your AI.

We wanted to build email agents you could forward your work to and get back a completed task. The agents would act entirely autonomously, they wouldn't need to borrow your identity. If they got stuck, they could just email you or anyone else.

Using Gmail, we kept hitting the same walls. No way to create inboxes programmatically. Rate and sending limits. OAuth for every single inbox. Keyword search that doesn't understand context. Per-seat pricing that doesn't work for agents.

So we built what we wished existed. An email provider for developers. APIs for creating inboxes and configuring domains. Email parsing and threading. Text extraction from attachments. Real-time webhooks and websockets. Semantic search across inboxes. Usage-based pricing that works for agents.

Developers, startups, and enterprises are already deploying email agents with AgentMail. Agents that convert conversations and documents into structured data. Agents that source quotes, negotiate prices, and get the best deals.

To celebrate our launch, we're giving early-stage teams a free month on our Startup plan. If you're building with agents, apply here: https://tally.so/r/QKrxj8

We also just added a deal for developers - 2 months free on our $20/month plan. You can claim the code right here from our Product Hunt page and get started for free at agentmail.to. Looking forward to hearing your thoughts.

11
回复

@haakam super excited about this and what comes next!

0
回复

@haakam Experimented with AgentMail around its inception to automate parts of MHacks. Amazing to see how the infra has grown.

3
回复

@haakam Congrats on the launch! agentmail is a brilliantly simple and elegant implementation of something lots of agents (and the developers that build them) are going to need.

3
回复

Used AgentMail a few months back for a project during a big SF power outage everyone was mad about, set up a bunch of inboxes people could pick from to send complaint emails to PG&E, plus shared public inboxes for transparency. AgentMail handled all the email stuff, literally plug and play. Built the whole thing overnight, and launched it on reddit in the morning, that's how easy it was to use. Congrats on the launch! 


Added a screenshot of an email someone sent using the platform below

5
回复

@kareem88 This is incredible! Love seeing powerful use cases like this!
Appreciate you sharing and congrats on shipping something that actually helped people when it mattered. Thanks for the support!

3
回复

Wait can i use this for 2FA? ive been losing my mind trying to get verification codes for browser automation agents. please tell me this solves that

4
回复

@vivek_sonar1 Yes and we support websockets too. That means you agent can enter its email in a form, open a websocket connection, wait for the 2FA, and enter the code all in the same thread. No need to spin up a separate http server that needs to be publicly exposed to receive webhooks.

4
回复

So how is this different from just using SES or Sendgrid? I've been hacking together SES for an agent project and it kinda works but feels like im fighting it the whole time. What am I missing here

4
回复

@new_user___0992026f7638df402840b2b Other email APIs just give you a webhook notification when you receive an email. AgentMail providers inboxes, threads, messages, attachments and allows you to reply, forward, label, search, etc. The functionality is a lot closer to Gmail.

4
回复
0
回复

semantic search across agent inboxes is a nice touch. we've been thinking about AI agents that need to handle support emails for our healthcare clients, and the threading/context preservation would be huge. are you seeing mostly customer service use cases or other workflows?

3
回复

@piotreksedzik Hey Piotr, thanks! Yeah we actually have a ton of customers using us for healthcare support exactly. We also see teams using us for document processing, vendor negotiation, and a few startups using us for QA testing. The common thread is agents that need to hold real conversations and maintain context across threads. If you need any help getting set up feel free to reach out at support@agentmail.to, happy to help!

2
回复
How do semantic search and reply/quote extraction work end-to-end for an agent developer—what gets indexed, what stays private, and how does it compare to just storing raw emails and letting each agent re-read its thread history with an LLM on every turn?
3
回复

@curiouskitty All emails sent and received by AgentMail gets indexed, but of course stays private to you. This allows agents to quickly find what they might need and then narrow down by reading the threads.

3
回复

a email for your ai, not ai for your email... love that distinction. we've been struggling with parsing attachments into structured data using legacy providers. does the text extraction handle complex pdfs well? @haakam @AgentMail

2
回复

@haakam  @priya_kushwaha1  Yes. 100% completely PDF support. We will make it better for everyone!

3
回复

Insane potential on the project, can't wait to see what you guys build and congrats for the launch !

2
回复

@francoisdefitte Thanks Francois! That's love

0
回复

Ok this is actually solving a problem we hit last month. We tried giving our AI agents email capabilities through Gmail API and it was a nightmare — OAuth per inbox, rate limits, the whole thing. The websocket approach for 2FA is really clever. Quick q: do you support custom domains so agents can send from @company.com?

2
回复

@pierre_de_la_grand_rive Yeah you can connect your own domain so agents send from @yourcompany.com. You add a couple DNS records from our console, CNAME for DKIM, SPF include, MX record and we handle key rotation and deliverability from there. Glad you found us! Please reach out if you need any help : )

Also check out the special offers we have running for the launch!

0
回复

This is super clean, giving each agent its own inbox makes a lot of sense.

Quick question though, what happens if an agent gets compromised or starts acting weird? How do you stop it from sending spam or leaking data?

2
回复

@dong_recost Good question! Each inbox is isolated so one agent acting up doesn't affect others. We have rate limiting, reputation monitoring, and allow/blocklists you can configure per inbox. You can also revoke an agent's inbox instantly if something goes wrong. The isolation is actually one of the big advantages over shared mailboxes where one compromised agent could mess things up for everyone.

0
回复

Not trying to be an a-hole, but couldn't you just build this on top of Cloudflare email workers + SES in a weekend?
What's the actual hard part here that justifies paying for it?

2
回复

@raymond_1907 You could build something that exchanges emails, yes. But, we provide webhooks, inboxes, threads, attachments, replies, and even custom domains. This functionality is a lot closer to what consumer mail providers like GMail and Outlook have to offer BUT for your agent.

1
回复

Giving each AI agent its own inbox is a simple idea, but it unlocks a lot. Agents can operate like real participants in workflows instead of awkward integrations bolted onto shared mailboxes.

The semantic search and built-in parsing are interesting too. Once agents can reliably read attachments, thread conversations, and react in real time, email becomes a surprisingly powerful automation layer.

2
回复

@niksmac Well said! That's exactly how we think about it. We think the next billion users of the internet are going to be AI agents, and for them to be effective they need their own identity, not borrowed human credentials. Giving them an inbox is the first step. Thanks for checking us out!

1
回复

Congrats on the launch! 🎉

AgentMail solves a problem I hit head-on while building my open source project Praktor — a personal AI agent assistant that runs multiple Claude-powered agents in isolated Docker containers. I needed a way for agents to send and receive email autonomously, without the nightmare of managing OAuth tokens per agent or sharing a single mailbox across them.

AgentMail was a perfect fit. The WebSocket integration for real-time message.received events made it straightforward to wire up — my gateway maintains a persistent WS connection and dispatches incoming emails to the right agent based on their inbox ID. Each agent gets its own dedicated inbox, fully isolated, which aligns perfectly with the sandboxed container model.

The developer experience is really clean. No per-inbox OAuth, the API is simple and well-documented, and the real-time delivery via WebSockets just works. Took me an afternoon to integrate, and it's been reliable since.

If you're building anything with autonomous agents that need email capabilities, this is the infrastructure you want so you can focus on the agent logic instead of fighting email protocols.

1
回复

@zen_guerrilla This is amazing to hear. Thank you so much for sharing, Manolis. Appreciate the support.

0
回复
As someone who’s been building with AgentMail from the beginning I can tell you: anyone who claims to be on the forefront of the new agentic paradigm should know and use agentmail. Amazing work team! Congrats on the launch.
1
回复

@jacobclaerhout Thanks for the kind words Jacob!

0
回复

@haakam Great product -- experimented on my own after getting credits from a Hackathon; Amazing to see its evolution of the last year or so

1
回复

@haakam  @nikhil_vaidyanathan Thanks Nikhil! Love hearing that

0
回复

That is cool. Is it for the mass mailers or personal automation? How is it different from gog that I use for agents?

1
回复

@visualpharm It is for everything. We see it as the email API of your agents' dreams. gmail, and other email providers built for humans, are not the best setup for agents considering their setup has always been anti-bot. We built to bridge that gap in the market.

0
回复

The WebSocket support is crucial for me. No public-facing webhook url required, and the flow is simple. White-listing, attachments, so far everything I look for, I find. Very impressive, vastly better than anything else for my uses.

1
回复

@pwinnski Means the world to us! Thanks Philip

0
回复

Our customers have used it to set up voice agents and used this an an inbox for their agents! Works seamlessly. Great job! @adi_singh13

1
回复

@adi_singh13  @pratikmundra Thanks Pratik! Great to know : )

0
回复

How does agent self-signup work?

1
回复

@anmolcs We actually launched agent.email for this. This is a LP that agents can use to sign up for AgentMail - no human needed :)
Check it out and let me know if you have any thoughts!

0
回复

We use Agentmail to power our customer support experience, great work guys!!

0
回复

@heycamego Thanks, Carlos. Appreciate the kind words. Great to hear that you're finding value with AgentMail.

0
回复
#12
Smuggl
Share your localhost as an invite only link
194
一句话介绍:Smuggl 是一款允许开发者将本地主机(localhost)生成为加密、仅限受邀访问链接的工具,在需要安全分享本地开发环境进行演示、预览或收集反馈的场景下,解决了传统方式需完全暴露计算机至公网的安全隐患。
Developer Tools Alpha
开发工具 本地开发分享 内网穿透 安全演示 开发者协作 网络安全 预览工具 轻量级工具 Go语言 TUI应用
用户评论摘要:用户普遍认可其“默认阻止、手动放行”的核心安全逻辑,认为比ngrok等工具更安全便捷。主要问题集中在:与竞品(ngrok, Cloudflare Tunnels, Tailscale)的差异化、链接安全性(防猜测)、密码保护、Slack集成、无头(自动化)运行模式以及实时阻断机制。开发者回应积极。
AI 锐评

Smuggl 切入了一个微小但真实存在的缝隙市场:在“完全开放的ngrok式公开隧道”与“配置复杂的零信任网络方案”之间,提供了一个极简的、以人为审核为核心的安全层。它的核心价值并非技术上的颠覆,而是产品定位与用户体验上的精准拿捏。

它聪明地抓住了开发者在“分享”与“安全”之间的心理矛盾。开发者渴望快速分享localhost以获得即时反馈,但又对将个人电脑端口暴露给整个互联网心存恐惧。Smuggl将“暴露”转化为“邀请”,并通过直观的TUI界面将访客IP和国家信息呈现出来,把访问控制权从复杂的配置文件中解放出来,交给了开发者一个直观的“允许/阻止”按钮。这种设计将安全责任转化为一种可感知、可操作的简易流程,极大地降低了心理负担和操作成本。

然而,其面临的挑战同样清晰。首先,其“手动审批”模式在需要大规模或异步协作的场景下可能成为瓶颈,这从用户询问密码保护和自动化功能就能看出。其次,其商业模式(提及12美元终身费用)在面对成熟竞品时能否持续存疑。最后,其技术壁垒可能不高,“Go+Charm”的选型也印证了其轻量化、快速实现的思路,护城河可能在于对开发者工作流细节的持续打磨和体验优化。

本质上,Smuggl是“安全思维”在开发者工具领域的一次轻量级实践。它未必适合企业级重型应用,但对于独立开发者、小团队快速原型展示、以及需要频繁进行客户预览的场景,它提供了一个恰到好处的、心理上更安稳的解决方案。它的成功与否,将取决于能否在保持极致简单的同时,优雅地扩展其功能边界,以应对用户自然增长的需求,而不至于沦为另一个复杂的配置工具。

查看原始信息
Smuggl
Smuggl lets you share your localhost as a secure link instead of blindly exposing your computer to the whole internet.

Hey Smugglers!

Smuggl lets you share localhost without exposing it to the whole web. You can create an invite only links, see each visitor’s IP and country, and choose who to allow or block.

Built for quick demos, previews, and feedback on local apps without opening everything up.

Go try it out and have fun!

Sayuj

6
回复

@sayuj_suresh Kudos on the launch, just a tiny quetsion: any plans for password protection on links or integration with tools like Slack for seamless team previews?

0
回复

@sayuj_suresh Hi. How safe is the invite-only link? Can random people still guess it somehow?

1
回复

neat product - no more "Check out my latest app http://localhost:3000"

5
回复

@fmerian hahaha yess!

1
回复

@fmerian woah, looks exactly like mine

0
回复

@fmerian Exactly what I wanted to say!

0
回复

I use ngrok and have it for years. $12 lifetime with the ability to see who's accessing before letting them through? Great.

1
回复

Neat name 🥷

1
回复

Hey! This is pretty cool! Can I ask how it differs from the likes of ngrok?

1
回复

@jordan_carroll2 Thanks! It doesn't expose your computer to public web instead you have to approve each ip which is much more secure! Neve expose your computer localhost to public web

1
回复

People laughed about http://localhost:3000 you fixed it!

0
回复

Love the idea! Is it possible to run it without TUI (automation)? Use case: I have the remote agent running somewhere behind firewall and I want it to expose me a dev server.

0
回复

@artur_rosa That’s a food idea I will work on it!

0
回复

Getting clients to review local builds without pushing to a staging environment is always a hassle, so having an invite-only layer right over localhost is a massive upgrade over basic ngrok links. Do you handle the authentication via magic links or does the invitee need to create an account first? I could see myself using this constantly for quick design sign-offs before deploying.

0
回复

@y_taka It is very simple, you will see the visitor ip on your terminal and you just allow or block. No account creations or other weird stuff

0
回复

@sayuj_suresh , hi! nice job. The invite-only plus IP visibility combo is a nice touch for demos. usually you either expose everything or nothing. Does blocking work in real time, or do you have to set the allowlist before sharing the link?

0
回复

@ikalimullin thank you! it works on real time where each IP shows up and you can allow or block!

0
回复

Excellent to share, I've always used Cloudflare Tunnels

0
回复

@enzoevn that's a good choice too, it is just oo much setup for me to do.

0
回复

very cool. I've used ngrok for this before and I believe tailscale has a functionality similar to this as well. I do like the "block by default" approach. what did you write it in? l will guess rust based on the TUI, with a backup guess of go (maybe with charm?) :) congrats on shipping!

0
回复

@catt_marroll Hey Matt, yes smuggl is just ngrok but block by default! I built with go and charm!

2
回复
This is something I definitely would have wanted when I just started, and I think will still be useful when I test out random ideas! Looking forward to using this on the next project
0
回复

@krishnam_goel Yess that's exactly why I built smuggl, to share my silly projects with friends without exposing my mac to the whole world!

1
回复

Good luck with the launch @sayuj_suresh ! Love the simplicity of Smuggl, one feature, but a much needed one.

While I generally don't develop locally anymore, I can totally see the use case for Smuggl.

0
回复

@jonathanfors Thank you Jonathan! Hahaha yes I develop and do builds all on my local machine so need to make sure it is secure, so that's how I ended up building smuggl!

1
回复
#13
Startups.RIP
Rebuild 1,738+ dead YC startups with AI
181
一句话介绍:一款利用AI深度研究并生成已关闭或被收购的YC初创公司详尽“验尸报告”与重建指南的数据库,帮助创业者在当前技术环境下快速验证并重启那些因时机不对而失败的商业创意,解决从零到一寻找经市场初步验证方向的痛点。
Startup Lessons Vibe coding Alpha
创业灵感 AI研究工具 初创公司数据库 市场验证 失败分析 YC生态 产品重建 商业智能 趋势洞察 SaaS
用户评论摘要:用户普遍认可其作为灵感来源和数据库的价值,但质疑“每个失败初创公司都是已验证市场”的论断。主要建议包括:为报告增加TL;DR摘要、区分“关闭”与“被收购”状态并增加筛选、优化信息呈现(如加入网站历史存档链接)。创始人对反馈回应积极。
AI 锐评

Startups.RIP 的精明之处在于,它巧妙地将“失败叙事”从单纯的教训库,重构为一个充满机会的“半成品市场”。其宣称的真正价值并非在于那1700多条死亡记录本身——这类信息散见于网络——而在于其AI驱动的“翻译”与“重构”能力:将陈旧的失败案例,转译为符合当下AI代工(如Claude Code)时代语境的、可立即执行的“重建手册”。

然而,产品面临的核心质疑直指其逻辑根基。评论犀利地指出,并非所有失败都意味着市场存在,很多是源于根本性的需求或经济模型缺陷。创始人Oscar的回应将范围缩小至“已达到PMF但仍失败”的项目,这虽使论点更严谨,却也暴露了其分析框架的模糊性。AI如何从混杂的、时常带有事后合理化的创始人叙述中,抽取出真实的失败动因?这仍是黑箱。目前,其最大优势似乎是高效的信息聚合与结构化,为创业者提供了高效的“灵感沙盘”。

其商业模式暗藏巧思。“建造者折扣”旨在形成激励闭环:用户从平台获取灵感并成功构建,反过来又为平台增添了成功案例。这试图将“末日浏览”转化为生产力,但最终考验的是其“重建手册”能否真正跨越“时机”这道最关键的鸿沟。它提供的是一份基于历史数据的“技术实现图纸”,但创业成功所需的市场敏感度、运营智慧和运气,是任何AI都难以打包提供的。它是一款强大的辅助工具,但绝非确保成功的“阿拉丁神灯”。

查看原始信息
Startups.RIP
Startups often fail because of timing, not ideas. Startups.RIP is a wiki of 1,700+ YC startups that shut down or got acquired. Our AI research agent writes a detailed post-mortem (what they built, why they failed, what's changed since) and a rebuild playbook with implementation-ready technical specs you can drop straight into your AI coding agent. Every failed startup is a validated market with unfinished business. Shortcut the idea maze. Start with what almost worked.

Hey Product Hunt, I'm Oscar, the maker of Startup.RIP 👋

The best startup ideas aren't always new. They're remixes that entered a market at the right time.

Lyrebird (S17) built AI voice cloning in 2017 and folded. Years later, ElevenLabs hit $11B valuation on the same idea. Multiple YC companies tried prediction markets before regulatory changes enabled Kalshi to go mainstream. It pays to learn from startup history.

Startups.RIP is a database of 1,700+ YC startups that died or got acquired. Our AI deeply researches post-mortem for each one — what they built, why they failed, what's changed — and generates a rebuild playbook with implementation-ready specs you can drop into Claude Code, Codex, or your coding AI of choice.

As covered by Forbes: dozens of YC fintech startups that took teams of engineers years to build can now be shipped in an afternoon using AI.

The first 32 reports are free. Pro ($20/mo) unlocks everything. We're giving 25% off the Pro subscription to our first 100 supporters (use the code PHLAUNCH). We also offer a 50% BUILDER discount for anyone who builds and ships a project inspired by an idea they found on Startups.RIP.

The product is still rough around the edges, so any feedback is much appreciated. Drop a comment; I read everything.

What failed YC startup would you rebuild with AI today?

6
回复

@sfoscar Oo!! I had this idea once maybe a year ago on a random work, just never worked on it. Seeing it launch here and gather so many points is satisfying :) I feel very happy for you!

3
回复

Interesting dataset. Looking at failed startups is always useful.

But I’m not fully convinced by the framing that “every failed startup is a validated market.” Many of them failed because the market simply wasn’t there, or the economics never worked. Timing matters, but sometimes the idea itself was flawed.

Also curious how the AI determines why a startup failed. Post-mortems are messy and often speculative even for humans who were inside the company.

Still, the archive itself sounds valuable. A structured database of 1,700 YC shutdowns could be a great learning resource for founders if the analysis stays grounded in real signals and not just narrative.

6
回复

@niksmac You're right, that was probably too strong a statement. I was mostly thinking of startups that hit PMF (in YC's words, "made something people wanted") but still failed. Many were over-capitalised for the size of the market they were in, so while it might not have made sense as a venture-backed co, it could be a great bootstrapped business.

Re: economics, AI changes the landscape too. E.g. Atrium (W18) tried to do a tech-enabled law firm, but most of the work still had to be done by expensive lawyers. Years later, startups like Harvey, Legora (W24), and Crosby were able to benefit from offloading legal work to LLMs.

Our specialised Deep Research agent prioritises any post-mortem / retrospective-like commentary from the founders themselves (blog posts, tweets, podcast interviews, etc.) We try to ground the claims in primary accounts as much as possible and note speculations.

Appreciate you checking us out!

1
回复

Loved the idea and the name, all the best for the launch. Small feedback it would be great if u could add TL;DR for each startup.

4
回复

@gamifykaran yes karan i also think so

3
回复

@gamifykaran great idea! we will for sure add this. thx for suggesting 🙏

2
回复

lol at Delve being the first featured company hahaha. This is cool to see though. Love that it does so much of the heavy lifting... it's not an aggregated graveyard, more like a treasure trove + AI planning so you can avoid any pitfalls

3
回复

@chris_u_han thx for the kind words! "treasure trove" is a great way to put it, I hope Startups.RIP can inspire people who are looking for their project to tackle!

0
回复

This provides a great dataset for anyone looking to learn from companies that didn't end up succeeding. One question, if a company was acquired instead of shutting-down, does Starups.rip provide information on what worked and how it went through the steps to get acquired?

2
回复

@bill_mccormick09 Hey Bill, currently we don't separate it out into its own section, but that information may be embedded in the rest of the report on the startup's history and timeline. It might be good to call this out more explicitly in the text or UI. Is there a particular acquired startup you would be most interested in? I can send it to you when it's ready. Thanks for the suggestion!

1
回复

It seems like I should be able to filter out acquisitions. I.e optimizely isn’t really dead, it just isn’t public or still a startup.

2
回复

@catt_marroll Good point! We'll add a filter for status (inactive or acquired). We currently only filter by batch & industry.

1
回复

I always loved browsing this site before I even launched my first product. Absolute gold mine for when you have founders-block

2
回复

@krishnam_goel So glad it helped! If your next project is inspired in part or whole by the ideas on Startups.RIP, please let me know! We'd love to feature you 😁

1
回复
@sfoscar Today's launch actually was! Inspired by Marf & Rejoy Health, part of the reasons they didn't do so well is what Cyris hopes to solve
2
回复

I love the name, You can maybe include a link to the archive website to see the previous website ?

1
回复

@bengeekly Good call! We'll wrap old links (might not be up anymore) in something like web archive / wayback machine.

0
回复

Some of them might work if the product + strategy were done properly.

1
回复

@busmark_w_nika I think so too! Many people take away the wrong lessons from startups lessons "oh that has been tried before & didn't work" when in reality markets evolve, consumer behaviours evolve, the underlying tech & infra evolves, etc. not to mention the team's execution, of course.

0
回复

Love the 50% BUILDER discount – so if I read about a dead fintech startup and immediately ship the same thing, you'll give me a discount on the tool I used to get the idea. That's a beautiful loop. Does anyone actually do this or is it mostly people doom-scrolling YC obituaries 😆

1
回复

@ikalimullin We just shipped builder discount today so no one has taken me up on it yet. But we wanted to find some way to reward the builders & doers. It's just a small incentive, but sometimes that's all it takes to break out of analysis paralysis :)

Is there one company you'd want to see someone reimagine for the AI era? Maybe something you'd want to use yourself?

0
回复

Hah I love that delve is at the top of the list. RIP indeed..

1
回复

also wow i just went into the details page, i didnt realize how thorough these are! https://startups.rip/company/delve, very impressive, include references at the end. damn.

1
回复
#14
Convert or Not
Simulate first-time users. See why they drop off
153
一句话介绍:一款通过AI模拟目标首次访问用户行为(点击、滚动、尝试注册等),自动识别网站转化漏斗中的犹豫点和流失原因,帮助开发者在真实用户流失前发现并修复问题的工具。
Analytics Artificial Intelligence Alpha
用户行为模拟 转化率优化 用户体验分析 AI驱动测试 网站分析工具 产品增长 用户流失分析 无代码测试 首访用户洞察 SaaS工具
用户评论摘要:用户普遍认可其“模拟首次用户”的核心价值,尤其在产品早期缺乏真实用户数据时。主要问题与建议集中在:模拟行为的真实性与深度(是发现技术摩擦还是理解问题?)、对移动端网页的支持、测试队列等待时间与完成通知、不同用户画像的对比分析功能,以及后台模型的具体构成。
AI 锐评

Convert or Not 切入了一个精准且疼痛的缝隙市场:产品冷启动或迭代初期,那一段“有数据但看不懂,有用户但留不住”的尴尬真空期。传统分析工具告诉你“发生了什么”,用户访谈告诉你“他们怎么说”,而它试图用AI模拟来回答“他们当时为什么犹豫”——这是一个从描述现象到推测动机的野心跳跃。

其真正价值不在于替代A/B测试或真实用户研究,而在于充当一个成本极低、随时可用的“第一反应”诊断系统。它用预设的用户画像驱动LLM进行推理交互,本质上是将产品团队对用户心智模型的假设,与网站的实际交互界面进行了一次压力测试。从评论看,其成功案例(如发现定价页面的盲点)印证了这种“旁观者清”的AI视角的价值,它能打破创造者自身的认知茧房。

然而,其面临的质疑也直指核心:模拟的“真实性”天花板。工具能出色地识别按钮无法点击或流程混乱,但它能否真正理解用户因价值主张不清晰而产生的“5秒困惑”?这涉及到对“意图”的深度建模,目前的LLM可能仍停留在模式化的行为模仿上。此外,将复杂的流失原因简单地归因并呈现,本身可能带来误导风险。

产品当前的爆发性关注,反映的正是市场对“自动化、可解释性用户洞察”的渴求。它的未来不在于追求100%拟真,而在于明确其能力边界——是优秀的“UX检查员”和“流程压力测试员”,而非真正的“用户心理分析师”。若能清晰界定于此,并深耕移动端、多画像对比等实用场景,它将成为增长团队工具箱中一把锋利的手术刀。

查看原始信息
Convert or Not
Convert or Not simulates first-time user sessions on your site. It clicks, scrolls, and attempts to complete key actions like signup, revealing where your target users hesitate, drop and why. Use it to understand and fix conversion gaps before real users are lost.

If you don’t have time for user research, this simulates your target first-time users clicking, scrolling, and using your site, and shows where they drop off and why.

I kept seeing users get close to signing up, then stop. This tries to show where, and more importantly, why that happens

3
回复

@junetic This is actually a really interesting approach — most tools tell you what users do, but not really why they hesitate in the moment.

The simulation angle feels like it could uncover things analytics completely misses.

Curious — how do you model different user intents? Like someone exploring vs someone ready to sign up?

0
回复

@junetic Hi. How realistic are the simulated first-time users? Do they really behave like real noobs?)))

I'm definitely bookmarking this tool. I often work with website releases

2
回复

Congrats on the launch! 🎉

Honestly the timing of this is uncanny. I've literally spent today trying to figure out how to get real test users for my own product. Watching people drop off without knowing why is one of the most frustrating parts of being a solo founder. You build something, you ship it, and then... silence. Was it the headline? The pricing? The signup flow? You're guessing.

A simulated first-time session that tells you where people hesitate is genuinely useful , especially in that gap before you have enough real traffic to A/B test anything.

Quick question: how close does the simulation get to real human hesitation? Like does it catch the "I don't understand what this does in 5 seconds" moment, or is it more about UX friction (broken buttons, confusing flows)? Curious where it sits on that spectrum.

Either way, congrats

2
回复

@maria_fitzpatrick Maria's question didn't really get answered and it's the one I'd most want to know. There's a big difference between "the button was broken" and "I didn't understand what this product does in 5 seconds." One is a fix, the other is a positioning problem. Does the simulation tell you which one you're dealing with?

0
回复

Just ran it on our landing page and damn, it caught a friction point on our pricing section I've been blind to for weeks. The persona-based simulation is what sells it — generic "user testing" tools miss the fact that a CTO and a marketing lead look at the same page completely differently. Would love to see a comparison mode where you can run the same page with different personas side by side.

1
回复

@pierre_de_la_grand_rive great to hear it was helpful. You can generate a combined report where there is some comparison available but we will work on improving it

0
回复

Could be interesting to see or simulate how users will interact. How are you modeling a first-time user? Is it rule based flows, LLM-driven reasoning or something else?

1
回复

@lak7 No rule based flows. LLM reasoning on ux (what it sees, experiences and does) with context about their persona (that you can specify based on who your target user is)

0
回复

Would you ever work on a version for mobile apps? I would love to be able to simulate first-time user sessions on our mobile app on both iOS and Android and understand more about our user behavior

1
回复

@chris_u_han Do you use any mobile product analytics? ie mixpanel, posthog etc?

0
回复

cool idea, congrats on the launch! would be great to have some kind of indication how long the user simulations will take - they take a while, and i don't want to just sit there waiting. either a browser notification when they finish, or an estimated timeline. can't really comment on output quality, since my test run is still queued. which model are you using in the background?

0
回复

@bengauss thanks for the great feedback. There are a bunch of people trying it out so the queue was delayed. And some server issues which now should be fixed. You will be emailed once processing is done

0
回复

@bengauss using various models in background (claude, openai etc)

0
回复

Interesting idea, I wish I knew about this a day before at least.

I tried the website out and it was straight forward except for a couple of things:
1. It wasn't very clear that I can run one single persona and it took me quite a bit of time till I realized how to run a single one not all 3. I thought the Edit part would only edit the persona and not exclusively run it.
2. When I ran that one single persona against my website, it went to the queue (which is fine), however, 45 minutes later and it is still in queue. Not sure if that is intended or not.

Does it notify me when it is done? I kept refreshing to see if it finished the analysis or not.

Nonetheless, congratulations on the release.

0
回复

@vallar thanks for the feedback. You'll be notified when report is ready

1
回复

Hey! Looks great, is it going to work with mobile apps?

0
回复

Hey Junu, this is a great idea as I'm just launching and would love to know more on how users will use my landing page. I just signed up but now I'm stuck on a blank screen. Any suggestions?

0
回复

@jordan_carroll2 Hi Jordan. Could you go back to main page (convertornot.com) and let me know what you see

0
回复

Congrats on the launch! This is really interesting, I had to give it a go on my site PromptBase where I spend a lot of time optimising for CRO. I liked how it was super simple to just paste in a URL and also choose the customer persona. I got a score of 5/100 (not converted) but not sure it ran successfully. Would love to achieve a successful run!

0
回复

@tinyprojects Thanks for trying it out! Will take a look to see if smth went wrong 😅

1
回复

@tinyprojects quick update - there was an issue with the model taking action - making clicks etc. It should be fixed now. You can try another run and hopefully it is better

0
回复

This is most useful for new SAAS products testing with real users is always expensive!

0
回复

Alright this is scary relevant. I just launched my app and I'm watching people hit the landing page and vanish. The gap between 'someone visited' and 'someone downloaded' is where indie devs go to cry. Real question: does it simulate mobile users too? Because 70%+ of my traffic is mobile and desktop testing tells you almost nothing about that experience.

0
回复

@thenomadcode Right now desktop web but mobile web can be added soon

0
回复

@thenomadcode EXACTLY what I was thinking - we just launched too and would be lovely to be able to see mobile web too!

0
回复
#15
Claude Managed Agents
Pre-built agent harness on managed infrastructure
143
一句话介绍:一款提供预构建、可组合API套件的云托管智能体部署平台,通过在云端原生处理沙箱、工具执行、状态管理等复杂基础设施问题,帮助开发团队大幅提升生产级智能体的部署速度,专注于用户体验构建。
API SaaS Artificial Intelligence
智能体部署平台 云托管 可组合API 生产级AI 基础设施即服务 多智能体协作 长时会话 沙箱执行 企业级AI工具 Anthropic生态
用户评论摘要:评论者认为该产品是企业部署云端Claude工作流的强大竞争者,其核心价值在于将基础设施的繁重工作(如沙箱执行、状态管理)原生处理,使团队能专注于核心业务。同时,评论也提出了一个关键质疑:究竟哪个系统能在实际生产中真正交付成果。
AI 锐评

Claude Managed Agents的出现,标志着AI智能体赛道正从“玩具”和“演示”阶段,迈入严肃的“生产部署”深水区。Anthropic此举的深层逻辑,并非仅仅是提供一个工具包,而是试图为混乱的智能体开发生态定义一套“云原生”标准。

其真正价值在于“接管复杂性”。当前,将实验室中的智能体转化为稳定、安全、可协作的生产服务,面临工具链混乱、状态管理棘手、基础设施运维沉重等巨大鸿沟。该产品将沙箱、认证、工具执行、长会话等非差异化但至关重要的脏活累活打包成托管服务,本质上是在出售“确定性”和“效率”,承诺让团队部署速度提升10倍的口号也直击企业成本痛点。

然而,光环之下暗藏挑战。首当其冲的是“锁定风险”。企业一旦将核心智能体的运行底座深度绑定于此平台,未来的迁移成本和灵活性将成为一个问号。其次,评论中“哪个系统能真正在生产中交付”的质疑非常犀利,这指向了智能体技术的核心痛点:在受控演示中表现惊艳,在复杂真实场景中却可能脆弱不堪。该平台解决了“部署难”,但并未承诺解决“智能体不好用”的根本问题。最后,在AWS Bedrock、Azure AI Studio等云巨头均已布局智能体托管服务的战场上,Anthropic这款源自其自身工程实践的产品,是能凭借对Claude模型的深度优化和更敏捷的体验脱颖而出,还是最终会因生态位狭窄而受限,仍需市场检验。它是一剂强效的止痛药,但智能体应用的“疾病”是否仅在于“部署之痛”,仍需观察。

查看原始信息
Claude Managed Agents
Claude Managed Agents is a suite of composable APIs for building and deploying cloud-hosted agents. It handles sandboxing, authentication, tool execution, long-running sessions, and multi-agent coordination, letting teams focus on user experience while shipping production agents up to 10x faster

Hi everyone!

Claude Managed Agents is shaping up as a strong contender for enterprises deploying cloud-based Claw workflows.

By natively handling the infrastructure—sandboxed execution, state management, orchestration, and long-running sessions—they are taking all the heavy lifting out of agent deployment.

Ultimately, the key question is still the same: which system can actually deliver in production?

Check out this engineering post to dive into how Anthropic built it.

2
回复
#16
Ycode Open Source
The open-source alternative to Webflow
138
一句话介绍:Ycode Open Source 是一款开源、可自托管的可视化网站构建工具,通过提供代码所有权和部署灵活性,解决了用户被Webflow等闭源平台在数据、定价和扩展性上“锁定”的痛点。
Design Tools Open Source Website Builder
网站建设工具 开源替代品 可视化开发 无锁定策略 自托管 MCP连接 Webflow竞品 开发者工具 社区驱动 灵活部署
用户评论摘要:用户反馈积极,认可开源理念。主要问题集中于:与AI智能体通过MCP的兼容性、是否支持导入Webflow模板、以及与Framer的功能成熟度对比。有评论指出Framer因社区大而暂时领先,但看好Ycode长期潜力。
AI 锐评

Ycode Open Source 祭出“开源”大旗,直指Webflow、Framer等主流可视化建站工具最敏感的命门——平台锁定。其真正的价值内核并非功能层面的简单复刻,而是一场关于“所有权”和“控制权”的范式转移。它试图将建站从一种“租赁服务”重新定义为“自有资产”,通过开放源代码和允许自托管,赋予开发者数据自主、迁移自由和成本可控的终极权利。

然而,其面临的挑战同样尖锐。首先,“开源”在降低门槛的同时,也意味着用户需要承担更高的技术栈责任,这与主流无代码用户追求“省心”的核心诉求存在内在张力。其次,评论中关于MCP连接、模板兼容性的疑问,暴露出其生态位的关键短板:一个建站工具的实用价值,不仅在于引擎是否开放,更在于其模板市场、组件库、集成生态的丰富度。Framer评论者点出的“社区更大”正是其护城河所在。

产品将“MCP连接”作为亮点,颇具前瞻性,这暗示其战略是押注AI代理驱动的开发范式。若能成为AI构建网站的首选可操控、可审查的基础层,或许能开辟一条绕过传统模板竞争的新路径。但眼下,它更像是一份面向技术意识强烈的开发者与创业公司的“宣言”,其成功与否,将极度依赖开源社区能否真正形成贡献闭环,快速填补与巨头之间的功能与生态鸿沟。它掀开了桌子,但自己也需要在同样的餐桌上,端出更美味的菜肴。

查看原始信息
Ycode Open Source
Most website builders like Webflow or Framer lock you in. Ycode is an open-source alternative that puts you back in control, with everything you need to build professional websites—including MCP connections for AI tools.

Hey everyone 👋

When we started building Ycode, we kept coming back to the same problem: Most website builders don’t just help you build, they lock you in. Your site, your data, and even your ability to scale are tied to a platform you don’t control, with pricing and rules that can change anytime.

We believe it shouldn’t work like that.

With Ycode Open Source, you can fully own your project. You can self-host it on your own infrastructure, use Ycode Cloud for convenience, and move between the two whenever you want. No lock-in, no restrictions, just flexibility.

What makes this even more exciting is the community. Ycode isn’t just built by us, it’s shaped by developers and creators contributing and improving it together.

We truly believe the future of website building is open, flexible, and accessible to everyone, not controlled by a few platforms.

Would love to hear what you think 🙌

2
回复

@lunenas That's great! I like it. Does this work with any agent using MCP? I'll try it with the agent I built.

0
回复

Congratulations! Is it compatible with Webflow templates?

0
回复
nice, is it on the same level as framer?
0
回复

@evrendombak Framer is still stronger as the community is bigger- more templates and components, more YouTube content. But I really think that in the long run, this is going to be a head on head.

0
回复
#17
Lunagraph
Your design canvas that writes code powered by AI
135
一句话介绍:一款AI驱动的设计画布,可直接生成真实代码,为设计师、创始人和工程师在同一个画布上协作、弥合设计与开发鸿沟提供了解决方案。
Design Tools Developer Tools Alpha
AI设计工具 设计转代码 实时协作 前端开发 Figma替代品 React组件 Tailwind CSS 产品原型 低代码 设计系统
用户评论摘要:用户普遍认可其“设计即代码”的核心价值,认为能简化流程。主要问题集中在学习曲线(非技术创始人)、对粗糙草稿的理解能力,以及对复杂交互(如滚动、视差)实现细节的询问。开发者关注生成代码的可合并性。
AI 锐评

Lunagraph的野心不在于成为另一个Figma,而在于成为“设计-开发”工作流的终结者。它直指当前AI辅助设计工具的致命伤:在“提示与祈祷”之后,设计师仍无法进行像素级的精确控制,工程师仍需手动重建。其真正价值并非“AI生成代码”,而是构建了一个**以真实代码为底层、AI为协作者的可视化操作环境**。

这带来了双重颠覆:对设计师,它降低了直接操作代码的门槛,让AI从“黑盒生成器”变为“可精确调校的合作伙伴”;对开发者,它承诺交付可合并的、基于成熟体系(如React、Tailwind、shadcn)的代码,而非待翻译的静态标注。产品标语中“Powered by AI”的表述可能弱化了其更深层的革新——**“Code as the Source of Truth”**。画布上的每个元素都是可即时检验、符合生产标准的代码实体,这从根本上改变了团队协作的“信源”,有望消灭因格式转换和解释偏差导致的损耗。

然而,其挑战同样尖锐。它将设计工具的专业门槛从视觉规范部分转移到了前端工程规范。评论中关于学习Tailwind和shadcn的讨论印证了这一点:它可能更受“设计工程师”或“强技术背景创始人”的青睐,而纯视觉设计师可能面临新的学习曲线。此外,在Alpha阶段缺失的交互设计能力(如拖拽)是其与成熟设计工具体验差距的关键。能否在保持代码纯净度的同时,提供不逊于Figma的流畅、直观的设计体验,将决定它是成为一个小众的先锋工具,还是一个真正的范式颠覆者。它的出现,标志着“设计工具”正在从“模拟代码”走向“成为代码”的新阶段。

查看原始信息
Lunagraph
Lunagraph is a design canvas — like Figma, but everything you add is real HTML, CSS, and React. Hand-craft UIs from scratch with granular control, or ask Claude to make sweeping changes. Designers, founders, and engineers all work on the same canvas.

Hi Product Hunt! Excited and a little nervous to share Lunagraph on Alpha Day.

This is genuinely early. I'm sharing it now because I want feedback before I keep building in the wrong direction.

Lunagraph is a design canvas, like Figma, but everything you add to the canvas is real HTML, CSS, and React.

It's for designers, but also for everyone else on the team.

  • If you're a designer, you've probably been trying Claude or Cursor and feeling handicapped. No canvas, no controls, can't tweak padding with a click, just prompting and praying.

  • If you're a founder, you've been using Claude for design because Figma is just hard for you to use.

  • And engineers, meanwhile, are stuck rebuilding mockups and tweaking by hand.

You can hand-craft UIs from scratch with granular control over every value, or ask Claude as your creative partner to do big sweeps of change and make variations you can tweak. The components are real React components, like shadcn. The colors and spacing come from your actual design tokens on Tailwind. The code that ships is the code you designed.

What works today:

  • Design from scratch with real HTML or React components: divs, text, shadcn, etc.

  • Use Claude side-by-side to remix screens, apply a design system across a flow, or generate variations.

  • Customize shadcn components directly in the canvas.

  • Hand off real code to engineers. No Figma files, no annotations, ready to ship.

  • Founders, product, and sales can duplicate and remix existing designs without bugging the design team.

What's still rough (because it's alpha):

  • There's no onboarding. You'll probably need me to walk you through your first session, and I want to, so reach out.

  • Still working to reach parity with Figma's canvas and shortcuts.

  • You can't drag components in yet. Please click to add them to the canvas.

  • No drag for absolute positioning yet. Please use Top, Left, Bottom, Right.

  • You can use Claude Code Chat to pull components from your codebase into the project. I'm still figuring out the right approach to work between codebase and design system.

Pricing

Free. I'm not pricing this until I know what people are actually using it for.

What I need from you

  • If you're a designer: try building one screen from scratch and tell me where you got stuck. That's the most useful thing in the world to me right now.

  • If you're a founder or PM: try the chat to remix an existing screen and tell me if the output felt usable or janky.

  • If you're an engineer: look at the code Lunagraph produces and tell me if you'd actually merge it.

I'm reading every comment today and I'll reply to all of them. The whole point of Alpha Day is the feedback loop, so let's actually do it.

Big thanks to the small group who's been testing this in the closed alpha. You know who you are.

See you in the canvas.

9
回复

@putrikarunia Hi. You draw on canvas and it writes code, what if my sketch is super rough, does it still understand?

2
回复

Wow such a cool idea. Small question, being a non tech founder how would rate the learning curve for this as compared to figma (m ok with figma as of now)

2
回复

@gamifykaran Should be similar to Figma! The only thing is that if you want to use Shadcn components or Tailwind classes, you kinda need to know tailwind and how to compose Shadcn components ( but you can always just copy paste from their documentation). And being familiar with CSS would help, but not necessary.

Plus there's Claude Code to chat with on the left sidebar, so you can create UI and ask for guidance if you can't find the right way to style something.

3
回复

I like it, does it work with TailwindCSS?

1
回复

@bengeekly Yess it has tailwind out of the box, you can add p-2 etc on the right sidebar and even write any tailwind classes as well (like hover:bg-blue-500)

and you can ask chat (claude code) to help you update design colors and vas and it will literally update the globals.css in the lunagraph project + it can make a quick mock of all your colors and vars in the canvas to view easily

1
回复

Very cool! How would I go about building more complex UX (scrolling, parallax, etc). If it did that it would be way better than Figma!

1
回复

@stefano_delmanto yeah you can edit all CSS and Tailwind on your designs, or ask Claude Code on the chat to help you. All interactions and scrolling works on the canvas!

0
回复
Super cool insight that figma as a design layer isn’t that necessary anymore. Amped to see where this goes 🤙🏻
1
回复

@jake_schonberger1 Yess, code on the canvas makes everyone's life easier :)

0
回复

I have been following Putri's journey since Typedream, when I got the opportunity to test Lunagraph I was amazed by what she and Anthony have created! I use AI a lot in my workflow, but the lack of a design founders take on all these tools puts designer's at a disadvantage as everything is built around developers - Lunagraph is bridging that gap from design to code, while still keeping the design workflow intact and honestly impressed by the product and will be using it!

1
回复

@mrnick_buzz thank you Nick!! Super excited to see what you build on Lunagraph and new workflows you're discovering :)

0
回复
#18
Plow
Openclaw on your Mac, with permissions you can understand
132
一句话介绍:Plow是一款为Mac用户提供的沙盒化、易安装的OpenClaw客户端,解决了原生OpenClaw配置复杂、权限不透明导致用户难以使用和信任的痛点。
Productivity Artificial Intelligence Alpha
AI助手 Mac应用 沙盒安全 一键安装 开源客户端 用户协作开发 权限管理 生产力工具 alpha测试 低门槛AI
用户评论摘要:用户普遍赞赏其简化安装和沙盒安全设计,有用户分享其提升个人工作流程的具体用例。主要问题集中于能否覆盖现有OpenClaw安装,以及对权限管理颗粒度的询问。开发者积极回应,确认权限隔离于特定文件夹。
AI 锐评

Plow的本质并非技术创新,而是一次精准的“体验外科手术”。它瞄准了开源明星项目OpenClaw高达35.2万星却难以转化为实际用户的巨大断层——这断层由复杂的本地部署和令人不安的权限风险构成。产品将“沙盒”作为核心卖点,是极高明的策略,它转换了叙事:从不透明的、需要技术信仰的“信任开源代码”,转变为可视化的、符合直觉的“控制文件访问”。这直接击中了专业用户最后的心理防线。

然而,其商业模式和长期价值存在深层拷问。以“协同开发”之名招募付费alpha用户,更像是一种社区预热与现金流测试的混合体,定价策略(第7位7美元,第83位83美元)充满了游戏化营销意味。其真正的挑战在于,一旦解决了安装与初始信任问题,产品是否会沦为单纯的“安装器”?它的护城河是短暂的便利性,还是能构建出超越原生OpenClaw的、独特的交互层或生态?评论中用户自发的使用场景分享(如下班复盘、任务整理)揭示了更深层需求:用户需要的或许不是一个更安全的OpenClaw,而是一个更懂场景、更“无感”的AI工作流引擎。Plow若止步于安装与沙盒,则价值天花板清晰可见;若能以此为基础,构建一个让非技术用户也能轻松组合AI技能的“乐高平台”,方有可能从开源项目的“搬运工”蜕变为新价值的“定义者”。当前,它聪明地找到了一个裂缝,但尚未证明自己能开凿出一条新航道。

查看原始信息
Plow
OpenClaw has 352k GitHub stars, yet many never get it running on their machine. We fixed that. Plow is an easy-to-install OpenClaw, where your data is firewalled behind a sandbox. If you've been wanting to use OpenClaw on your Mac but aren't quite sure how to do that, we're here to help. We're looking for our first alpha customers to work with us and co-develop this product. 100 alpha spots. Spot #7 is $7. Spot #83 is $83

Hi everyone! Plow is pretty simple: Sandboxed Openclaw on your Mac, installed in seconds. If you've been wanting to try OpenClaw but aren't sure where to start, this is for you.

We are looking for 100 users to co-develop this project with. All alpha users get access to the Plow engineering team, dedicated to getting OpenClaw running on your Mac.

4
回复

@sodio Judging by the video, it's a piece of cake to figure it out!))

2
回复

setting up my openclaw was a crazy painful experience. will try to get my parents to use openclaw using Plow

1
回复

The first time I installed OpenClaw it took me about 40 minutes, and by the end I still didn’t really know what to do with it. And even once it was set up, it lived in Telegram, which I never use, so I ended up forgetting about it entirely.

With Plow I was up and running in under a minute, texting my agent in imessage right away.

My favorite skill I’ve set up: midday it asks me what time I’m signing off. At that time it pings me a reminder, asks for a brain dump, and I just voice-to-text everything. What I did, what’s still rattling around, what I’m picking up tomorrow. Next morning at 7:30 it sends me an organized list.

The first time I ran it, Plow searched my Slack after my brain dump and surfaced a task I had completely forgotten I finished and added it to the list. It was a small thing but weirdly satisfying!

Curious what others would build. What’s the first skill you’d set up?

1
回复

I already have OpenClaw installed can I install Plow on top of it, or Plow needs a fresh install ?

0
回复

Really excited to finally share this. The whole idea started because we kept seeing people bounce off OpenClaw during setup. Plow handles all of that so you can just start using it.
Would love feedback from anyone who tries it!

0
回复

been wanting to try OpenClaw but the setup always looked intimidating. sandboxing approach makes sense for something this powerful - you don't really know what it's accessing until you're deep in the weeds. how granular do the permissions get? can you see exactly which files it's touching?

0
回复

@piotreksedzik yes you can. Openclaw only has access to files that are in your ~/Plow folder - so you have full control over what files it can access.

0
回复

The sandboxing angle is smart. A lot of people bounced off OpenClaw not because they didn't want it but because the setup felt risky on a personal machine. Removing that friction is the right call. We're in the same neighbourhood today with Grass, letting developers run Claude Code on a cloud VM instead of their local machine. Good luck with the alpha.

0
回复
#19
ReminderOS
Reminders that keep up with you
128
一句话介绍:ReminderOS是一款通过“预提醒”和灵活调度系统,在健身、服药、事务跟进等日常场景中,解决用户因单次通知易被忽略而无法真正落实任务的痛点。
Task Management Calendar Alpha
效率工具 智能提醒 任务管理 预提醒机制 习惯养成 跨设备同步 无账号设计 灵活排期
用户评论摘要:用户普遍认可“预提醒”概念,认为其实用性强,尤其对健身准备等场景表示共鸣。主要疑问集中在是否支持Siri创建、是否具备习惯学习能力,以及对“预提醒”与“子任务”功能定义的探讨。
AI 锐评

ReminderOS看似是拥挤的提醒应用市场中的又一个入局者,但其切入角度精准地刺中了现有产品的软肋:通知与执行之间的断层。它没有追逐“AI智能”的宏大叙事,而是聚焦于一个被忽视的微观逻辑——许多任务的失败,并非源于遗忘,而是源于准备不足或即时状态不适。

产品将“提醒”拆解为“准备”与“执行”两个阶段,通过可配置的“预提醒”机制,在心理和时间上为用户搭建了一个执行缓冲区。这本质上是将项目管理中的“前置依赖”思想微型化、日常化。其价值不在于通知的“智能”,而在于对人性弱点的“体贴”设计:它承认用户会拖延、会准备不周,并提供了一种结构化而非说教式的补救流程。

然而,其深层挑战也在于此。这种设计可能将简单事务复杂化,对轻量用户构成使用门槛。评论中关于“习惯学习”的提问,恰恰反映了市场对“自动化”的期待。ReminderOS当前选择做一款“谦逊的工具”,通过灵活排期和iCloud同步保障基础体验,是务实的。但其长远发展需思考:在用户定义了大量预提醒规则后,产品能否从中提炼模式,主动优化提醒策略,实现从“可配置工具”到“贴心伙伴”的进化?否则,它可能仅成为效率热衷者的玩物,难以触动更广泛的懒人市场。

查看原始信息
ReminderOS
Never miss what matters with flexible schedules, one-tap snooze and reminders that stay in sync across your devices.

Nice idea! This feels much more practical with the follow-ups

2
回复

@nat_lasica Hello Paul 👋
I like the idea of reminders that actually help you follow through instead of just notifying once. That pre-reminder concept makes a lot of sense

1
回复

@nat_lasica Congrats on launching 🎉. The gym example really clicked for me. The preparation reminder is often more important than the actual task.

1
回复

this is really cool! can I set up these reminders by asking Siri?

2
回复

@naveensharma Thank you! Creating reminders with Siri is a work in progress!

0
回复
Hey Product Hunt 👋 I’m Paul, and I’m excited to launch ReminderOS today! Most reminder apps do the same thing: they notify you at a time you chose, and assume that’s enough. In reality, that’s usually not how things get done. A few examples from how I use ReminderOS: - I take vitamin C + D every morning. I’ve got a short heads-up before the actual reminder so I don’t just dismiss it and move on. - If I need to return something, I star the email and it becomes a reminder. - For the gym, the useful reminder isn’t the workout — it’s the one before it that tells me to pack my bag and get ready. That’s the idea behind ReminderOS- not just “remind me at this time” but “help me actually follow through”. You can keep things simple, or get very specific with schedules (every 3 days, certain weekdays, etc.). Everything syncs via iCloud, so no accounts and no tracking. I didn’t set out to build a reminders app, I just wanted something that works properly day to day. How do you find reminder apps? What's working and what's not working?
1
回复

@paul_waweru1 Hi. Reminders that “keep up with you”, does it actually learn my habits or just ping more often?

2
回复

is it follow ups or sub-reminders? sub-reminders could be really effective actually

1
回复

@theapricotapp Hey! It's "pre-reminders" that you can configure, for instance 30 mins or 15 minutes before the main alarm, so it helps with being prepared before the main alarm arrives!

0
回复

I love the multiple reminders! Thats whats missing from my google calender/iphone notifs!

1
回复

i mostly use reminder for work thing (and for that i use apple reminder and so far so good) but yeah loved the thought and idea behind it, we all need 1 extra push sometimes

1
回复

Love the idea of reminding before the reminder !! that’s actually what makes things happen in real life. Most apps assume one notification is enough, but it rarely is. Congratss !! will definitely try it

0
回复
#20
Chaterm
Deploy, fix, and automate your infra in one terminal
123
一句话介绍:Chaterm是一款AI原生终端,允许SRE和DevOps工程师使用自然语言描述目标,由其自动规划并执行从部署、诊断到回滚的完整基础设施运维工作流,解决了复杂基础设施操作门槛高、知识传承难及重复劳动多的痛点。
Developer Tools Alpha
AI原生终端 基础设施即代码 DevOps自动化 SRE协作者 自然语言运维 智能工作流 知识库技能化 开源工具 跨平台 SSH集成
用户评论摘要:用户普遍认可其“从意图到执行”的核心价值,特别是“可复用Agent Skills”能将专家经验转化为团队资产。关注点集中在与实际技术栈的集成、跳板机等安全环境适配性、移动端语音输入的实用性,以及其执行可靠性是否足以改变团队协作方式。
AI 锐评

Chaterm的野心不在于成为另一个智能命令提示器,而旨在成为基础设施领域的“执行层大脑”。其真正的颠覆性在于两点:一是将自然语言界面从“建议”推向“可靠执行”,这需要产品在理解上下文、规划安全操作序列方面有极高的准确性,否则极易沦为危险的玩具。二是提出了“Agent Skills”这一知识载体概念,试图将运维中的“部落知识”和应急预案标准化、产品化,这直击了运维团队知识管理与人员依赖的核心痛点。

然而,其面临的挑战同样严峻。首先,在复杂、异构的生产环境中,AI代理的决策容错率极低,任何误操作都可能代价高昂。用户评论中隐含的对“可靠性”的追问,是它必须用实际表现回答的首要问题。其次,它游走于“增强现有工具链”与“创建新标准”之间。深度集成与安全合规性(如评论提及的跳板机支持)是落地关键,若仅作为松散的外挂助手,其价值将大打折扣。

从趋势看,Chaterm代表了AI向IT运维核心纵深切入的尝试——从辅助分析走向控制执行。它的成功与否,不仅取决于其技术成熟度,更取决于能否在运维团队最重视的安全、可控、可审计方面建立起坚实的信任。如果它能跨越这些鸿沟,才可能真正实现其“让每个开发者都拥有SRE超能力”的愿景,否则,它可能只是又一个在边缘场景试水的有趣实验。

查看原始信息
Chaterm
Chaterm is the Claude Code for SREs and DevOps — built for real infrastructure. Describe your goal, and let Chaterm execute it end-to-end — from deploy to diagnose. It transforms team knowledge into reusable Agent Skills, automating complex workflows and removing repetitive work across your infrastructure.
Hi Product Hunt 👋 I'm Walter, founder of the open-source project Chaterm, and an SRE with over 10 years of experience at INTSIG PTE, an AWS Advanced Partner. In my previous roles, we managed tens of thousands of servers, dozens of Kubernetes clusters, and hundreds of databases. One key challenge was helping engineers ramp up quickly in such environments. That’s why we built Chaterm — an AI-native terminal for cloud infrastructure management that bridges intent and execution. Instead of memorizing complex CLI flags or digging through documentation, you simply describe your goal in natural language. Chaterm understands your infrastructure topology and autonomously plans and executes workflows—from multi-cluster deployments and anomaly diagnosis to automatic rollbacks. Our core philosophy: ● From Commands to Execution: Let AI handle the heavy lifting of planning and executing complex tasks. ● Reusable Agent Skills: Turn your team’s expertise into safe, reusable skills anyone can run. ● SRE Superpowers for Everyone: Lowering the barrier, giving every developer SRE-level execution. We’re excited to share Chaterm with the PH community and would truly appreciate your feedback. We’ll be here all day answering any questions and discuss ideas. 🎁 Product Hunt Launch Bonus: Use code PH2026 for a 3-month Pro trial. 👉 Explore Chaterm: https://github.com/chaterm/Chaterm Thanks so much for your support — and special thanks to our hunter Chris Messina 🙏
13
回复

Thanks to Chris for the recommendation.and thanks to our team's developers: Allen, Ivar, David, Remulic, Diann, Levi, Vagt, and Neddy.

4
回复

@jarvishappy Really like this framing — “from commands to execution” hits hard.

Infra has always been powerful but inaccessible. If Chaterm can truly bridge intent → execution reliably, this could fundamentally change how teams interact with their systems.

Congrats on the launch 🔥

5
回复

@jarvishappy Congratulations! And also, thank you very much to our hunter, Chris.

2
回复

As the maker of Chaterm, I built this because I felt the terminal experience hadn’t evolved enough for modern AI-native workflows.

Chaterm is an AI-powered terminal that helps you move faster without losing control:

- Smart command completion with context

- Multi-device and SSH-friendly workflows

- Built-in AI Agent capabilities for real tasks, not just chat

This is just the beginning, and I’m building it closely with user feedback.

Would love for you to try it and tell me what to improve next.

Thanks for checking it out and supporting us on Product Hunt!

7
回复

@yu_zhou8 Nice Job!

1
回复

Cool! manage Servers and K8s clusters using natural language.

4
回复

@min_zhou A big thank you to Min and Capy for providing such extensive support and assistance during our product development phase!

3
回复

@min_zhou Couldn't agree more

1
回复

As an AI-native terminal product, Chaterm has also launched a cross-platform mobile version(Android/IOS/Harmonyos). For it, Whether you’re on the go or without carrying laptop, you can handle operation and maintenance tasks seamlessly anytime, anywhere. When typing commands isn’t convenient, you can even finish SRE&OPS tasks simply with your voice input. We aim to deliver users a simple, efficient, and powerful experience.

3
回复

@linda_vagt that's great !

1
回复

Nice shot for automating dev ops! How does Chaterm integrate with other components of tech stack btw?

3
回复

@cruise_chen Thanks a lot! Great question.

Chaterm integrates with the stack at the workflow layer, so teams can adopt it without heavy migration:

- SSH-friendly for remote servers and multi-environment operations

- Can fit into CI/CD and infra workflows as an execution assistant (instead of replacing your toolchain)

- Designed to stay composable with the tools you already use

Our philosophy is to augment your current stack, not force a new one.

1
回复

Hi PH folks! Chaterm is an open-source AI-native terminal and SRE Copilot. Manage complex infrastructure with simple natural language, enjoy faster AI workflows while staying in control. Try it, share feedback—your support means a lot :)

3
回复

@ninghui_yu Thanks to Neddy for preparing so much for this lanuch.

2
回复

@ninghui_yu Thank you for Nedy's support. Feeling really excited to put it out in public!

1
回复

It truly brings large language models into real-world DevOps workflows. From troubleshooting and log analysis to handling daily operational tasks, it significantly boosts efficiency—making operations smarter and less about just typing commands.

3
回复

@dingdingdingyinyinyin A big thank you to Diann—the only female developer on our team. Thanks to your contributions, Chaterm is able to become even better!

2
回复

@dingdingdingyinyinyin Thanks Diann 🙌

1
回复
Really like the focus on execution, not just suggestions — that’s what DevOps tools often miss.
3
回复

@ibitekukie 
Thanks Chenyue!

2
回复

@ibitekukie Really appreciate this — that’s exactly the gap we wanted to close.

1
回复

Every team has that one engineer who knows how to fix everything in prod. When they go on vacation, everyone panics. Turning that knowledge into reusable skills is the real feature here.

2
回复

@kailesk_khumar Totally agree, we’ve all been there.

Our goal with Agent Skills is to turn that hero knowledge into something the whole team can safely reuse. No more single points of failure😄

1
回复

Wow, Chaterm. love the idea of an AI-native terminal built for real infrastructure

2
回复

@janicelewis00 Grateful to Janice and the AdFox team!wishing AdFox continued growth and success!

1
回复

As one of the developers behind Chaterm, I’m truly honored to be part of this project.
We’ve put a lot of thought into it and refined many details along the way, hoping it will be more than just a new tool and genuinely help people in real-world workflows.

2
回复

@remulic Let’s keep listening, iterating, and making Chaterm genuinely useful where it matters most.

1
回复

@remulic The conversational input and output features on mobile are really cool!

1
回复

I’d highly recommend everyone to try the built-in Jumpserver asset integration.

Most AI terminal tools can’t really operate within bastion-managed environments, but Chaterm bridges that gap nicely.

This directly addresses a real pain point for ops teams working with secured infrastructure.

Small feature, but makes a big difference in real-world usage.

2
回复

@david1986 very interesting

1
回复

@david1986 Both Jumpserver and AWS EICE are practical plugins!

1
回复

Built for real operational scenarios, Chaterm is an AI-native terminal. It focuses less on isolated commands and more on helping multi-step, context-heavy tasks keep moving. In practice, that often matters more than making any single command better.

2
回复

@rvarbob Thank you — this means a lot.

1
回复

@rvarbob Nice job, Ivar!

1
回复

Been waiting for something like this. We run a bunch of K8s clusters at Delos and onboarding new devs on infra is always painful. The 'Agent Skills' concept is what makes this different from just another AI terminal — turning tribal knowledge into reusable workflows is huge. Trying it today.

1
回复

@pierre_de_la_grand_rive Thanks so much — that’s exactly the problem we’re trying to solve.

Would love to hear your feedback after trying it.

1
回复