Product Hunt 每日热榜 2026-05-03

PH热榜 | 2026-05-03

#1
Radar
The missing open-source Kubernetes UI
319
一句话介绍:Radar 是一个开源、本地优先的 Kubernetes UI,通过实时拓扑、资源管理、Helm/GitOps 集成和 AI 代理接口,解决了工程师需要在多个终端、仪表盘和云控制台间切换才能完成日常集群操作的割裂痛点。
Open Source Developer Tools Artificial Intelligence GitHub
开源 Kubernetes UI 本地优先 容器管理 Helm GitOps 集群审计 实时流量 AI 代理 MCP
用户评论摘要:用户高度认可集群审计(31项检查)带来的效率提升,但希望支持自定义检查注入。另一核心关注点围绕MCP的权限边界,团队回应其非破坏性设计(只读+可控操作)并通过RBAC继承用户权限。也有用户称赞单二进制部署消除了平台团队审批的摩擦。
AI 锐评

Radar 的出现,本质上是 Kubernetes 工具链“一体化界面”这一老问题的新解,但它的差异化不在功能叠加,而在架构哲学。当前市场上的开源自建方案,要么是重客户端(Lens/FreeLens),要么是浅层看板(Headlamp),要么是终端粘性工具(k9s),而 SaaS 方案则要求账户、节点计价和信任授权。Radar 选择的路径是“本地优先、单二进制、零账户”,这精准击中了两个痛点:一是平台团队与业务开发之间的信任鸿沟——部署一个集群内工具往往需要漫长的审批流程,而本地 kubeconfig 让工程师获得即时可见性;二是运维复杂度的感知门槛——将实时流量、Helm diff、成本洞察、安全审计等渐进式深度功能整合进同一UI,降低了从新手到专家间的认知跃迁成本。

值得关注的是 MCP(Model Context Protocol)的引入。这不是炫耀技术,而是为 Kubernetes 操作赋予了一个可被 AI 代理安全调用的抽象层。通过非破坏性设计和 RBAC 继承,Radar 实际上创建了一个“安全且可编程的运维接口”,这将可能改变运维人员与 AI 协作的模式:AI 不再是只读助手,而是能在权限边界内执行重启、扩缩容等操作。这种设计比直接用 kubectl + LLM 的方案更可控,也更接近企业级采纳的前提。

不过,Radar 的价值仍面临现实考验——当集群规模增长、涉及多租户隔离和复杂网络策略时,单二进制模式是否能维持性能而不退化?自定义审计规则的缺失、核心功能(如日志聚合、告警规则管理)对原有工具的依赖是否会成为下一次“版本割裂”?以及,在 Kubernetes 生态已有大量头部商业产品(如 Datadog、Grafana)深度布局的背景下,Radar 的社区驱动力能否支撑起长期迭代的野心?这些都是需要持续观察的变量。总体来说,它是一款少见的、兼具设计美感与工程判断力的开源产品,但距离“替代所有现有工具”的目标,还有一段扎实的补全之路。

查看原始信息
Radar
Radar brings your Kubernetes workflows into one fast, open-source UI: real-time topology, resources, events, Helm, GitOps, live traffic flows, security & best-practice checks, image filesystem inspection, and MCP for AI agents. Run it locally as a single binary or self-host it in-cluster with RBAC + OIDC — no account, agents, or cloud required.

Hey PH 👋 Eyal, Roy, and Nadav here - the team behind Radar. We also build Skyhook, YC W23.


We've wanted a better Kubernetes UI for a long time. kubectl is powerful, but day-to-day cluster work still ends up split across terminals, dashboards, Helm, Argo/Flux, cloud consoles, and log tools.


The existing options all have tradeoffs. Lens lost the OSS trust that made people love it. FreeLens is a welcome fork, but still carries the same heavy Electron desktop model. Headlamp is useful, but shallow once you want deeper operations - Helm, GitOps, traffic, audits. k9s is excellent if you live in the terminal, but not everyone does. And the SaaS tools often price by node and ask for a work email before they let you look at your own cluster.

So we built the Kubernetes UI we wanted: fast, local-first, open source, and not locked behind an account. We quietly shipped it a couple of months ago. The community took it past 1.4k GitHub stars and gave us way more feedback than we expected, so we kept shipping. Today is the proper launch.

What's in it:

- Topology with real ownership chains, not force-directed spaghetti

- Live event stream across all resources using Kubernetes watches, not polling

- Helm release management with diff/rollback + native Argo CD / Flux sync

- Live traffic flows via Hubble/Cilium, Caretta, or Istio

- Cost insights via OpenCost - auto-detected per namespace, workload, and node

- Cluster audit - 31 checks across security, reliability, and efficiency

- Image filesystem viewer - read container files in the UI, no exec, no pull

- Built-in MCP server - point Cursor or Claude at your cluster


Plus first-class integrations for 20+ popular K8s tools - Argo Rollouts, Karpenter, KEDA, cert-manager, Trivy, Kyverno, Velero, Knative, and more.


Single Go binary. Apache 2.0. No account required. No usage tracking. No cloud dependency.


Site: https://radarhq.io

Repo: https://github.com/skyhook-io/radar

Discord: https://radarhq.io/community/chat


Also yes, we cared about making it beautiful. K8s tools don't have to look like punishment.


Would love your feedback - what's missing, what breaks, what we got wrong. We're here all day.

8
回复

@nadav_erell Finally! k9s is still my go-to, but as you said, most people may want a real GUI. Nice product!

0
回复

a cluster audit with 31 checks across security and reliability is a massive value-add for day-to-day ops. we usually run separate trivy or kyverno reports, so having that integrated into the primary ui workflow is a huge time-saver. does the audit allow for custom check injection? @nadav_erell

3
回复

@vikramp7470 Thanks! Not yet, but definitely something we can consider.
If you have any specific checks you think are missing that could be very fast to add, we tried to balance and not go overboard spamming too many, so real things don't get lost in the noise.

1
回复

Looks very useful, sharing it with my team

2
回复

@surya_oruganti1 thank you! Would love to get their feedback

0
回复
Was actually just looking for sth like this. Was about to build an internal shoddy version, this will do!
2
回复

@jalcantara You deserve better than shoddiness :)
We basically built this because none of the existing options really did what we wanted well enough. Surprising that this is the case for k8s in 2026.

0
回复

nice - gave it a star! good luck!

2
回复

@nikolas_dimitroulakis thank you, much appreciated!

0
回复

Local-first with zero cluster-side installation is the right call. When I was scaling an engineering org from 15 to 120, the biggest friction with K8s tooling was always the chicken-and-egg problem: you need cluster access to install the tool that helps you understand the cluster. Having this run as a single binary using existing kubeconfig means any engineer can get visibility without needing platform team approval first. That alone probably saves a week of onboarding time per new infrastructure hire.

1
回复
0
回复

The MCP-for-AI-agents piece is the most interesting bit and the existing comments haven't poked at it. What can an agent actually do via Radar's MCP — read-only stuff (describe pods, fetch events, summarise an outage), or destructive ops (kubectl delete, rollout restart)? That boundary decides whether anyone runs this against a prod cluster.

0
回复

@sounak_bhattacharya Hi, Roy from the Radar team here. Good question!

We had your considerations in mind when building it. Boundary is "non-destructive by design." No delete, no force-uninstall, no --cascade=orphan.

Reads: dashboard, resources, topology, events, pod / workload logs, changes timeline, Helm releases. Outputs are minified and secret-scrubbed (Secret .data never returned, env values redacted, logs scrubbed for token shapes).

Writes are a curated, non-destructive set: restart / scale / rollback workloads, trigger / suspend cronjobs, sync / reconcile GitOps, cordon / drain nodes, and apply_resource with dry_run. Nothing that deletes.

The other half is RBAC. Calls go through K8s with the user's identity (impersonation in OIDC / proxy mode, the agent's ServiceAccount otherwise), so the agent inherits exactly your perms - a 403 from K8s is a 403 from MCP. And in OSS, MCP listens on loopback only.

Full breakdown at /features/mcp.

Would love to hear your feedback on this approach - and if you've got ideas for where the boundary should sit differently, very open to it.

0
回复
#2
PandaProbe
open source agent engineering platform
302
一句话介绍:PandaProbe 是一款开源的智能体工程平台,专为解决 AI Agent 在生产环境中难以追踪、评估、监控和调试的痛点,帮助开发者将行为可见性从“本地跑得通”提升到“完全理解生产状态”。
Open Source Developer Tools Artificial Intelligence GitHub
AI Agent观测 开源 智能体调试 追踪与评估 生产监控 LLM应用 开发者工具 质量评估 可观测性 工程平台
用户评论摘要:用户普遍认可该平台在调试长时自治Agent、应对轨迹级质量漂移方面的价值。核心关注点集中于:是否支持自定义追踪原始API调用、如何以低成本(异步/采样)处理主观质量滑坡与轨迹级评估的具体方法,以及与LangSmith等工具的差异化定位。
AI 锐评

PandaProbe切中的确实是当前Agent工程化的“硬核”盲区——大多数平台仍停留在提示词日志级别,而生产环境的Agent失败模式往往是跨时间、跨工具的轨迹级退化。创始人将学术论文(TRACER)直接转化为产品架构,选择从“完整会话观测”而非“单轮问答”切入,有很强的理论先发优势。但值得注意的是,该赛道已有LangSmith、Langfuse等成熟玩家,它们也正从日志向“智能体观测”演进。PandaProbe开源+云化的双轨模式虽能降低试用门槛,但真正的护城河在于:它能否让“评估成本低于推理成本”以及“轨迹级评估结果具备可操作的重现性”——否则极容易沦为一个漂亮的监控仪表盘。此外,用户对MCP、自定义API追踪的支持需求证明了其“混合架构”战略的正确性,但这意味着工程集成成本会陡增。总的来说,PandaProbe方向正确,但要在激烈竞争中立足,必须证明自己的评估体系和低成本方案不仅仅是营销话术,而是能真正取代开发者的“人工看日志”苦力活。

查看原始信息
PandaProbe
PandaProbe is an open-source agent engineering platform that gives you deep observability into AI agent applications. Use it to trace, evaluate, monitor and debug your AI agents in development and production.

👋 Hey Product Hunt!

I’m Sina, founder of PandaProbe.

Building AI agents is getting easier, but understanding and trusting them in production is still hard.

Once agents start calling LLMs, tools, APIs, MCPs, and sub-agents, logs aren’t enough anymore. You need to see what happened, why it failed, whether quality regressed, and how reliable the system is across full sessions.

PandaProbe is my attempt to solve this: an open-source agent engineering platform for tracing, evaluation, monitoring, and debugging AI agent applications.

The goal is simple: help developers move from “it works on my laptop” to “I understand production behavior, can measure quality, and continuously improve it.”

What PandaProbe provides

🔎 Trace — capture full agent executions as sessions, traces, and spans across LLMs, tools, agents, and custom logic.
📊 Evaluate — score traces and sessions using mission-critical, agent-specific metrics.
⏱️ Monitor — schedule recurring evaluations to automatically validate new traces and sessions in production.
📈 Analytics — track performance, cost, latency, errors, and quality trends over time.
🛠️ Open source + cloud — use the open-source core on GitHub or run PandaProbe in the cloud.

Who it’s for

🧑‍💻 AI engineers — debug agent behavior across LLMs, tools, and workflows.
🏗️ Platform teams — monitor quality, regressions, and reliability in production.
🔬 Builders experimenting with agents — understand failures and iterate faster.
🚀 Startups — add observability and evaluation before things become unmanageable.reason about.

Quick links

GitHub: https://github.com/chirpz-ai/pandaprobe

Docs: https://docs.pandaprobe.com

Cloud: https://www.pandaprobe.com/

I’ll be here all day answering questions and collecting feedback.

If you’re building agents today, what’s the hardest part to debug or evaluate?

Thanks for checking it out 🙏
— Sina

