I'm the solo founder of Korrero. I built this out of my own frustration. On my previous projects, I was constantly getting pulled from core dev work to handle "simple" content updates for marketing (like changing text on a promo banner). It was a huge productivity killer.
So I built Korrero: a headless CMS focused only on notification content. The idea is to be a "peace treaty»:
1. For Marketers/PMs: An intuitive no-code UI to create, schedule, and manage all dynamic content (banners, alerts, etc.).
2. For Developers: A simple API/SDK. You set it up once, and never get a content ticket again.
It's built on a modern stack: Next.js/Tailwind for the lander, React/MUI for the admin panel, and an Express/Prisma/Postgres backend.
We're also launching on Product Hunt today, but I'm here because I'd love the technical feedback from the HN community.
Is this architecture overkill? Is this a pain point you've also felt? I'd be grateful for any thoughts or brutal feedback.
Hey HN,
I'm the solo founder of Korrero. I built this out of my own frustration. On my previous projects, I was constantly getting pulled from core dev work to handle "simple" content updates for marketing (like changing text on a promo banner). It was a huge productivity killer.
So I built Korrero: a headless CMS focused only on notification content. The idea is to be a "peace treaty»: 1. For Marketers/PMs: An intuitive no-code UI to create, schedule, and manage all dynamic content (banners, alerts, etc.). 2. For Developers: A simple API/SDK. You set it up once, and never get a content ticket again.
It's built on a modern stack: Next.js/Tailwind for the lander, React/MUI for the admin panel, and an Express/Prisma/Postgres backend.
We're also launching on Product Hunt today, but I'm here because I'd love the technical feedback from the HN community.
Is this architecture overkill? Is this a pain point you've also felt? I'd be grateful for any thoughts or brutal feedback.