... because they validated with surveys instead of money. Stack is intentionally boring: Next.js, Supabase (auth + DB), Vercel for hosting, Stripe for billing. The interesting part is the research engine underneath we scrape job boards, Reddit pain threads, and competitor reviews to identify niches where buyers are already spending, then package it into a report with a vibe coding blueprint so you can actually ship it. Permissions/auth is Supabase Row Level Security verbose to set up but rock solid once ... ... tone and created an em-dash epidemic. Users describe intent, get a draft, edit, send. The human stays in the loop. Here's the rub: Stack Next.js 15 and TypeScript, deployed on Google Cloud Run. Postgres and pgvector via Prisma

... full-stack web application for managing medical laboratory operations, built with modern technologies and deployed as a cloud SaaS solution. Key Achievements: I developed a comprehensive LIMS (Laboratory Information Management System) Implemented multi-tenant architecture with Neon PostgreSQL and Prisma ORM Designed PDF report generation with customizable branding and e-signatures Integrated WhatsApp API for automated result delivery to patients Tech Stack: Next.js 14, TypeScript, Prisma

... been working on Kairox Analytics a lightweight, privacy-first alternative to Google Analytics. I wanted something that: Doesn t need cookie banners Respects user privacy by default Works well with modern stacks (Next.js, Edge, Serverless) So I built Kairox open-source and self-hostable . Tech stack: Next.js 15, Prisma

... user-provided error classes in custom mappers (Zod, Joi). Added the ability to enable only selected mappers via configuration, reducing unnecessary checks. Added rate limiting for the logger. Fixed incorrect logic in the express-validator mapper. Expanded supported Prisma errors: P2005, P2006, P2007, P2011, P2027. Improved validation logic for mongoose and sequelize mappers. What does this mean? Starting from version 1.8.0 and above, you can choose which mappers are enabled, so unused mappers are not processed, improving performance. This version ... ... remain dependency-free. Allowing custom error classes keeps this advantage while enabling more precise checks. Previously, built-in loggers had no rate limiting, which could lead to crashes or freezes. This issue has now been resolved. Small improvements New Prisma

... small tool to solve something I kept running into: I plan most of my projects, dashboards, and MVPs in Notion but when it s time to build, I end up manually recreating the schema in Firebase, Supabase, or Prisma. Rewriting fields, guessing types, cleaning mock data It adds friction I wish I could avoid. So I built a tool that connects to your Notion workspace and lets you: View all your Notion databases in one place Clean mock/test data Export ... ... full schema (SQL, Prisma

... small tool to solve something I kept running into: I plan most of my projects, dashboards, and MVPs in Notion but when it s time to build, I end up manually recreating the schema in Firebase, Supabase, or Prisma. Rewriting fields, guessing types, cleaning mock data It adds friction I wish I could avoid. So I built a tool that connects to your Notion workspace and lets you: View all your Notion databases in one place Clean mock/test data Export ... ... full schema (SQL, Prisma