4
回复

Handling state and debugging for long-running autonomous agents is usually a nightmare, so having an open-source platform to standardize that workflow is huge. I can definitely see myself using PandaProbe to self-host my agent evaluation pipeline to keep sensitive client data entirely local. I am really curious to hear if you currently support custom tracing for raw API calls instead of just the standard frameworks.

3
回复

@y_taka Really appreciate that — and yes, democratizing observability and enabling teams to keep sensitive workflows fully self-hosted were big motivations behind making PandaProbe open source from day one.

And absolutely: we support custom tracing beyond standard frameworks. Alongside native integrations, PandaProbe also provides manual instrumentation APIs and decorators, so you can trace raw API calls, internal services, custom orchestration layers, or essentially any part of your agent workflow you want visibility into.

A lot of teams end up with hybrid architectures, so supporting low-level custom instrumentation was important for us early on.

0
回复

Evaluation is the hardest part of this whole space and most platforms hand-wave it. The failure mode that actually bites in production isn't crashes or schema errors. It's slow drift in subjective quality (voice, classification accuracy, output style) that only shows up when a human reads 50 outputs in a row. How does PandaProbe handle that in practice? LLM-as-judge with custom rubrics, human-in-loop on a held-out set, embedding-distance from a golden corpus, or something else? And how do you stop eval cost from outpacing inference cost when you're re-judging every trace?

1
回复

@vincentf This is actually one of the core motivations behind PandaProbe.

A lot of evaluation systems today focus on isolated outputs, but in production we kept seeing failures emerge as trajectory-level drift: looping, degraded tool grounding, coordination breakdowns, subtle quality regression, output-style drift, etc. The model can still sound confident locally while the overall session quality quietly collapses.

That led directly to a research paper I recently published called TRACER (Trajectory Risk Aggregation for Critical Episodes in Agentic Reasoning). The core idea is evaluating uncertainty and failure at the trajectory/session level rather than the individual response level.

That research became a major foundation for PandaProbe’s evaluation system and heavily shaped how we think about observability and longitudinal agent evaluation.

On the cost side, we’re also very conscious about evals becoming more expensive than inference. PandaProbe supports async and sampled evaluations, composable metrics, and lightweight structural trajectory signals so teams don’t have to run expensive judge models on every trace.

0
回复

Great pain to tackle, Sina. Good luck.

1
回复
@ardalan2 thanks for your support Ardalan. happy to hear your feedback if you adopt the platform.
0
回复

Really nice work. The gap between "it ran" and "I understand what happened" is enormous for agents and nobody's solved it cleanly yet. Rooting for you!

1
回复

@igorsorokinua Really appreciate that and I completely agree. That gap becomes painfully obvious once agents start interacting with tools, memory, APIs, and other agents in production.

A big part of PandaProbe’s vision is making agent behavior actually inspectable (like traditional software engineering) and understandable instead of feeling like a black box.

0
回复

Congrats on the launch and thanks for using mcp-use :)

1
回复

@pederzh thanks for the support Luigi. I'm a big fan of mcp-use :)

0
回复
Congrats on another great product going live! does it support MCP tool tracing natively or do you have to instrument those calls manually?
1
回复

@kate_ramakaieva Thanks for the support, Kate! Great question.

If you’re using one of our supported integrations for frameworks like LangGraph, CrewAI, and others, MCP tool calls are automatically captured and traced out of the box.

For custom agent architectures or internal tooling, we also provide lightweight manual instrumentation via decorators, so you can trace virtually any function, tool call, or workflow step in your agent logic.

0
回复

Where does PandaProbe sit relative to LangSmith, Langfuse, and Helicone? They all claim "agent observability" but mean very different things underneath — some are basically prompt loggers, others actually trace tool-call DAGs. Curious which problem you decided was the real one.

0
回复
#3
Huddle01 VMs
Virtual Machines for Your Agents
296
一句话介绍:通过集成MCP协议,用户可直接在Claude、Cursor等AI助手的聊天界面中一键创建、配置和管理虚拟机,大幅降低基础设施建设的技术门槛和操作时间。
Developer Tools Artificial Intelligence Development
云计算 MCP协议 AI基础设施 虚拟主机 开发者工具 低代码部署 智能运维 按秒计费 DevTools 无限制流量
用户评论摘要:用户对“AI聊天控制虚拟机”的便捷性表示认可(如节省时间、适合多Agent系统)。核心疑虑集中在:认证与花销控制(Agent循环导致资源浪费)、GPU实例支持、冷启动速度、以及配置错误带来的成本风险。同时有用户询问与Railway等现有方案的性价比对比。
AI 锐评

Huddle01 VMs打动市场的并非技术突破,而是交互范式的革新。它将云基础设施的“配置入口”从专业控制台转移到了自然语言界面,直接响应了AI开发者的核心痛点:写代码的能力有了,但部署和运维依旧是“认知断层”。其MCP原生属性是当前AI工作流中的稀缺资产,尤其适合“Vibe Coding”后迅速构建后端服务的场景。

然而,产品面临双重考验。其一,信任门槛高。用户的评论精准点出风险:Agent失控循环、配置失误导致费用飙升,以及冷启动延迟是否侵蚀按秒计费的优势。这要求Huddle01不仅提供API,更需内置预算锁、沙箱测试与异步确认机制,否则“便利性”会反噬为“灾难性体验”。其二,差异化护城河尚浅。AWS Lightsail、DigitalOcean等竞品同样可被MCP工具链调用,Huddle01的“70%便宜”只能作为短期获客手段。长期价值取决于:能否沉淀为AI Agents的“Infra-as-a-Dialogue”标准,并从单次创建演进为可编排的自动化运维管道,真正让AI接管成本优化、扩展与资源回收。

一句话总结:这是一个聪明的“入口级”产品,切中了AI基础设施的摩擦点。但革命性体验需以极致的成本可视性与安全锚点为代价,否则只会成为高级玩家的玩具,而非大众开发者的生产力基石。

查看原始信息
Huddle01 VMs
Huddle01 Cloud allows you to spin up a Virtual Machine (VM) from your favourite AI assistant now! The MCP server lets you control your infrastructure setup on Huddle01 just by chatting. Works with Claude, Cursor, Antigravity, or anywhere you can set up MCPs. Your virtual machines come with Unlimited Ingress, Per-second billing, and Unthrottled NVMe Storage.

Hey Product Hunt!

I am Ayush, founder of Huddle01 Cloud. Virtual Machines are an essential when it comes to taking your website or applications online. In last few months, developers and non-devs have been building their applications using AI assistants. Anyone who is not familiar with tech has to spend a lot of time reading through docs to setup their Virtual Machines to get the website published. 

So we decided to fix that. 

Huddle01’s MCP server allows you to access the Virtual Machines from your AI Assistants like Claude Code, Cursor, Antigravity and any tools that support MCPs. You just need to install the server with one line of code and then your chat can handle everything else. 

With this:

  • Beginners and non-developers can setup Virtual Machine instances from their AI assistant chats.

  • Developers and Builders can setup their agents to auto-deploy instances for the apps that agents create.

  • Check the already running instances and info about VMs without visiting the dashboard.

Huddle01 Virtual Machines come with dedicated AMD EPYC vCPUs, NVME storage and unlimited egress across global regions. 

Why Huddle01 VMs for your agents?

  • MCP native: We’re the first VM provider that allow you or the agents to just write in the chat and get the infra live. 

  • You don’t pay any brand tax. Just pay for what you use with no egress markup. This makes Huddle01 almost 70% cheaper than other hyper scalers. 

  • Only three steps setup an then you can get VMs by chatting anytime. 

How to use: 

  • Just go to get.huddle01.com and copy the code

  • Paste it in your Claude Code terminal, Cursor, Antigravity or any tool. 

  • Run it and you’re ready to get deploying from the chat 

If you’re building your first python project and don’t want to configure everything manually or you have a multi-agent system working that self deploys everything, Huddle01 has got you covered. 

You can leave feedback or ask questions to us in our Discord too. 

It’s time to get deploying with Huddle01 (huddle01.com). 

We’re here the whole day to answer all your questions!

17
回复

@ranjan3118 Huddle01 MCP feels like the way forward on how Cloud Products should feel like, everything will move MCP native going forward

2
回复
@itsomg This new workflow will save so much time for everyone!
0
回复

@ranjan3118 Huddle looks like a great step up to conventional coding assistants.

Thinking about security first, how does the MCP server handle authentication? If my agent goes into a loop, are there spending limits I can set to prevent token usage surprises?

Also, does it have access to root directories or we can create a VM/sandbox for it?

1
回复

Congrats on shipping!! Always exciting to see infra innovation happening.

3
回复
@roopreddy yup!! infrastructure is the next unlock for AI ans agents in general Excited to see what people build with it
0
回复
@roopreddy thank you! we appreciate the support
0
回复
@roopreddy Thank you so much, Roop! Excited to get your feedback!
0
回复

Congrats on your launch! I'm not very knowledgeable about virtual machines or why I would need one. My current workflow to publish my vibe coded apps is Antigravity => Github => Vercel. That seems pretty straightforward and simple.

What use case are you solving that can't be done with my workflow?

3
回复

@peterclaridge Hey Peter thats an awesome workflow, but as your apps will move to a more mature stage you will need a Backend server to Host your websites, your backend server and much more!!

We see people say deploying from discord bots to major analytics servers on VMs and easily configuring it using MCPs

2
回复
Congrats on the launch
2
回复
@german_merlo1 Thank you!
0
回复

@german_merlo1 Thank you so much!

0
回复
Congratsss guys 🔥
2
回复
@suhasmotwani thanks suhas
0
回复
@suhasmotwani thank you suhas!
0
回复
@suhasmotwani Thank you, Suhas! :)
0
回复

I've faced this problem myself, being confused about deploying side projects or getting my agent to do it. It's been incredible to see the team ship this in such a short time.

2
回复
@otodidakt_20 The devs are crazy shippers!
1
回复

Is there support for GPU instances as well?

1
回复
@zerotox yes GPU instances are alo natively supported - we took the concept from Perplexity to use CLI under MCP to expend its capabilities And our hudl cli always had these commands
1
回复

Nice! But how do you ensure cost control if agents keep spinning up instances automatically? 😅

1
回复
@iamanantgupta lol thats for sure was an issue with older models - but recent models have become very capable with skills about handle these waste provisions
0
回复

We had so much fun building VMs for Agents. Excited to see how people use it to deploy their apps!

1
回复
@krupali_trivedi MCPs are such an awesome hack to increase your shipping speed and decrease the time spent in spinning up VMs!
0
回复

Per-second billing only matters if spin-up is also fast — what's the cold-start time for a vanilla Ubuntu image, and does it stay flat as the image gets heavier (e.g. with a 2GB Docker layer baked in)? The economics break the moment startup is 90 seconds and I'm paying for warm-up.

0
回复
I was wondering if I deploy from an assistant, how can I manage the configurations? What if the configurations used by AI end up charging me more?
0
回复
I’m launching a Discord bot soon, would this be a good alternative to what I’m currently using, which is railway?
0
回复
@billchirico will be super easy and much cheaper to use Huddle
0
回复

@billchirico Would be awesome to get your feedback, Bill! In terms of cost, it would be way more economical. In terms of speed, it will be much faster.

0
回复
#4
Mockin 2.0
Ultimate career toolkit for UX/UI & Product designers
255
一句话介绍:Mockin 2.0 是一款专为UX/UI与产品设计师打造的求职全流程工具,通过上传简历获取真实市场反馈,提前识别并修复招聘环节中的潜在风险,从而提升面试邀约率。
Hiring Education Career
求职工具 UX/UI设计 产品设计 简历优化 面试准备 招聘反馈 职业发展 产品猎手 设计师工具
用户评论摘要:用户普遍反馈求职中“沉默拒绝”是最大痛点,期待Mockin能精准定位具体环节的失败原因。有用户询问是否覆盖其他岗位,团队回应已考虑扩展。还有用户建议增加白板面试与求职信练习功能。
AI 锐评

