Everything goes through queues
Send peaks never affect the publishing systems.
Our own cores
Multichannel messaging
Email, Telegram and WhatsApp from a single service.
LaravelVue.jsRedisMySQL
The challenge
Each system sent emails and messages its own way: no retries, no history, no limits and credentials scattered around. When a provider failed, messages were lost without anyone noticing.
How we solved it
We created a multi-tenant messaging core with a panel and API. Systems publish a send and the core queues it, delivers it on the right channel, retries on failure and keeps the history.
Architecture
How it is built.
Simplified view of the components and how information flows.
01
Source
System events
Campaigns from the panel
02
Core
Templates & white-label
Plans, quotas & limits
03
Queues
Workers & retries
Attachment antivirus
04
Channels
WhatsApp Cloud API
Telegram & email
LaravelVue.jsRedisMySQLWhatsApp Cloud APITelegram BotsTransactional emailDocker
Technical decisions
Why we built it this way.
Limits per plan and company
No customer can saturate the platform or exceed their plan.
Delivery receipts
You know which message arrived, was read or failed.
Scanned attachments
Files go through antivirus before being sent.
AI-assisted inbox
Incoming conversations are supported by the AI core.
Outcome
What changed.
- Products send messages with a single API call.
- Centralized, traceable history of every send.
- Automated tests and API documentation for integrators.
Ready to build what’s next?
Let’s find the right solution for your business.
Tell us about your goals and one of our engineers will get back to you personally.