Nicheloom

Market intelligence for builders — see what's gaining traction before it's crowded.

Kapso

WhatsApp for developers

Details

External ID
46368379
Source
HN
Company
—
Product
Kapso
Website domain
kapso.ai
Launched
Dec. 23, 2025
Cohort
—
Upvotes
48
Upvotes percentile
0.8129770992366412
Tags
—
Fetched at
Sept. 7, 2026, 9:25 p.m.
Updated at
Sept. 7, 2026, 9:25 p.m.

Description

Hey HN, I'm Andres. I've been building Kapso as a solo founder, and just crossed 4,000 developers, all organic.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 LLMsWe'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!https://kapso.ai/

Enrichment

Theme
autonomous ai agents for business
Vertical
Horizontal
Function
Communication
Audience
Developer
AI stance
Not AI
Project type
Commercial product
Normalized one-liner
messaging platform for developers
Manually corrected
False

Could you build this?

Partial The developer portal and webhook handlers are easy to vibe-code, but becoming an official WhatsApp Business Solution Provider (BSP) or reliably managing WhatsApp Business Cloud API scaling requires external vendor approvals and telecom-grade reliability.

What it would actually take: The architecture uses a Node.js/Go backend wrapping Meta's WhatsApp Cloud API or running on-premises WhatsApp Business API nodes, backed by distributed queue systems (e.g., Redis/RabbitMQ) and PostgreSQL for idempotency and webhook event distribution. The main hurdles are surviving Meta's BSP onboarding, compliance, high-throughput rate-limiting, and managing edge webhook deliverability at telecom volume. Doing this properly requires enterprise messaging infrastructure experience and navigating Meta's partner ecosystem.

Discussion

20 comments analyzed.

Competitors mentioned: Twilio WhatsApp API, Meta API (official)

Concerns raised: Meta/Facebook account required for number and templates, .ai domain name confuses people about AI focus, Facebook account hard requirement frustrates some users

Feature requests: WhatsApp group management support, Instagram/LinkedIn integrations, Support for other channels beyond WhatsApp

Competitors

Other products that read as similar to this one — 139 launches clear the similarity bar, closest 8 shown.

Attention rank: #16 of 140 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).

Launched 44 days after the earliest competitor.

Other launches for this product