Mockin 2.0抓住了当前设计招聘市场中一个极其刁钻但真实的痛点:求职者被淘汰时往往得不到任何有意义的反馈。绝大多数求职工具做的是“表面抛光”——帮你改简历、练面试、谈薪资,但这些锦上添花的动作,如果选错了赛道或踩中了某些隐形的招聘红线,一切都是白费。Mockin的价值在于它不做“美化者”,而是做“诊断器”。它不帮你润色作品集,而是告诉你为什么你的作品集在HR眼里值不了面试机会。

从产品底层逻辑看,Mockin 2.0赌对了两个关键点。一是“行业垂直”。通用求职工具永远无法理解UX/UI设计师特有的“作品集叙事+案例研究+产品思维”这一套复杂的评价体系。Mockin之所以敢从最难的UX/UI领域切入,正是因为它有能力将晦暗不明的市场标准转化为可操作的标尺。二是“流程全栈”。它不是只解决简历一个问题,而是覆盖了从简历到HR筛选、再到面试、案例研究等整个漏斗。求职不是单点战役,而是一条锁链,Mockin试图堵住每一个可能导致断裂的环节。

不过,危险也在于此。“给出反馈”和“帮助改善”之间有一条巨大的鸿沟。如果Mockin的诊断只能告诉你“你的作品集叙事不够强”,但无法提供具体的重构路径或案例故事框架,那它本质上还是换了个马甲的“沉默拒绝”。此外,团队成员自曝有强烈设计背景,这决定了其对非设计角色的扩展不会轻松。一旦开始覆盖PM、工程等其他职能,产品将被迫稀释其最宝贵的专业深度。Mockin的未来不在于做“大”,而在于把UX/UI这一亩三分地刨到别人进不来的程度。

查看原始信息
Mockin 2.0
We once hit #1 Product of the Day with voice interviews. Now we’re back with a complete UX/UI career toolkit. Upload your CV. Get real feedback. Land your next UX/UI job.

Hi Product Hunt 👋

I’m Egor, co-founder of Mockin.

In the 9 months since our last launch here, the design job market got even harder.
After speaking with more than 60 designers, one pattern became impossible to ignore. Strong skills do not guarantee interviews. People get filtered out at every stage, often without understanding why.


Resume.
Portfolio.
Recruiter screen.
Hiring manager interview.
Case study.

One weak point is enough to lose momentum, and usually the only feedback you get is silence.

That is exactly why we built Mockin 2.0.

We turned Mockin into a tool that helps UX/UI and Product Designers see real hiring risks early, fix them before real interviews, and prepare across the full job search funnel based on real expectations from the market.


I’d love for you to try it and tell us what feels strongest, weakest, or still missing.

Thank you

10
回复
@egor_krasnoperov congrats on the launch. I’ll share your product with my designer friends 👌☺️
1
回复

Hey Product Hunt community! We significantly improved our app since the last launch. Appreciate your feedback on the updates and Mockin itself ♥️

4
回复

Thanks to the team for a great job!

4
回复

Andrey & team are awesome and always ship delightful products!!

3
回复

@suleimenov thank you for your kind words Arman

2
回复

@suleimenov thanks 🙌

1
回复

Congrats with launch! So, now all the features to land a next job is inside?

3
回复

@islam_midov looks like we're packed! But we were thinking of the cover letter

2
回复

@islam_midov thanks so much! Almost :)
We’re also considering adding whiteboard interview practice and cover letters next. So stay tuned!

2
回复

Guys that's great for designers! Will you go to other roles?

3
回复

@and_bayleaf great question! It's on our radar. Just wanted to make sure we did a great job for at least one role

3
回复

a only 'feedback you get is silence' line is the most painful part of the 2026 job market. You can have a world-class portfolio, but if you’re failing at the recruiter screen without knowing why, you’re just spinning your wheels. Excited to see how Mockin identifies those specific hiring risks before they turn into rejections. Support on the launch, @lipkovskiy Egor

3
回复

@vikramp7470 thanks a lot for the support! Really appreciate it.
And if you try Mockin, let me know what we can improve.

1
回复

Great product

3
回复

@madalina_barbu thank you

1
回复

Hi, congrats for your launch. Why did you started with the UI/UX niche. Any user feed back or based on personal evidance ? I used to have a very similar idea but for other roles. UI / UX designers are the hardest role to start with I guess.

2
回复

@ozgurds thanks for your question!


There are a few reasons. First, this is where I have the strongest expertise. For the last 9 years, I’ve been involved in hiring designers, interviewing candidates, reviewing portfolios, and also going through hiring processes myself. So I’ve seen this pain from both sides.

Second, UX/UI and Product Designers have a very specific hiring funnel. It’s not only about a resume. It’s also about portfolio quality, case study storytelling, product thinking, visual craft, communication, and interview confidence.

So yes, designers are probably not the easiest niche to start with. But that’s exactly why we started here. A generic career tool doesn’t really understand this process well enough.

2
回复
Congratulation with the release guys!
2
回复

@aleksanadr_lavrinenko thank you Alex! And appreciate your support

0
回复

Congratulations. And happy product launch. @lipkovskiy

0
回复

awesome launch, congrats!

0
回复

Most career-prep tools double down on the polish layer — portfolios, mock interviews, salary scripts — and skip the actual high-leverage decision, which is which role to take in the first place. I'm an Accredited Financial Counselor and the most common thing I counsel new grads on is the "safe offer vs. the role that builds the skill stack" tradeoff — the comp gap usually closes within a year if the second role is right. Curious — are designers showing up to Mockin pre-offer to make that call, or mostly post-offer for prep?

0
回复
#5
Rosentic
Catch when coding agents break each other before merge
163
一句话介绍:Rosentic在AI编程代理并行开发时,通过跨分支代码结构分析,在合并前检测出单一PR检查无法发现的语义不兼容问题——解决“各自测试通过、合并后崩溃”的痛点。
Open Source Developer Tools Artificial Intelligence
AI代理冲突检测 跨分支兼容性分析 代码结构分析 语义冲突 确定性分析 CI增强 合并前检测 无模型调用 GitHub Actions
用户评论摘要:用户关注“语义层冲突”而非文本冲突的检测机制(@avrisimon),开发者明确回应基于符号级结构匹配、不依赖LLM;用户质疑误报处理能力(@necipreis),回应称仅标记接口不兼容,侧写效应暂不处理;另有用户赞赏“确定性分析”的承诺。
AI 锐评

Rosentic切中了一个因AI代理泛滥而急剧放大的裂缝——当多个编码Agent同时作业时,传统CI的“单分支验证”方法论彻底失效。产品真正的聪明之处在于放弃了花哨方案:不用LLM糊弄(避免幻觉和不确定性),不重新发明文本合并(信任Git),直击“语义兼容性”这一关键空隙。本质上是“跨分支依赖图分析器”,通过解析代码结构中的符号契约(函数签名、路由、接口定义等),在合并前就预判各分支是否互相伤害。

从评论区的互动看,罗森蒂克对自身能力范围的声明相当克制——聚焦“结构契约”而主动忽略文本冲突和副作用变更,这非常专业,也减少了误报预期管理压力。但这也意味着其检测覆盖面有限:日志、配置、资源声明等非结构化变更的连锁反应无法捕获。对于真正复杂的多代理协调场景(如六七个分支交叉修改数据库Schema和对应查询方法),这个工具仍然只能当第一道筛网。

产品的商业逻辑可信:安装轻量(YAML+60秒),不上传代码(本地运行),无账单陷阱。但问题在于——仅靠一个GitHub Action插件建立护城河很难,一旦GitHub官方或大型工程平台(如Bitbucket、GitLab)下场做原生跨分支兼容分析,Rosentic就将面临功能同质化风险。另外,对于很多团队而言,“合并之前手动检查所有活跃分支间的兼容性”可能本身就不是高频需求,除非代理数量真正规模化(30+并行PR)。口号能吓人到CEO耳根子发软,但使用深度需要团队成熟度配合。

一句话辛辣总结:**它解决的是“AI多线程铺开工程后”工程师的第五层地狱,而真正地狱是——多数团队目前才刚走到第二层。**

查看原始信息
Rosentic
Rosentic checks every PR against every other open PR before merge. When coding agents work in parallel, they break each other in ways no single-PR tool catches. Rosentic catches it. Deterministic analysis. Same scan, same result, every time. Most scans come back clean. That means you're clear to merge. Runs on your infrastructure. One YAML file, no signup, 60-second install.

Hey Product Hunt 👋. I'm Laramie. Nearly 20 years in tech. By day I run technical partnerships. By night I build with Claude Code and Codex on the same repo.

Here's what I kept running into: both agents write good code. Both PRs pass CI. Then they merge and break main. CI checks one branch at a time. Git merges text, not logic. Nobody checks whether the branches are compatible with each other.

With agent orchestration tools shipping weekly and PR volume exploding, this is only getting worse.

So I built Rosentic.

It checks every PR against every other active branch before merge. Deterministic. Same scan, same result, every time.

Most scans come back clean. That means you're clear to merge. When something fires, you catch it before production does.

150+ repos scanned. Real conflicts found and fixed by maintainers. One YAML file, no signup, 60-second install.

What's the messiest merge conflict you or your team has dealt with lately?

https://github.com/marketplace/actions/rosentic-cross-branch-compatibility-check

9
回复

This is solving a problem that's about to hit every engineering team at scale. When I was CTO running 120 engineers, merge conflicts between humans were already one of our biggest velocity killers - now multiply that by AI agents working in parallel across the same codebase. The hard part isn't detecting the textual conflict - it's catching the semantic breaks where two agents make changes that individually pass tests but together introduce subtle regressions. Curious how you're handling that semantic layer versus pure git-level conflicts?

3
回复
@avrisimon Hey Avri great question. We don’t touch textual conflicts at all. Git already catches those. Rosentic analyzes the code structure on your own infrastructure and checks whether changes on one branch are compatible with what’s happening on other branches. So if one branch changes a function signature and another branch still calls the old version, we flag it with the exact file, line, and why it breaks. 120 engineers, I can only imagine how many branches were in flight. That must have been rough even before agents.​​​​​​​​​​​​​​​!
1
回复

"Deterministic analysis" is the line that earns trust here — what's the actual technique? AST-level diff, type-graph reachability, an SMT solver, something else? Asking because "deterministic" in this space sometimes means "we wrap an LLM and average," and the value is very different depending on which one it is.

0
回复
@sounak_bhattacharya No LLM anywhere in the engine. We parse the code structure, extract the symbols that matter, and do exact structural matching across branches. Same repo state, same result, every time. No averaging, no inference, no model calls. Every finding comes with the exact proof of why two changes are incompatible.​​​​​​​​​​​​​​​​
0
回复

Nice work. Narrow but useful problem. Curious how you handle false positives when two PRs touch the same surface for legitimately different reasons (e.g. coordinated multi-agent refactors). That's been the trickiest part of PR-conflict detection in our orchestration work.

0
回复
@necipreis The engine checks whether the actual usage is compatible, not just whether the same code was touched. If two agents both change the same function but the callers still match, it comes back clean. When it does flag something, it shows exactly why so you can decide fast. It’s not perfect and we’re always tuning. If you run it and see something off, I’d love the feedback.​​​​​​​​​​​​​​​​
1
回复
@necipreis That’s a great edge case. Right now we focus on the structural contracts – signatures, routes, schemas. Side-effect changes like metrics or logging that don’t show up in the function interface are outside scope today. We’d love to hear what you find when you run it. Those kinds of real-world cases are exactly what helps us figure out where to go next.​​​​​​​​​​​​​​​​
0
回复
#6
Aximote In-Car App
The fitness tracker for your car
134
一句话介绍:Aximote 是一款无需额外硬件的车载数据分析应用,通过在 Android Automotive 仪表盘上实时反馈行程、能耗、效率等数据,解决车主对车辆“黑箱”状态的不透明痛点。
Android Cars Electric Cars
车载分析 驾驶数据 实时反馈 能耗监测 充电洞察 行程追踪 Android Automotive 车联网 无硬件方案 Strava for cars
用户评论摘要:EV车主肯定其解决了能耗成本不透明的问题,并强调仪表盘直显比手机App更安全便捷。用户关心数据所有权及跨车辆迁移,建议增加CSV导出(已支持)。另有人希望加入冒险模式推荐风景路线。
AI 锐评

