Launch day taught me one thing: speed is everything, but flexibility is a close second. My next step for Kitlaunch is to move beyond just 'page templates' and start building a library of high-end interactive components (think animated bento grids, glassmorphic forms, and GSAP-powered scroll effects) that can be dropped into any React/Tailwind project. I m curious, when buying a UI kit, do you prefer full-page layouts or a massive library of individual components that you can mix and match? Which one saves you more time?
TLDR: I built Cursor for Blender which generates clean wireframes.
Let me start with a confession. I'm a terrible 3D artist. Like, genuinely bad. Every time I opened Blender, I'd spend three hours trying to model something simple and end up with a geometry crime that looked like it was designed by someone who has never seen a real object before.
But here's the thing. I needed 3D assets for my projects. Game prototypes, architectural mockups, product visualizations. And hiring a 3D artist for every little thing, specially to send proposals and to make drafts, was not in the budget.
So I did what any developer with too much free time and not enough common sense would do.
I wanted to share a milestone: I ve successfully scaled a web platform to 1 Million+ monthly active users using a completely serverless, "Zero-Cost" architecture.
The Tech Stack:
Frontend: Next.js (Deployed on Vercel/Cloudflare Pages)
Backend: Supabase (PostgreSQL) for scalable data management.
Automation: Integrated Gemini AI to automate content generation and SEO metadata.
Deployment: GitHub CI/CD for seamless updates.
Key Achievement: Managed to maintain a 90+ PageSpeed score and handle massive concurrency without spending a rupee on servers. By leveraging AI and Edge computing, I ve optimized the entire pipeline for both speed and scale.
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 built Sharpread, a forensic SEC filing analysis tool, on a standard in-process rate limiter for managing requests to the SEC EDGAR database. It worked perfectly in development and in early production.
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?
Anyone else tired of habit trackers that are either paywalled or too distracting? I am building a simple app for macOS that lives in your menubar. Forever free, no subscriptions, no paywalls. Clean UI with groups and tasks to stay organized. Launching in May, happy to hear feedback!
Use the AI Agent to have conversations about artists you search for get more info, similar artists, best songs, best albums, best live concerts, and more.
Listen to an artist's full discography without interruptions.
Accepting new independent artists to register and upload their music.
