WhatsApp has 3B+ users and 98% open rates. You'd expect developers to be building tons of stuff on it, especially when the US is the fastest-growing market in WhatsApp usage.
But it’s not happening… And I'd bet it's because the DX is painful.
Every team needs to build the same features again and again. Meta fires webhooks for everything. There's valuable data in there for debugging, but no way to make sense of it without building your own tooling.
That’s why I built Kapso. What you get:
- Working WhatsApp API + inbox in 2 minutes, not days - Full observability: every webhook parsed, every message tracked, actual debugging tools - Multi-tenant platform: generate a setup link, customer connects their Meta account, done - Workflow builder for deterministic automations and AI Agents - WhatsApp Flows: build mini apps inside WhatsApp using AI + serverless functions - Docs that work for humans and LLMs
We're up to 95% cheaper than Twilio, with a generous free tier (2,000 messages per month).
We also open source several tools: a TypeScript client for the WhatsApp Cloud API, a reference WhatsApp Inbox implementation, and a voice AI agent for WhatsApp.
GitHub: https://github.com/gokapso/
Happy to answer questions!
gonzalovargas•16h ago
Building software today increasingly means integrating dozens of external services rather than building systems end to end. Email, auth, analytics, billing, AI tooling, and observability each come with their own accounts, configs, SDKs, and API keys.
This composability is powerful, but increasingly inefficient.
It makes me wonder when we’ll see a platform that bundles these services with unified accounts, billing, auth, and configuration by default, instead of having to configure and manage each one independently.
aamatte•15h ago