Aximote 的切入点足够精准——用软件代替OBD硬件,直击Android Automotive系统原生应用空白。其“车辆健身追踪器”的定位,本质上是将驾控体验数据化、游戏化,从模糊感知升级为可量化反馈。这种设计对追求精细化能耗管理的EV车主尤其有吸引力,也是避开传统OBD兼容性坑的聪明选择。

但冷静来看,目前产品仍有两个关键瓶颈:一是依赖Android Automotive生态,而该系统的装机量远未达到主流,用户规模受限;二是数据价值锚点模糊——“知道能耗”和“改善驾驶习惯”之间,缺乏闭环的激励或指导机制,长期留存可能面临挑战。用户评论中的数据迁移和导出诉求也提示:这类工具容易沦为一次性状态检查器,而非持续的互动社区。

标榜“Strava for cars”是个诱人的愿景,但从数据聚合到社区共建,需要的是横向兼容性(兼容燃油车、非AAOS车型)和纵向社交驱动力(排行榜、挑战赛、路线共享)。目前Aximote更像一个精美的数据仪表盘,距离真正的驾驶社交平台还有一段路。若能尽快打通跨品牌数据标准、加入驾驶行为评分和社区排行,其从“工具”跃迁为“平台”的潜力才可能兑现。

查看原始信息
Aximote In-Car App
Aximote turns your car into a transparent, data-driven system. Our new Android Automotive in-car app gives drivers real-time feedback on trips, efficiency, speed, consistency, energy use, charging, and costs, without OBD hardware. It is like a fitness tracker for your car, built directly into the dashboard.
Hi Product Hunt, We are excited to launch the Aximote In-Car App, our first step toward making vehicle data understandable, useful, and fun directly inside the car. 🚗 What is Aximote? Aximote is a driving analytics platform that turns your vehicle data into real-time insights. With our new Android Automotive in-car app, drivers can see feedback directly in the dashboard, including trip tracking, efficiency, speed, consistency, energy use, charging, and cost-related insights. 🧩 What problem are we solving? Modern cars generate a huge amount of data, but most drivers only get access to a tiny fraction of it. OEM apps usually show basic status information, while deeper questions remain unanswered. How efficient was this trip really? What driving habits increased consumption? How much did charging or refueling actually cost? How does one trip compare to another? For many drivers, the car still feels like a black box. We want to change that. ⚙️ Why did we build it this way? Existing solutions often rely on OBD dongles, manual exports, or third-party integrations. We wanted a more native and software-only approach. Android Automotive OS gave us the opportunity to bring analytics directly into the car, without requiring extra hardware, while working across manufacturers instead of being limited to a single brand. 🔮 Where are we heading? We want Aximote to become the community layer for driving data: a kind of Strava for cars. Drivers should be able to compare efficiency, consistency, charging behavior, and real-world performance across trips, routes, and vehicles, independent of the manufacturer. 🙌 We would love your feedback We are especially curious to hear from EV drivers, Android Automotive users, and anyone who has ever wished their car explained itself better. What would you want to understand better about your car or your driving behavior? — The Aximote team
5
回复

as an ev driver, the 'black box' feeling is real. manufacturer apps are notoriously bad at showing the actual cost-per-trip vs energy loss. being able to see energy use and charging insights directly on the dashboard instead of a phone app is a huge safety and ux win. @laurenz_hinterholzer

4
回复

@priya_kushwaha1 thanks a lot, totally agree on that.

2
回复

Quick question on data ownership: if I switch cars in 3 years, can I take trip history with me, or does it stay tied to that specific vehicle? And any plan for CSV export for mileage tax write-offs? Niche use case but it tends to be the thing that converts hobby users into paying ones.

2
回复

@sweepbase hi! Currently you can see the trip history per vehicle in the app but you can have multiple vehicles as well.

CSV export is already on board andwe are open for format suggestions 🙂

1
回复

Innovative idea – I haven't seen something like this on PH before. :)

1
回复

@busmark_w_nika thank you!

0
回复

Love the concept mate... Wish this was part of Google Maps. I'll absolutely give it a try on iOS.
1 tiny feedback on the website. I'd recommend adding a QR scanner on the bottom right of the website.

This would make it easier for folks on desktop to download the app.

Best of luck @laurenz_hinterholzer

1
回复

@richard_andrews4 thanks appreciate your feedback!

1
回复

Awesome idea! Would be great if you could add some kind of adventure mode for those who love driving but want an alternative / more scenic route for their regular routes.

0
回复
#7
IsraelVC
The cleanest Israeli VC map ever built
30
一句话介绍:IsraelVC是一款为以色列初创生态打造的精选风投机构目录,帮助创始人与投资者在信息嘈杂的市场中快速找到活跃、真实的风投基金。
Investing Venture Capital Database
以色列创投 风投目录 初创公司数据库 投资人工具 精选基金 生态导航 创业资源 无付费墙 实时更新
用户评论摘要:用户肯定产品“精简”了以色列创业生态。创始人强调解决“信号”而非“可见性”问题,并鼓励社区贡献缺失基金或修正旧信息,以保持目录的鲜活与准确。当前为V1版本,期待更多反馈。
AI 锐评

IsraelVC的“干净”并非一句空话,它直击了一个核心矛盾:以色列科技生态从不缺关注度,缺的是在泛滥信息中提取有效信号的效率。创始人拥有20年行业观察与10年投资经验,这让他能精准区分“活化石”与“僵尸基金”,比那些自动抓取的数据库更具心智判断力。没有付费墙、没有花哨交互,而是把体验压到“搜索-浏览-联系”这一极简闭环,背后是对创始人时间成本的深刻理解——他们不需要另一个“看起来很大”的数据库,而是需要一张“此刻该敲谁的门”的活地图。

但风险也很明显:此类社区驱动目录极易陷入“维护熵增”。即便当前是V1,若缺乏持续的数据审核机制和规模化运营,随着条目膨胀,筛选质量会迅速滑坡。目前靠创始人人脉和用户众包来保鲜,长期看,能否引入类似“活跃度评级”“投资者最近轮次记录”等动态信号,将决定它是成为常青工具还是又一份过时的通讯录。此外,产品目前完全依赖以色列地域性叙事,容易在跨境或非纯以色列标的的创业者中流失用户。一句话:这是一把精准的瑞士军刀,但能否升级为工具箱,还看后续迭代的深度与速度。

查看原始信息
IsraelVC
IsraelVC is a clean, curated directory of venture capital funds investing in Israeli startups. The goal is simple: make the Israeli venture ecosystem easier to navigate for founders, investors, and anyone tracking the market.
Long time Product Hunter, but first time I've posted in a while... I'm happy to share the launch of israelvc.com. After 20+ years of writing about the Israeli tech ecosystem and 10+ years of investing in Israeli startups, I’ve finally built something for our ecosystem. When I started VC Cafe in 2005, the challenge was visibility. Today, it’s the opposite. We don’t have a visibility problem. We have a signal problem. Founders are navigating a more complex, noisy, and fast-moving market than ever, yet still relying on outdated spreadsheets, fragmented databases, and guesswork to figure out who to talk to. So I built something simple: A curated, no-fluff, no-paywall directory of active VCs, CVCs, and micro-VCs investing in Israel. A few things that make it different: - Curated, not scraped (real, active investors) - Fast and simple to use - Open and accessible to everyone This has actually been a long time coming... I bought the domain back in 2007 (!), but only recently had the tools (and push) to finally build it properly. This is very much V1, and I’d love your help shaping it: - Missing a fund? Add it - Spot outdated info? Fix it - Have ideas? Send them my way If you’re a founder, I hope this saves you serious time. If you’re an investor, make sure you’re represented properly. Explore it here: https://www.israelvc.com Feedback and ideas on how to make it more useful are much appreciated 🙏
2
回复

@ediggs Awesome! Startup nation just got a little more streamlined 💪😉🇮🇱

0
回复
#8
TinyLottie
Smart Lottie optimization for high-performance SaaS.
18
一句话介绍:TinyLottie 是一款零上传、纯浏览器端的 Lottie 动画智能压缩工具,帮助设计师和开发者在保持高性能的同时,将动画文件体积减少高达 98%,解决 SaaS 产品因动画资源过大导致加载缓慢的痛点。
Design Tools SaaS Developer Tools
Lottie压缩 动画优化 dotLottie 浏览器工具 前端性能 SaaS工具 文件压缩 设计师工具 开发者工具 无损压缩
用户评论摘要:用户反馈集中在压缩质量和原理上。有用户因应用体积限制弃用Lottie,询问是否存在画质损失;另有用户追问“98%压缩率”是依赖坐标量化、删减关键帧还是转为二进制格式,并指出不同技术路线下视觉保真度差异明显。
AI 锐评

TinyLottie 在 Product Hunt 上以“AI 一周搓出”的故事吸引了眼球,但其核心价值在于精准切中了前端性能和动画丰富性之间长期存在的矛盾。18 票和寥寥评论与其宣传的“98%压缩”噱头形成微妙反差。

从技术角度看,用户对“98%压缩率”的质疑非常关键。如果仅是路径坐标量化和关键帧删减,那它与市面上存在多年的 SVG 精简工具无异,且必然伴随肉眼可见的视觉降级;若是真正转化为 dotLottie 的二进制格式,则确实是行业级别的进步,但当前缺乏透明度。更值得警惕的是,“零上传、纯浏览器”虽有隐私卖点,却也意味着压缩算法受限于客户端算力,面对复杂的逐帧 Lottie 文件,其处理效率和效果都存疑。

此外,该产品依赖“vibe-coding”(AI 生成代码)完成,这解释了 UI 美观但逻辑深度不足的现状。作为一款需要极致优化算法的工具,非专业手写的压缩逻辑在瓶颈场景下的稳定性堪忧。对于严肃的 SaaS 团队,它或许是一个快速验证的初步方案,但若要真正替代成熟的 LottieFiles 或手动压缩流程,还需要公开更详尽的技术基准测试和极端案例下的质量对比。否则,这个“98%”更像是一个数学游戏,而非工程突破。

查看原始信息
TinyLottie
Optimize and compress Lottie (JSON) and dotLottie animations up to 98% instantly. Zero uploads, 100% private in-browser tool for designers and developers.

Damnnnnn. I'm working on an app called Habit Doom.
I moved away from Lottie animations cause I needed to keep the app size less than 50 MB.
Will give it a try. Is there no quality loss on compression?

1
回复
Hi Product Hunt community! 👋 I'm Emir, a product designer and developer obsessed with clean interfaces and high performance. I built TinyLottie to solve a personal pain point which is the struggle of balancing rich Lottie animations with web speed. This project is also a personal milestone for me because it was entirely vibe-coded using AI agents in just one week! We’ve even added a Global Leaderboard to see how much data our community is saving in real-time. I’d love to hear your feedback, see your names on the leaderboard, and answer any questions you have. Special Gift for Hunters: Use the code PH20 for a special discount on our Pro plan! Let's make the web faster, one Lottie at a time. ⚡
0
回复

98% compression on Lottie JSON — is the technique mostly path/coordinate quantization, dropping redundant keyframes, or actually re-encoding to dotLottie's binary format? The answer matters because each of those has a different visual-fidelity trade-off, and "up to 98%" is the kind of number that's true on a specific shape of input.

