Founder
Coffey Vidzro
Focused on backend architecture, telecommunications infrastructure, messaging gateways, and reliable delivery systems.
About Dugble
Messaging infrastructure should be easier to debug.
Dugble is being built for teams that send customer-critical messages, OTPs, receipts, alerts, and updates - and need to know exactly what happened after every API call.
The point of view is simple: send the message, keep the receipt, and make every failure easier to explain.
What it actually is
A messaging API, built on real identity infrastructure.
Underneath the SMS and Email APIs is a lightweight Go HTTP server handling multi-tenant identity and team management, the same foundation a full product needs, not a messaging script with an API bolted on top.
Messaging layer
What you integrate against
SMS APIEmail APISigned webhooks
Identity & team layer
What makes it a real multi-tenant platform
Browser authenticationTeam membershipScoped team tokens
How it's built
A few opinions we don't compromise on.
Every request is traceable
A message_id isn't an afterthought. It's returned on accept, searchable in logs, and referenced in every webhook event that follows.
Security is a default
Scoped tokens, signed webhooks, and session checks aren't a paid tier. They're how the request path works for every workspace.
Small, honest surface area
Fewer endpoints that do exactly what they say, over a large API that's easy to misuse.
Built for the terminal, not just the dashboard
If something can be done with curl and read in a log line, it shouldn't require clicking through five screens.
Under the hood
Tokens scoped to a team, not a person.
Every request carries a token scoped to a specific team and workspace, not a shared account key. Security middleware checks the session and signature before a request ever reaches messaging logic.
Read the full security modelScoped requestworkspace-isolated
GET /v1/messages/msg_9c41af HTTP/1.1 Host: api.dugble.com Authorization: Bearer tk_team_8f2ac1 X-Dugble-Workspace: wsp_4b71ea
Where it started
Early, in the changelog.
Rather than tell you a founding story, here's what actually shipped first.
Template data validation
Sends with a template now fail fast with a clear error if required template_data fields are missing, instead of sending a partially-rendered message.
Sandbox messages appearing in production logs
Sandbox test sends were briefly visible in the production log view for workspaces created before April. Log scoping is now consistent for every workspace.
Workspace-level webhook signing keys
Each workspace now gets its own signing key, so rotating a key in one workspace no longer affects others.
Team
Founders building Dugble.
Co-Founder
Prosper Kessie
Focused on developer experience, API and webhook architecture, SDK engineering, and product design.
Send your first message in the next five minutes.
Create a workspace, generate an API key, and watch the delivery event come back in the dashboard.