CodeNXT Lab · Product / Bhejna
Bhejna.
Reliable WhatsApp message delivery for apps. Every WhatsApp message BarberBase sends goes through Bhejna. Messages are queued, retried when sending fails, and tracked until they are delivered.
In production as the notification layer of BarberBase. Access by invitation.
01
What it is.
Messages that cannot be silently dropped.
Most WhatsApp integrations accept a message, return success, and lose it when the API is rate-limited or down. Bhejna puts a queue between the app and WhatsApp, so a message that fails to send is retried instead of lost.
Today its one caller is BarberBase, which uses it for every queue alert. Other apps get access by invitation.
02
Architecture.
Queue, retry, track.
- A Go service, routed with Chi. Apps hand it a message over HTTP.
- SQLite in WAL mode holds the message queue.
- A delivery worker sends each message to WhatsApp and retries with backoff when sending fails.
- Every message is tracked, so the calling app can see whether it was delivered.
- Caddy sits in front and handles TLS.
- OpenAPI first: the API contract is written before the code, and the code follows it.
Go · Chi · SQLite (WAL) · Caddy
03
What it does not do.
Delivery only. Nothing around it.
- No two-way inbox. Bhejna delivers messages; it does not host conversations or render a chat UI.
- No campaign builder, audience segmentation, or contact management.
- No analytics dashboard. It reports delivery state; interpreting that is the calling app’s job.
04
Getting access.
Invite only. One WhatsApp message.
Bhejna is invite-only. Send us a WhatsApp message saying you want access, with a line on what your app sends. If it's a fit, we reply with the link to create your account.
Request access on WhatsApp →