0
回复
#9
Vfoli
Publish your venture portfolio
17
一句话介绍:Vfoli让创业者或投资人只需粘贴一个链接,AI即可自动生成专业的项目组合展示页面,解决“作品集总是零散、更新慢、没人看”的痛点。
Productivity Venture Capital Artificial Intelligence
创业项目组合展示 AI自动生成页面 投资人作品集 创业者作品集 链接转页面 项目更新 作品集分析 项目发现 天使投资展示 风险投资展示
用户评论摘要:用户肯定“粘贴链接即生成”的演示效果,但质疑其边界:当项目处于隐身模式、只有AngelList/LinkedIn页面,或公司多次转型时,是否仍能“一键完成”而非需要大量手动修正。这暴露出AI对不同数据源的兼容性风险。
AI 锐评

Vfoli的“粘贴即生成”无疑切中了创始人/投资人“展示零散资产”的痒点——把发布门槛降到极致,这是产品第一眼的价值。但评论区的质疑才是真刀:真正决定产品命运的,不是Demo有多顺滑,而是当输入变得“脏”时,AI的鲁棒性有多强。

从本质看,Vfoli做的不是“建站工具”,而是“信息资产重塑器”。它将散落于Notion、LinkedIn、公司官网的碎片信息,提炼成一套结构化、可更新、可追踪的叙事。这套叙事对创始人的价值是“时间换可信度”——过去耗费数小时手动搭建页面,现在一分钟完成;对投资人的价值则是“从静态度量到动态监控”——自带更新与分析功能,让portfolio不再是一个“死链接”,而是一个活的资产看板。

但问题的致命点在于:多个项目、多次转型、隐身状态——这类复杂实体恰恰是创始人与投资人最需要高效展示的资产,却也是结构化难度最高的。若AI只能完美处理那些已经有完整官网的“干净项目”,而面对AngelList这类半结构化数据反而出错,那产品就沦为“锦上添花”而非“雪中送炭”。对于早期创业者而言,很多项目恰恰处于“只有一条旧Twitter链接或一个过期Notion”的状态。

真正的护城河,不在于AI首屏生成的惊艳,而在于后续编辑的便捷度、对非标数据的容错率,以及“Explore Feed”能否真正为沉默的长尾组合带来冷启动流量。如果Vfoli能证明自己在“脏数据”下也能20秒内生成一个可用的、无需大修的页面,并把分发做得比传统作品集更广,它就不只是一个效率工具,而是新的创业信用基础设施。否则,它只是一件好用的核身入门级外套,终究难以赢得投资人/创始人真正高频的忠实使用。

查看原始信息
Vfoli
Paste a link. Get a portfolio. Vfoli's AI builds the entire page around your venture for founders showing what they've built and investors showing what they've backed. Updates, analytics, and discovery built in.
Hey Product Hunt 👋 I'm the maker of Vfoli, and this one started from a frustration I think a lot of you will recognize. Every time someone asked "what are you working on?" or "what have you backed?", I'd send a different link. A Notion doc for one project. A landing page for another. A LinkedIn post buried somewhere for the third. I kept telling myself I'd build a proper portfolio "this weekend." I never did. The blank page was the problem. So I built Vfoli to remove it entirely. How it works: ✨ Paste a link to your venture. That's it. The AI pulls the details, writes the copy, and builds the page around it. From blank to published in about a minute. 🚀 Built specifically for ventures - not a generic page builder. Every layout is designed for showing what you've built or backed. 📣 Updates keep it alive - post a quick note when something ships or hits a milestone. No more portfolios that quietly died in 2023. 📊 Analytics on every venture - see who's actually viewing your work. Genuinely useful when fundraising, hiring, or sourcing deals. 🔭 Explore feed for discovery - your portfolio doesn't just sit there. The right people can find it. Who it's for: Founders with more than one project. Angel investors and VCs who want a cleaner way to show their portfolio. Operators who do both. Anyone who's been meaning to build a portfolio for months and never quite got around to it. It's free, paste one link and see what comes out the other side. I'd genuinely love your feedback. If something looks weird, breaks, or is missing, tell me. I'm here. Huge thanks to everyone who tested early versions and helped shape this 🙏 Gil
0
回复

Paste-a-link → portfolio is a great demo, but the interesting question is where it breaks. What happens with a stealth-mode startup that has no website, a portfolio entry that's only on AngelList/LinkedIn, or a company that pivoted three times? Trying to figure out whether this is genuinely "one click" or "one click, then 20 minutes of cleanup."

0
回复
#10
Deskboard
Turn your PC folders into visual boards
14
一句话介绍:Deskboard将电脑文件夹转化为可视化看板,让笔记、文件、小部件同处一室,解决桌面杂乱无序、文件与任务割裂的痛点。
Productivity Notes Wallpaper
文件管理 可视化看板 桌面整理 本地同步 个人仪表盘 Windows应用 效率工具 主题定制 文件图标 待办清单
用户评论摘要:用户肯定产品对“散乱桌面”的实用性,指出无需改变文件结构即可使用。同时关注Mac/Linux版本;也有用户预想其对于整理未归档文件的帮助。普遍以正面反馈为主,期待惊喜。
AI 锐评

Deskboard的创意在于对“生产力”的重新定义——它不再强迫用户迁就于一个全新的管理逻辑,而是把“文件夹”这个最原始、用户最熟悉的数字容器,直接包装成可交互的“空间”。这种“就地改造”的思路,降低了工具采用的心理门槛。14个投票说明它处于极早期,但评论区的积极反馈验证了痛点存在:很多用户桌面确实混乱,且厌倦了在Finder和任务管理App之间反复跳转。

然而,其价值并非无懈可击。产品本质是对文件夹的“皮肤化+轻交互增强”,并未改变文件系统深层的组织逻辑。这意味着,当用户文件夹结构本身就一团糟时,漂亮看板只是“金玉其外”。此外,同步依赖于“实际文件”,若出现大量临时文件、跨设备同步需求,或文件被外部程序修改,看板的状态维护将成为负担。它更适合“存档式”或“项目式”的文件夹管理,而非高频变动的临时工作流。

真正值得警惕的,是“装饰性”与“生产力”之间的平衡。Music Player、个性化主题、动画壁纸等功能虽有趣,但若喧宾夺主,容易沦为又一个“花了三小时美化却什么事都没做”的数字玩具。产品真正的护城河,应是确保“看板交互”能比原生文件管理器更高效地选中、预览、操作文件,并让Todo与文件形成原子级的关联,而非仅仅是视觉上的堆砌。目前看,它更像是一剂针对“桌面焦虑症”的安慰剂,是药还是糖,取决于后续对文件操作效率的精深打磨。

查看原始信息
Deskboard
Deskboard transforms your folders into personal spaces where your notes live right next to your files. Customise your board with various themes & decorations, custom file icons, animated wallpapers, widgets like Music Player and To-do list, etc. The best part? Everything remains local and synced with your actual files.

Where do the hundreds of random files I haven't filed away yet live then?? :) Seriously, I can definitely use this for my complete mess of a desktop. Good luck with the launch.

1
回复

@channelscout Thanks. It can be really helpful when working with files scattered around! The best part is, you don't need to change anything. Just open the existing folder with Deskboard, and you are done

1
回复

This looks like a messsss!!! In a good way...
Just like my mind 😅 Need something like this for my Mac.

....
Anyway, best of luck @divyesh Rooting for you 🍀

1
回复

@richard_andrews4 Thanks a lot! Versions for Mac and Linux are in work. Will update soon

0
回复

All your work eventually happens in files and folders. So instead of relying on other apps to keep track of your notes and tasks, why not turn your folders into a personal dashboard? A sticky note placed right next to your file will never be forgotten.

But it isn't just a productivity tool. You can also design and decorate aesthetic boards that track your life or turn it into the coolest launcher for games.

There's something special for everyone, whether you are a developer, gamer, student, or professional.

0
回复
#11
Uncluttr - Clean up your tabs
The tab bar was never meant for 80+ tabs. Let AI organize it
13
一句话介绍:Uncluttr 是一款垂直侧边栏标签页管理工具,利用AI自动按项目或主题分组,并挂起不活跃标签以释放内存,专为解决浏览器打开80+标签页后杂乱无章、内存爆满、找回困难的痛点而设计。
Productivity User Experience Artificial Intelligence
标签页管理 AI分组 垂直侧边栏 内存优化 浏览器扩展 效率工具 工作流管理 标签页挂起 Chrome插件 重复标签去重
用户评论摘要:用户普遍称赞其AI分组和挂起功能,认为它比同类工具更贴合实际工作流。核心需求包括:支持Firefox浏览器(开发者称若呼声高会优先处理)、跨设备同步(尤其是手机端,开发者表示将作为付费计划下一步开发)。另外有用户反馈屏幕共享时标签难以定位,期待更智能的搜索和整理。
AI 锐评

Uncluttr 在“标签页管理”这个已显拥挤的赛道上,找到了一条有差异化的路——它没有停留在“提供一个侧边栏”或“手动分类”的老套路,而是将AI分组作为核心卖点,试图从“被动整理”转向“主动理解用户工作流”。这是其真正的价值所在:AI不再是锦上添花,而是解决用户“打开60+标签后连找都找不到”这一场景下唯一可行的方案。手动分组在几十个标签面前是徒劳的,只有AI能持续、自动地维持秩序。

但冷静来看,这款产品目前面临的挑战不小。首先,13个投票数表明它仍处于极早期,口碑积累和用户基数都很薄弱。其次,AI分组的能力到底有多“智能”?能否区分“同一项目下不同子任务”的微妙差异,而不是简单按域名归类?一旦用户发现AI分组只是“把Google Docs归为一组,JIRA归为一组”这种表面功夫,粘性就会迅速下降。再者,产品目前依赖Chrome生态,Firefox支持缺失,而跨设备同步(尤其是手机)是工作流用户刚需,后者还被放在了付费计划里——在用户还没形成深度依赖前就谈付费,可能为时过早。

开发者Ciprian的真诚和亲力亲为值得肯定,但他的回复中“如果更多人要求才做Firefox”也暴露了资源有限、靠反馈驱动的被动策略。Uncluttr像一把精致的瑞士军刀,但只有在用户已经被“80+标签页的灾难”折磨到忍无可忍时,才会觉得它不可或缺。对于普通用户,它可能只是一个“能省点内存”的小工具。建议开发者在AI分组的“智能感”和跨平台同步上继续砸重金,否则很容易被OneTab、Sidewise等已有一定用户基数的竞品模仿或压制。

查看原始信息
Uncluttr - Clean up your tabs
You have too many tabs open right now. You know it, your RAM knows it, your fan knows it. Uncluttr replaces the tab bar with a vertical sidebar and uses AI to group your tabs automatically, by project, topic or domain. Inactive tabs get suspended to free memory. Everything persists during crashes and restarts.

Looks cool, got support for firefox?

2
回复

@const_in Thanks! Not yet, there are a couple of things to fix over there but if more people ask for it I'll prioritize

0
回复

Such a cool extension. For someone that has tens of tabs open at all time for a variety of tasks, I love that I don't have to switch to an entire different browser (which means loosing mobile sync and potentially other feature) just to modernize my tab situation. Keeping tabs manually organized gets out of control too quick to be a feasible option, and the suspend feature on top of that is (unfortunately) perfect for the modern web

❤️

2
回复

@adrian_pascu3 Thanks for the nice comment! This is exactly why I made this. Also glad you like the suspend feature, I also like using it a lot

0
回复

This is amazing. I’ve just tried this for the first time and after trying countless tab managers this is the only one that works for me. Great job!

2
回复
@vladzinca Thank you Vlad, glad you found this useful! Let me know if you encoujter any issues so I can help!
0
回复

Hey everyone, Ciprian here, the developer of Uncluttr!

This is the first time I ever make a personal product public. For a long time I struggled with having too many tabs open.
I would close all of them and in 6 hours max I would get back to 60+ tabs.

