I build backend services, messaging infrastructure, and platform foundations that are meant to stay clean, stable, and usable under pressure.
Right now I spend most of my time on:
- multi-session WhatsApp API systems
- webhook and queue-driven backend flows
- deployment patterns that stay lightweight but production-ready
- internal tooling that reduces noise instead of creating more of it
| Area | What I'm doing |
|---|---|
| WhatsApp API | Building multi-session architecture, QR/pairing flow, reconnect handling, and worker-based runtime control |
| Messaging Infrastructure | Improving webhook delivery, queue-backed processing, and downstream reliability |
| Platform / Ops | Keeping VPS deployment practical with PM2, Nginx, Redis, PostgreSQL, and predictable service layout |
| Backend Systems | Designing APIs and internal services that are automation-ready and easy to maintain |
- prefer systems that are calm to operate, not flashy to demo
- optimize for stability, readability, and recovery paths first
- care about operator experience as much as implementation detail
- scale deliberately: add weight only when it earns its place
A lot of the best backend work starts quietly: small internal tools, careful cleanup, then steady hardening until they are ready for real use.
If you're here for backend systems, messaging infrastructure, and practical platform work, you're in the right place.