Lewati ke konten
← Back to All Projects
broadcastwhatsapp.my.id Live 2025—2026

WABlast Pro: WhatsApp broadcast queue with OTP login

Period
2025—2026
Role
Development, security, deployment
Visual summary of broadcastwhatsapp.my.id

01

Key Indicators

30 / 30
tests passing
1
central message queue
OTP
passwordless login

Context & Challenge

Users needed to message hundreds of contacts without losing track: who was messaged, what failed, and which session was used. An interrupted run must not resend messages that already went out.

Constraints

  • —No user passwords stored in any form.
  • —Sending must be idempotent: delivered messages must not repeat after a restart.
  • —Runs on one service with persistent disk to keep operating costs small.

Out of Scope

  • ×No contact lists stored with third-party services.
  • ×Not a paid campaign platform or cross-channel analytics tool.

Technical Decisions

  1. 1

    Each recipient is a queue row with its own status, so a run resumes after a restart without duplicates.

  2. 2

    Login uses email OTP through Resend; no passwords are stored or sent.

  3. 3

    The database and uploads live on persistent disk, while API keys are read only from the environment.

Results

  • 30 tests cover authentication, the queue, and send limits.
  • The admin panel shows per-contact status, send history, and session settings.
  • Runs on a single Render service with persistent disk; later deploys do not erase data.

Technology

  • Bun
  • Node
  • SQLite
  • Resend
  • Render
Visit Site ↗