About a year ago I started building my own solution, a vertical sidebar tab manager with AI grouping, so I'd never have to manually organize my tabs again.


Why not use an existing one? I tried. Most tab managers are built to be generic. AI changes that, it learns how you work and organizes tabs around your actual workflow, not a one-size-fits-all system.

After using it daily for months, I realized this could work for others too. So I put in the extra work to make it public.

What you get for free:

  • vertical sidebar

  • unlimited workspaces and groups

  • tab suspension to save memory

  • tab search

  • deduplication

  • no account needed, all data stays in your browser.

  • a couple of AI groupings, enough to get a taste of it's power

To celebrate the launch, I'm offering the first 6 months free on the yearly plan with promo code PH50.

I'm actively building this and your feedback directly shapes what comes next. What would your dream tab manager do that nothing on the market does today?

1
回复

Nice one!

In my day to day work as an analyst, I have lots of tabs open (easily 30+ just for JIRA, plus several others for documentation and research). Needless to say sometimes I get overwhelmed. Imagine when I share my screen and I can't find some tickets...

I am looking forward to the cross-device synching. When I'm away from my desk, my phone basically becomes my laptop.

1
回复

@bogdan_george_dragomir Thank you George!

Cross device syncing will probably be the next feature to come to the paid plan. Not sure how well it will work with mobile devices, but I'll look into it

1
回复
#12
Iconstack: MCP-Native Icon Search
Semantic search + MCP + API. 50k icons. Always free.
11
一句话介绍:IconStack通过语义搜索与MCP支持,将50,000+图标库统一为单一接口,解决了开发者在不同图标网站间频繁切换、命名混乱、无法被AI工具直接调用的效率痛点。
Icons Development Design resources
图标搜索 语义搜索 MCP集成 API 开发者工具 设计师工具 AI原生 免费图标库 图标统一管理
用户评论摘要:用户对统一图标库和语义搜索功能表示赞赏,特别提及MCP支持在AI开发环境中的便捷性。主要建议是希望未来能引入更多图标库,并关注API的灵活使用场景。
AI 锐评

IconStack的价值不在“集成50K图标”这个数字本身,而在于它精准捕捉了现代开发工作流中一个被长期忽视的断层:AI编码工具(Cursor、Claude等)的快速迭代,让“在编辑器内完成一切”成为刚需,但图标这种高频但琐碎的资源仍停留在“打开浏览器→翻找→复制→粘贴”的原始阶段。MCP(Model Context Protocol)支持的引入,本质上是在AI代理和设计师/开发者的界面之间架设了一条即时的语义通道,让AI能直接根据“一个表示‘设置’的齿轮图标”这种自然语言指令返回资源,这才是真正的“AI原生”体验。

从运营策略看,全静态、零成本架构配合“永久免费”承诺,显示这是一款极简主义产物——没有数据库、没有商业化压力,也就没有用户锁定的动机。创始人Deepak以独立黑客身份做了巨头不愿做的小事,但这件小事恰好卡在“工具链碎片化”的通用痛点上。唯一风险是,随着使用量激增,API查询的稳定性与响应速度能否保持免费级水平?此外,语义搜索的质量高度依赖底层向量化模型的精度,如果出现语义偏差,会直接破坏“无需知道系统名称”的核心承诺。

总的来说,IconStack与其说是一个图标搜索工具,不如说是“AI时代的图标资源中间层”——它在编辑器的AI Agent和图标数据库之间,做了一次轻量但关键的解耦。对于任何重视开发流不被中断的用户,它值得被加入工作流。

查看原始信息
Iconstack: MCP-Native Icon Search
IconStack is the icon library built for how modern developers and designers workflow. 50,000+ icons from 15+ libraries; unified, semantic, and AI-native. → Semantic search: find icons by meaning, not system names → MCP support: your AI agent queries icons directly in-editor → API access: programmatic access for tools and pipelines → Always free. No account. No paywall. Forever. One search. Every library. Built to last.
Hey PH 👋 Deepak here. I run a UI/UX studio and build AI tools on the side as an indie hacker. IconStack started as a personal frustration. Switching between icon sites mid-build is a genuine flow killer. Wrong names, fragmented libraries, no API. A 2014 experience in a 2026 workflow. So I unified 53,000+ icons from 15+ libraries and built the search layer they always deserved. It already pulls ~15,000 visitors a day organically. Clearly I wasn't the only one frustrated. Two things I'm most proud of: Semantic search: you shouldn't need to know an icon's system name. Just describe what you need and it finds it. MCP support: your AI agent can now query icons directly inside Cursor, Windsurf, or Claude. No tab switching. Icons land right in your code. Fully static, costs near-zero to run, and stays free permanently. No account, no paywall, no plans to change that. And I'll keep adding more libraries over time, so drop a comment if yours is missing. Would love to know what you'd do with the API too. Roast it, break it, ship with it.
1
回复
#13
Blurts-Voice to Any Task App
Speak your chaos. Blurts turns it into tasks.
10
一句话介绍:Blurts 是一款专为“脑子一团乱麻时”设计的语音转任务工具,用户只需说出混杂的念头,AI 会自动清理赘词、拆分想法、识别日期并同步到 Notion、Google Tasks 等常用工具,解决“想记录但没手打字、记下来后还得手动整理”的痛点。
Android iOS Productivity Artificial Intelligence
用户评论摘要:用户普遍认可Blurts解决“说出即整理”的核心价值,尤其称赞日期识别功能(“连今天星期几都不知道”)。高级用户提出“发泄模式(Vent Mode)”需求:希望有时只记录情绪/废话,不强转任务。制作方已将其列入路线图,显示出对非任务场景的认可。
AI 锐评

Blurts 的价值不在“多了一个AI助手”,而在于它做出了一个重要的产品设计判断:**人类在真实生活中,任务是混在脏话、牢骚和尿布之间的**。市面上绝大多数任务管理工具假定用户是理性的、有空闲的、能精确表达意图的——这本身就是一种精英主义的傲慢。

Blurts 的聪明之处在于,它没有去挑战“如何让用户更自律”这个无解题,而是承认“用户就是会在大脑发懵时丢出垃圾话”,然后只做一件事情:**在垃圾里筛出金子**。它不要求用户先想清楚再说话,而是让用户先说话,然后再由机器去想清楚——这是行为路径上颠覆性的转变。

但从产品角度看,目前10个投票和仅有的3条评论,说明它仍在早期验证阶段。最大的隐患是:**“混乱”固然是真实场景,但“混乱”是否高频到能让用户形成新的习惯?** 用户可能在头三次试用时感到爽,但后期如果发现“说出去的废话”并未真正减少决策负担——比如任务拆分后依然需要手动调优先级、跨工具同步仍有错位——那么新鲜感就会快速消退。

此外,仅凭语音清理+日期识别,很难形成足够的壁垒。类似Siri、Google Assistant等已经具备基础的任务识别能力,Blurts 的护城河只能是**对“非结构化语音”的清洗精度**,以及在这个垂直场景里用户粘性的养成。如果能提前做好“发泄模式”这类情绪出口,并配合“定期回顾/自动生成周报”的闭环,才会从“好用的工具”进化为“让用户离不开的系统”。

一句话锐评:**可惜只有10票,但方向对了好过执行完美。**

查看原始信息
Blurts-Voice to Any Task App
Blurts uses AI to sift through the mess and find the gold. It strips filler words, creates tasks, assigns dates, and syncs everything to your tools automatically. Built by a husband-and-wife team with a baby, full-time jobs, and zero time to write down tasks.

Hey Product Hunt! 👋

Blurts started as a tool I desperately needed for myself.

I’m a full-time software engineer, real estate property manager, and mom to a one-year-old daughter. My brain generates “don’t forget to do X” thoughts at the worst possible moments - while holding the baby, in a meeting, fighting a diaper change, walking between rooms, or too sleep-deprived to remember what I was doing in the first place.

And the problem is: I almost never have one clean thought at a time.

It’s usually four thoughts tangled together:

“Fix the leak, push the PR, buy diapers, and reschedule the dentist to next Tuesday.”

I tried voice memos. They captured the chaos, but they didn’t organize anything. Then I had to come back later, listen through everything, and turn the recording into actual tasks myself.

I tried notes and to-do apps too, but they expected me to stop, type clearly, choose the right place, pick the right fields, and organize everything manually. By the time I finished capturing one thing, I had usually forgotten the next one.

So my husband and I built Blurts.

Not as a shiny “AI productivity platform,” but as a simple way to get messy thoughts out of your head before they disappear.

🎙️ Speak naturally
Tap one button and say everything at once. Ramble, pause, repeat yourself, use filler words — no need to sound organized.

🧹 Blurts cleans up the word soup
It strips out the filler, separates mixed thoughts, and turns them into clean tasks.

📆 It understands dates from what you said
If you say “next Tuesday” or “tomorrow morning,” Blurts pulls that out and adds the right timing.

🔁 It works with the tools you already use
Blurts checks the structure of your existing tool and suggests fields like category, priority, status, effort, or whatever properties you already have set up.

Right now, Blurts integrates with Notion, Google Tasks, Google Calendar, Apple Reminders, and Apple Calendar.


That’s it. No complicated setup. No big dashboard to manage. Just speak, pocket your phone, and go back to what you were doing.

This is built by a husband and wife in the margins between full-time jobs, nap schedules, bedtime routines, and all the tiny life admin tasks that never seem to end.

I built Blurts because I needed something that could keep up with real life - not the calm, organized version of life, but the messy one.

If you’ve ever said “I’ll remember that later” and then absolutely did not, I’d love to hear:

Where do you usually remember tasks at the worst possible time?

And what tool do you wish was easier to use by voice?

Thanks for checking out Blurts 🧡

3
回复
love that it's smart enough to know when next Tuesday is because I barely even know what date today is
2
回复

@gene_lo haha the maker curse: building things so we don't have to remember things 😅

1
回复

"Speak your chaos" is the right frame — the verbalization is the hard part, not the to-do list. I counsel clients on money and the same pattern shows up: the avoidance loop breaks the moment someone says "I have $40K in credit card debt" out loud rather than circling it silently for a week. Have you thought about a vent mode that captures the dump without converting any of it to tasks? Sometimes the tasks come later — after the unload does the actual work.

1
回复

@justin_huynh the $40K example is so good - that's exactly it. the act of saying it out loud is already doing something, before any system touches it.

vent mode is something I've thought about but haven't built yet. right now everything gets converted, which is probably wrong for certain moments. sometimes the thought just needs to exist without becoming a task.

adding this to the roadmap for real - thank you for framing it this clearly.

0
回复
#14
PostGun
Build, remix and post on every social network
9
一句话介绍:PostGun是一个集内容创作、智能二创与一键分发于一体的跨平台社交媒体管理工具,帮助创作者摆脱在多个设计、排期和发布应用间反复跳转的繁琐流程,实现“一次构建,随处发布”。
Productivity Social Media Artificial Intelligence
社交媒体管理 内容创作 跨平台发布 二创工具 视频编辑 排版设计 排期日历 一键分发 TikTok Instagram
用户评论摘要:用户认可创意,但担忧“二创”功能易导致内容同质化;同时指出单一内容在不同平台表现不同,建议增加自动适配各平台语境的改写功能。用户还询问了与同类产品Post Bridge的差异。
AI 锐评

PostGun的定位精准地击中了多平台创作者一个真实但常被忽视的痛点——不是“发不出去”,而是“做不出来”。它巧妙地将设计画布、热门内容二创和发布日历熔于一炉,试图缝合从灵感到分发的断裂链条。“二创”功能是其最尖锐的武器,也最危险:它降低了内容生产的门槛,却可能将创作者推向“搬运式创作”的悬崖。如果PostGun仅提供一个快速吸睛的工具,用户很快会发现,所有人都在“拆解”同一批爆款,最终导致内容审美的窄化和平台算法的降权。真正的价值壁垒在于能否提供深度的“平台语境适配”——不仅仅是格式的裁剪,更是叙事节奏、视觉风格乃至社交礼仪的自动转换。目前9票的支持度显示其仍处于早期验证期,用户对“原创性”的质疑恰恰是其产品迭代的黄金路标。PostGun需要警惕变成另一个更快的内容速食机,而应进化为一个更具智能判断力的“创意参谋”,将“remix”上升为一种可学习的创作策略,而非简单的复制粘贴。否则,它终将被自己的效率所引发的同质化洪流淹没。

