I built QRAuth.io passwordless authentication, it works on any website or physical QR (menus, parking, ticketing, kiosks ).How it works in 8 seconds:
User sees an animated living QR on your site (rotates every 500 ms so screenshots are useless)
They point their phone camera at it
Tap once to confirm with biometrics/passkey
Boom, logged in. No typing, no copy-paste, no extra app.
It s cryptographically signed (ECDSA + post-quantum), phishing-resistant, includes proximity proof, and fraud intelligence. Drop-in web components mean you can add it with literally one HTML tag or npm install . Try the passwordless login flow or the beach-bar menu example, it s kinda addictive. Would love your honest feedback:
Does the living QR feel like magic or overkill?
What use cases would you actually use this for?
Any friction I should kill before I push it harder?
Mine for Lunia (AI bedtime stories): my kid asking the same monster-under-the-bed question for 3 weeks straight while every personalized story app just swapped her name into a generic dragon plot.
Hey PH community just shipped my first independent storefront and would love feedback / brutally honest critique.
What it is: 8 products total at https://onmylist.gumroad.com/ , all centred on AI adoption for Indian small businesses (1-25 person teams). The flagship is a 14-page brief that ranks 10 specific AI workflows by hours-saved-per-week monthly cost in INR, with 30+ copy-paste prompt templates and a tools comparison across 9 categories.
I'm Ruben. Small remote team, all senior dev/ops with 15+ years each. ano.chat is the chat tool we wanted and couldn't buy.
The headline feature: a real terminal inside chat. A proper PTY in the same window as channels and DMs. I switch between Claude Code and bash in there all day, with chat right next to it because that's where the context already lives.
The reframe: every "integration" is just a CLI. gh, kubectl, psql, your own scripts, whatever MCP server you wired up this morning they already exist. ano.chat gives you a place to run them next to the conversation about why.
Not only for engineers. Devs get the terminal. Sales, ops, design get chat that doesn't suck real threads, real search, an iOS app that handles notifications. Whole company, one workspace.
Self-becoming is an experimental open-source runtime that connects a long-running LLM instance to memory, self-state, reflection, rules, tools, and autonomous rhythms, exploring whether an AI can develop a functional sense of self over time.
I ve been building MapleBridge, a sourcing workflow for North American buyers looking for better-fit Chinese manufacturers.
One thing I kept running into: supplier search is not only a search problem. A buyer can have a very specific brief product, MOQ, target market, packaging, certification path, timeline but most supplier directories still reduce that into keywords and listings.
So I separated part of the work into an open layer.
I wanted to share a tool we ve been working on at Free Document Maker (FDM AI) that addresses a major privacy concern: digital signatures. Most online signature tools require you to upload your files (and your handwriting!) to their servers before you can download a PNG.
We built the Online Signature Generator to be 100% browser-native. Powered by our fdmGTP engine, your drawing stays entirely in your local browser memory.
If you're like me, you probably have 50+ startup ideas sitting in your phone, but you never start because validating them manually takes weeks. And asking standard AI just gives you polite "hallucinations" that sound good but mean nothing.
Hey Product Hunters We re building initdesk an email-first AI help desk for SaaS and lean teams. The idea is simple: support agents should not need to jump between browser tabs, admin panels, CRM, and internal dashboards just to answer a customer.
initdesk brings customer context into the ticket itself, then uses that context to help draft replies, summarize conversations, tag tickets, detect sentiment, and power a help center with AI chat. We also don t charge per seat. You can invite the whole team, and pricing is based on ticket volume instead.
Would love honest feedback on:
1. What customer context would be most useful inside a ticket?
