I built sapat.chat, a lightweight SaaS for websites that includes live chat, tickets, and a knowledge base.

What: Minimal live chat + support inbox with real‑time updates and an easy embed.
Why: Curiosity to learn how live chat works and because integrating Chatwoot into HostedStatus.page was painful (CSP issues/theming/embed). So I scratched my itch and shipped an MVP to see if it’s practical (and maybe profitable) 🤞🏻Even if it gets no users, it's not all for nothing because I use it ☺️
If you’ve wrestled with chat widgets, please give it a try and tell me what’s missing/wrong. 🙌🏻
🧐 A bit more context
The name "Šapat" means "whisper" in Serbian (and neighboring countries!) - a nod to quiet, personal communication. I wanted a tool that stays out of anyone's way, like a whisper between two people, not a megaphone.
What’s inside today
Drop-in widget + clean (I hope) staff dashboard.
Real-time chats via WebSockets with polling fallback.
Notifications and a simple “take chat” flow for agents.
CSP-friendly embed that plays nicely with any site.
Simple Knowledge Base and Ticketing
Who it’s for
Indie makers and small teams who want something simple that doesn’t fight your UI or deployment setup.
Why now
I kept hitting edge cases, embedding existing tools (CSP, styling, and integration friction). Rather than keep fighting it, I built the MVP I wanted and put it live to see if it resonates.
What’s next
Smoother onboarding, docs, a couple of lightweight integrations, and tightening the admin UX based on early feedback. Pricing TBD after validation; the ones on the site are just placeholders/temporary.
🆘 Want to help?
Thank you in advance! ❤️ Kick the tires, share where it breaks or feels rough, and tell me which “one missing thing” would make it a no-brainer for you. Happy to trade feedback and share my thoughts, give your product a spin if my thoughts will help! ☺️