查看原始信息
PostGun
Creating for every platform means jumping between Canva, a scheduler, y 5 different apps, designing once and reuploading everywhere. PostGun gives you a built-in canvas to build posts, a remix tool to turn viral content into your own, and one-click publishing to TikTok, Instagram, YouTube and more, all from a single calendar. Build it once. Remix the rest. Post everywhere.

Hey everyone, really excited to finally share PostGun with you today.
This is one of the projects from my challenge of building 24 startups in 12 months, and honestly it's one I've been wanting to build for a long time.
I built this because my own content workflow was driving me crazy. For every post I wanted to publish, I had to design it in Canva, download the file, open a scheduler, reupload it, write captions for each network one by one, and somehow keep track of what was going where. By the time anything went live, I had already lost the energy I started with.
The thing is, scheduling was never my real problem. The hard part has always been building posts that actually look native to each platform. Most tools out there only solve the scheduling side, so I wanted something where the creation, the remix and the publishing all happen in the same place.
PostGun started as a simple post composer. Then I added a built-in canvas, because flipping between tabs to design killed my flow every time. After that came the remix feature, which lets you take any viral post and rebuild it into your own in a couple of clicks. That part actually changed how I think about content, because most great posts are really just smart remixes of something that already worked. Finally I connected the whole thing to TikTok, Instagram, YouTube and the rest, so you can ship across every platform from a single calendar.
The idea behind PostGun is simple: build once, remix the rest, post everywhere.
I'd love to hear what you think, what feels missing, and which platforms you'd like to see next. Every piece of feedback genuinely shapes where this goes from here.
Thanks for taking the time to check it out.

1
回复

@pasho Congrats on the launch! Very nice product.

I'm curious - how does it compare against Post Bridge (https://www.post-bridge.com) by Jack Friks, which does the same overall?

0
回复

@pasho Congrats on the launch. The remix idea is interesting but feels like it could easily turn into low-effort copycat content if everyone’s pulling from the same viral posts. I’d probably worry about everything starting to look the same after a while. How much control do I actually have to make it feel original instead of just slightly tweaked?

0
回复

@pasho It's really interesting; it's a good tool.

0
回复

Love the concept in general but perhaps in my experience over the last few months what works on 1 platform rarely works on another. Instagram carousels that work are generally different from LinkedIn presentations that get engagement. Is there a way the same content can be rephrased and worked automatically for each platform? What do you think?

Anyway, best of luck @pasho Rooting for you 🚀

0
回复
#15
Posting Machine AI
Turn your LinkedIn into a sales pipeline for B2B founders
9
一句话介绍:Posting Machine AI 帮助B2B创始人将Slack中的真实对话自动转化为LinkedIn帖子草稿,10分钟即可批准一周内容,把注意力转化为温热的销售线索,而非冷冰冰的群发。
Sales Marketing LinkedIn
B2B销售 LinkedIn营销 创始人销售 Slack集成 AI内容生成 社交销售 内容自动化 销售线索挖掘 用户互动分析 效率工具
用户评论摘要:用户赞赏从Slack抓取信号的创意,认为“三选一”的回复选项不错。但提出核心疑问:非Slack用户如何自动化LinkedIn互动?并希望支持在解决特定问题的帖子下评论。官方回应称该功能暂未列入路线图,但会考虑。
AI 锐评

Posting Machine AI的切入口很聪明——它没有掉进“帮创始人写爆款文”的内卷陷阱,而是精准解决了B2B创始人与众不同的问题:不是缺乏内容,而是缺乏将日常工作中的高价值信号(客户洞察、产品决策、内部争论)系统化变现的机制。痛点抓得准,“信号捕获”比“内容生成”更具护城河效应。

但产品目前的核心局限在于对Slack的过度依赖。从评论中可知,不少用户(尤其非Slack重度使用者)期待的是更广泛的LinkedIn自动化能力,比如针对热门问题自动生成评论、主动互动等。而回复称“暂不在路线图”,暴露了早期产品的野心不够大。只做“Slack→LinkedIn”的单向管道,会让工具沦为“发帖效率器”,而非真正的“人脉销售引擎”。

真正的价值在于能否从“发帖助手”进化成“智能销售代理”:不仅要帮你生成内容,还要帮你选择跟谁互动、在哪个话题下留下痕迹、如何将点赞转化为私信。如果只是省了10分钟排版时间,很难说服创始人为此付费。未来方向应是:内容(从Slack)→ 分发(到LinkedIn)→ 互动(主动出击)→ 转化(私信归因)的全闭环系统,否则始终只是半成品。

查看原始信息
Posting Machine AI
Posting Machine helps B2B founders build LinkedIn pipeline without adding hours to their week. Approve a week of posts in 10 minutes, all drafted from real conversations already happening in your Slack. Then see exactly who's engaging and turn that attention into warm conversations — not cold outreach.
We built Posting Machine because founders don’t have a post content problem. They have a capture problem. The best raw material is already sitting in Slack: customer insights, product decisions, sharp opinions, lessons from calls, internal debates. But by the weekend, it’s buried. Most AI writing tools ask you to start from a blank prompt. Ghostwriters are expensive and need constant context transfer. We wanted something closer to the way founders already work: react to a useful Slack thread, let the system find the signal, turn it into LinkedIn drafts, and approve in minutes. This is an early product, please don't hesitate to let us know what you think!
3
回复

Hey Product Hunt 👋

We’re building Posting Machine to help B2B founders turn LinkedIn into a founder-led sales channel.

It helps founders draft posts from Slack, improve content with analytics, and turn engagement into outreach opportunities.

We have a promo code for Product Hunt users. Comment below or message us if you’d like to try it.

Would love to hear your feedback, questions, or anything you think we should improve.

1
回复

The 3 options before committing to a message or reply is good!!!
But I want to create posts and comment on existing posts that have a problem I'm trying to solve on LinkedIn.
I'm not a slack user but I want to automate my LinkedIn engagement. Is that part of your roadmap?

Best of luck guys @ian_hsiao @hank_wu_1999

0
回复

@hank_wu_1999  @richard_andrews4 hey Richard! We’re aiming to help B2B founders do founder-led sales; that’s not currently on our road map but we will consider it! Can you share more about the goal for automating link in engagement?

0
回复
#16
Tambr
Turn any story into a multi-voice audiobook
9
一句话介绍:Tambr可将任意文本(小说、剧本、同人等)转化为多角色有声书,通过AI自动为每个角色分配独特嗓音,解决传统TTS(文本转语音)对话生硬、缺乏沉浸感的核心痛点。
eBook Reader Books Audio
AI有声书 多角色语音 文本转语音 角色配音 沉浸式阅读 小说工具 创意写作 音频制作 AI语音合成
用户评论摘要:用户称赞操作简单、入门引导直观;但主要困惑在于无法自主调整角色声音,期待后续版本增加语音选择功能。制作人已确认下一版将加入声音定制选项。
AI 锐评

Tambr切中了一个精准且被低估的需求——让“听故事”真正像“看故事”一样有角色辨识度。当前大多数TTS工具要么是机械的单一人声朗读,要么需要繁琐的手动标记和配音素材,Tambr用“自动推断年龄/性别/地域”的逻辑,把用户操作压缩到粘贴或上传一步,这是典型的“降维体验”。

但9票的初始数据也暴露了两个关键问题:一是垂直场景太窄(针对文学与同人圈),这意味着商业天花板可能受限;二是当前版本“无法手动调音”会导致专业用户(如创作者)感到失控——虽然AI推断很酷,但用户对“角色声音”的想象往往无标准答案,需要精细控制权。制作人承诺的“voice selection”如果不能提供足够的自由度和调优选项(例如情绪、语速、方言强度),很可能沦为鸡肋预设。

另外,从产品逻辑看,Tambr隐含的最大价值可能是“版权转化衍生品通道”——一旦AI能批量化、高质量地将小说、剧本甚至草稿转化为分角色有声书,它实际上在降低音频出版物制作的准入门槛,这才是对音频内容供应链的潜在颠覆。但目前它更像一个“有趣的玩具”,要成为“可靠的工具”,仍需解决角色一致性、长文本上下文记忆等难题。一句话:创意很好,但别让“自动”变成“单调”。

查看原始信息
Tambr
Tambr turns any story into a multi-voice audiobook. Paste, upload, or link anything and each character gets their own voice, so dialogue actually sounds real. Perfect for stories, novels, fanfiction, scripts, and more.
Hi friends! 👋 I’m Caroline, one of the makers behind Tambr. I built Tambr because I’ve always wanted to feel like I was inside the stories I was reading—but most audio tools make dialogue sound robotic. Tambr turns any text into a multi-voice audiobook. Paste, upload, or link anything, and each character gets their own voice—we infer things like age, gender, and region so it actually feels real. Would love for you to try it out and share any feedback. Thanks ❤️
2
回复

I downloaded the app.

Super easy UX but I didn't understand how to change the voices.

Love the simple onboarding.

Best of luck @caroline_zhu1 Rooting for you ✨

1
回复

@richard_andrews4 thanks Richard!! Voice selection coming in the next update, appreciate the kind feedback ✨

0
回复
#17
today, a small planet — earth day
A 2-minute space for quiet reflection and connection.
8
一句话介绍:一款极简的静心工具,在花月夜等自然节点引导用户“想念一个人”,通过2分钟的沉思与互动音画,缓解日常的浮躁与孤独感,提供片刻内心宁静。
Music Meditation Spirituality
用户评论摘要:用户普遍赞赏界面设计、音效与动画的用心,认为它带来了“刹那改变世界”的体验。但评论均为正面反馈,未提具体问题或改进建议,缺乏实质性批判。
AI 锐评

这款产品是典型的“小而美”情感实验,它以Kenshi Yonezu的歌曲为灵感,将个人创作与公众情绪节点(花月夜、地球日)巧妙缝合。其核心价值并非功能创新,而是提供一种“被允许安静”的仪式:一句“想念一个人”的提问,配合旋转地球与背景音,精准击中了都市人普遍的情感匮乏——不是缺工具,而是缺一个让情绪合法降落的容器。

然而,冷静看,它更像一个数字标本而非成熟产品。投票仅8票,评论全部是创作者本人的深情回复而非真实的第三方客诉,显示出项目尚处于极早期的开发者自嗨阶段。产品几乎不解决任何实际问题,也无法形成持续使用习惯——2分钟的设定决定了它是一次性的情绪涟漪,而非长期陪伴。作为粉丝向的艺术项目,它足够真诚;但作为“产品”,它缺乏用户留存的基础(无日记、无提醒、无社交分享),商业价值趋近于零。

真正值得关注的,是这种“微小而明确的情感切入点”对独立开发者的启发:在泛滥的效率工具中,敢于为情绪做减法反而能脱颖而出。但若想从“点赞”走向“付费”,团队还需补上用户行为闭环的设计——比如让“想念”可被记录、被回看,甚至让不同用户的“片刻”产生连接,否则注定是又一座孤独的月下灯火。

