Vioset
Save smarter, not harder — AI-powered bookmark manager
After a few months of building solo, I shipped Vioset — a bookmark manager that uses AI to summarize saved pages, so you don't forget why you bookmarked something.
Background: Self-taught developer, came from an electrical installation background, did a fullstack JS program, and wanted to build something real — not just a portfolio tutorial clone — to prove I could ship end-to-end: auth, billing, AI integration, the works.
The problem: I kept saving links "to read later," then coming back weeks later with zero memory of what they were or why they mattered. Classic bookmark graveyard.
What it does:
- Nested collections + tags for actual organization (not a flat list)
- AI-generated summaries and key takeaways for every saved page (Premium)
- Instant search across titles, descriptions, and URLs
Tech: Next.js 16, TypeScript, PostgreSQL/Prisma, Better Auth (email + Google OAuth), Stripe subscriptions, Google Gemini for AI summaries.
Pricing: Free (15 bookmarks) / Premium $5/mo or $50/yr (unlimited + AI summaries).
Live: vioset.com
Would love feedback on:
1. Does the AI summary feature feel genuinely useful, or like a bolt-on?
2. Is $5/mo reasonable for what's offered, or off in either direction?
3. Anything confusing in the onboarding/sign-up flow?
Happy to answer questions about the build process, the stack, or specific technical decisions.
4 Comments
Just launched Vioset on Product Hunt today!
If you want to support, search "Vioset" on Product Hunt 🙏
Would love any feedback or upvotes from the IH community!
The interesting part here isn’t saving bookmarks—it’s restoring intent. Most tools help you store links or find them later, but the real failure point is losing the context of why you saved something in the first place. AI summaries help, but the real value is probably in surfacing that intent at the moment of return.
Exactly — "restoring intent" is the frame I've been
building around, even if I hadn't articulated it that
cleanly. The summary helps, but you're right that the
real unlock is surfacing it at the moment of return,
not just on demand. That's the next layer I'm working
toward — proactive surfacing rather than passive storage.
Thanks for putting that so precisely.
Glad it resonated.
Your reply made me think there's one strategic decision sitting underneath that shift from passive storage to proactive surfacing which becomes much more significant as the product grows, but I don't think I can explain the reasoning properly in a thread without oversimplifying it.
If you're interested, what's the best email to reach you on?