查看原始信息
today, a small planet — earth day
Tonight is the Flower Moon — May's full moon, named for the blossoms that bloom under its light. I built this small app to mark the day. This is a personal fan tribute, inspired by "Spinning Globe" (地球儀) — a song by Japanese artist Kenshi Yonezu for Studio Ghibli's The Boy and the Heron. It’s a quiet tool designed not to change the world, but to soften the way we meet our own ordinary days. How it works: The app asks one quiet question: "Think of someone." That's all. Thank You.
The moment you thought of someone, even briefly, changes the world." Listen to my story↓ https://soundcloud.com/27qkoaxar... Made with quiet hands in Japan. I hope this provides a moment of peace for your heart on this Flower Moon night. You can read more about the story behind this app and listen to my a cappella performance in my Medium article here: https://medium.com/p/d0e5f534b7f3
0
回复

Thanks a million, Liviu Chita! I’m so glad you enjoyed the globe and the soundscape. All of you encouragement and Kenshi Yonezu’s music are the two pillars that support my work. Best of luck to you too! 🌍✨

0
回复

Thank you so much,David! I’m incredibly moved by your kind upvoted. Your support, along with the music of Kenshi Yonezu, is what keeps me going and inspires my creativity every day. It means the world to me that you noticed the details like the sound and animations!

0
回复

Thank you for the amazing feedback、Richard! I put a lot of heart into the intentionality of this project. My creative journey is fueled by supporters like you and the profound music of Kenshi Yonezu. Knowing that the globe and sound resonated with you gives me so much energy to keep building!

0
回复

Such a beautiful website!!!!

Love the intentionality behind the interactions.

Loved the globe animation. It's a chefs kiss.

Even the background sound it heavy.

Best of luck mate!!! Rooting for you 🌎

0
回复
#18
Graphloom
The home for Etsy sellers - AI images + listings in 60s
7
一句话介绍:Graphloom专为Etsy卖家打造,能在60秒内将产品照片转为工作室级AI图像,并自动生成完整商品列表,解决小卖家无力承担专业摄影费用的痛点。
Productivity Artificial Intelligence E-Commerce
AI图像生成 Etsy卖家工具 商品摄影 列表生成器 电商视觉优化 低成本创业 背景替换 产品营销 自动化工具 FLUX Kontext
用户评论摘要:创始人Amit强调了产品针对Etsy卖家的专业性和低成本。用户询问能否选择与店铺现有风格匹配的背景或样式,创始团队回应支持自定义风格或输入提示词,并提示网站有完整视频演示。
AI 锐评

Graphloom精准切入了一个小而痛的缝隙市场:Etsy手工卖家对专业图片的需求与高昂摄影成本之间的巨大鸿沟。其核心价值不在于AI图像技术的领先(FLUX Kontext保持产品一致性是基础能力),而在于对Etsy生态的深度耦合——将“出片”与“上架”两个关键动作压缩在60秒内,并直接产出平台所需的标题、标签、描述,这是通用型AI图像工具难以比拟的。

但目前7票的低热度暗示其早期阶段尚在冷启动。产品真正的护城河不在于“降价”,而在于能否持续解决卖家“风格一致性”和“批量化管理”的进阶需求——用户关于“匹配店铺风格”的提问已揭示这一点。此外,$4/月的定价虽然低廉,却可能陷入“工具替代”而非“增值服务”的陷阱。如果能将AI生成的图片数据反哺给卖家(例如分析哪种风格转化率更高),或构建社区内的风格模板共享,Graphloom才能从一个“省钱的工具”进化为“帮卖家赚钱的平台”。否则,面对Canva、Midjourney等巨头在电商领域的渗透,其生存空间将停留在对价格极度敏感的长尾用户。

查看原始信息
Graphloom
We built Graphloom for one reason: Etsy sellers deserve professional product photos - not just the ones who can afford a $200 photographer. 🖼️ WHAT IT DOES: Upload your product photo → get studio-quality images + a complete Etsy listing generator in under 60 seconds.
Hey PH community! 🙏 I'm Amit, maker of Graphloom. Quick story: I was talking to Etsy sellers and kept hearing the same thing - "My products are great but my photos look amateur." A professional photoshoot was $200+. Way too expensive for most handmade sellers. That's why I built Graphloom. 🔥 What makes us different from generic AI tools: → FLUX Kontext AI keeps your EXACT product (not just similar) → Built specifically for Etsy - not a generic image tool → Listing generator included (title + 13 tags + description) → $4/month to start - cheaper than one coffee 🎁 For PH community: Use code PRODUCTHUNT for 30% off I'm here all day to answer questions. What would you want to see next? Background remover? Bulk generation? Let me know! 👇
1
回复

Can you choose a style or background that matches a shop’s existing vibe?

1
回复
@karimbenkeroum you can choose style or write custom prompt, watch full video
0
回复
@karimbenkeroum The video is provided on the website.
0
回复
#19
bouncy
Tiny Rust headless browser for scraping.
6
一句话介绍:bouncy是一款轻量级Rust无头浏览器,专为需要处理JavaScript渲染页面的网页抓取任务而生,在Playwright(臃肿、依赖多)和curl(无法处理动态内容)之间提供了一个低资源消耗、高启动速度的中间方案。
Productivity Developer Tools Artificial Intelligence GitHub
网页抓取 无头浏览器 Rust 命令行工具 MCP服务器 Playwright替代 轻量级 单二进制 V8引擎 开发者工具
用户评论摘要:开发者(产品作者)在评论中解释了构建动机:现有方案(Playwright/curl)在“只抓取少量动态内容”的场景下都过于笨重或不足。产品定位为两者的中间地带,强调体积小(10-21MB)、启动快(~30ms)、支持CDP协议以便作为Playwright的后端。
AI 锐评

bouncy并非又一个“更好的Playwright”,它的聪明之处恰恰在于承认Playwright和curl都有其适用范围,并精准切入两者之间的“边缘地带”。对于需要频繁、小批量抓取JS渲染页面的场景(如监控单页面状态变化、提取少量元数据、为LLM提供MCP接口),它的价值是颠覆性的:10MB级别的单二进制、30ms的冷启动,意味着你可以像用curl一样毫无心理负担地在脚本管道里调用它,而不必考虑复杂的Node环境和庞大的Chromium实例。

它的真正价值在于“去重”。“own DOM, embedded V8, HTTP client”表明它从根本上砍掉了对实际浏览器布局和渲染能力的依赖,只保留了JS执行和HTML解析。这种极致的“最小可用”设计,恰好解决了Playwright生态中“为了拿一个标题而启动整套浏览器渲染引擎”的荒谬浪费。另外,对Chrome DevTools Protocol的支持可谓神来之笔,这让它不是一个孤立工具,而是能无缝融入现有Playwright/puppeteer工作流的后端替换,降低了技术切换成本。

然而,必须指出其潜在局限。砍掉布局和渲染意味着它无法处理那些严重依赖CSS动画、Canvas或复杂DOM重排的动态生成内容。对于那些需要截图、渲染特定图片尺寸或执行复杂交互的场景,bouncy将无能为力。它巧妙但绝非万能,如果未来有野心挑战完整浏览器性能,可能会陷入难度陷阱。对于其当前定位——一个“最好的curl替代品”和“最轻的Playwright后端”,bouncy是犀利的,但开发者需要清醒认知它的边界。

查看原始信息
bouncy
bouncy is a web scraper. Tiny, fast, ships as a single binary — no Node, no Chrome, no Python to install. Point it at a URL and get back the HTML, the visible text, or every link on the page. If the page only renders properly with JavaScript, bouncy will run the JavaScript too. Use it from the command line like curl, or drop it in as a Playwright backend.
Why I built bouncy Every time I needed to scrape a JS-rendered page, the choice was: spin up Playwright (200+ MB per page, ~1s cold start, Node + Chromium) or fall back to curl + regex (fast, breaks on anything dynamic). For most jobs (fetch a page, extract a title, run one tiny snippet of JS) both felt wrong. So I built bouncy. A tiny Rust headless browser: 10-21 MB per page, ~30 ms cold start with V8, ships as a single binary. No Chromium, no Node runtime. Has its own DOM, embedded V8, HTTP client, and HTML extractor, all separately usable as crates if you only need one part. It also speaks the Chrome DevTools Protocol, so Playwright / puppeteer-core can drive it as a drop-in for the cases where you don't need real layout or paint. Plus an MCP server so Claude / Cursor / any MCP client can scrape with it natively. If you've ever wished there was a middle ground between Playwright and curl, this is it.
0
回复
#20
NYC Street Cleaning
The traffic light for NYC alternate-side parking
6
一句话介绍:NYC Street Cleaning 是一款极简的纽约路边停车换边清扫提醒工具,通过红绿灯式颜色卡片,让车主在停车位上即刻判断是否需要挪车,彻底解决“换边停车”规则繁琐、罚单频发的痛点。
Cars Maps GPS
纽约停车 换边停车 ASP 交通罚单 极简工具 城市实用应用 实时提醒 交通数据 iOS 免费应用
用户评论摘要:创始人Kip分享开发动机(年收4张罚单)与技术细节(街区级精度、340k标识解析、双时间表、30+天暂停识别、智能推送)。评论主要是对产品的认可与功能询问,无负面反馈,Android用户期待登台。
AI 锐评

这个产品本质是对“信息过载”的一种反向抵抗。纽约超过130万车主每天都需要面对密密麻麻的清扫时间表、节假日暂停和市政突发通知,而几乎所有竞品要么用付费墙自断生路,要么用设计堆叠把简单答案藏进三层菜单。Kip 从自己“年收4张罚单”的私痛出发,做出了一个反常识但极度好用的APP——只在屏幕上显示“红、绿、黄”三个颜色。这既是功能设计,也是战略选择:用户想要的不再是更多数据,而是被解读后的唯一答案。

产品价值不在于技术多复杂(虽然解析34万条街区标识、15分钟刷新暂停数据确实不简单),而在于它完美界定了“什么是好工具的截止线”——告诉你现在该不该动,一分钟后就消失。这种设计哲学在超大城市公共服务领域极其稀缺:不做全能管家,只做路口信号灯。AI锐评认为,如果团队能坚持“不膨胀”原则(不加地图、不加计费器、不加广告骚扰),它将成为纽约市政服务类应用的现象级标杆,其价值远超今日6票所能代表。真正的脆弱点在于:单靠一个隐私策略的隐藏广告位能否维持免费+无数据沉淀的生存模型。这或许是所有“极简主义公共工具”都无法绕开的终极拷问。

查看原始信息
NYC Street Cleaning
Tap the app, see green, yellow, or red. StreetCleaning reads the signs on your block and tells you whether to move your car right now. Suspension-aware, push reminders the night before, free forever. Built for the 1.3M New Yorkers who park on the street.
Hey Product Hunt 👋 — I'm Kip, founder of NYC StreetCleaning. I built this after collecting four ASP tickets in a single year. Every existing "NYC parking" app either crashed, asked for $9.99 a month, or buried the answer behind three taps and a paywall. I just wanted a green light or a red light — "do I need to move my car right now, or not." So that's the whole app. One screen. One color. A few things that took longer than expected and might be interesting to other makers here: • Block-level precision. The city's open data gives you sign locations as raw geometry — no "this side of the street between X and Y." We had to merge ~340k sign records, snap them to block faces, and build a parser that understands phrases like "TUES THURS 11:30AM-1PM EXCEPT SUN" plus the broom glyph. Worth it — every other ASP app gets this wrong on dual-schedule blocks. • Suspension-aware "you're safe." NYC issues 30+ suspension days a year (religious holidays, snow, mayoral orders). Telling someone they're safe when there's a fresh snow suspension you missed is the worst-possible bug, so we re-check the official feed every 15 minutes before showing green. • Push that doesn't suck. Night-before + morning-of, snoozable, and silent on suspension days. No "engagement" pings. It's free forever — funded by a single banner that's hidden when the status card is visible (we never block the answer). iOS only for now. Android is on the roadmap if there's demand — if you're on Android and would use this, drop a comment below and I'll send you a TestFlight-style beta when it lands. Question for you: if you've ever used a hyperlocal city utility app (parking, transit, bins, alternate routes), what's the one thing the makers got wrong? I'd love to not repeat it. 🙏 — Kip
0
回复