WatBee
A WhatsApp bulk-messaging platform, built and operated end to end — frontend, API, database and the WhatsApp session layer itself.
ROLE
FULL-STACK · PRODUCT
TIMELINE
Ongoing
STATUS
IN DEVELOPMENT
CATEGORY
Product
CONTEXT & OBJECTIVE
WatBee (formerly WAMaster) is a product I design, build and run myself — a WhatsApp bulk-messaging SaaS for small businesses that need to reach customers without paying for enterprise WhatsApp Business API access.
WhatsApp bulk-messaging SaaS — React on Vercel, FastAPI on Railway, MongoDB, plus a Puppeteer QR-scan sidecar for WhatsApp Web sessions.
0
SERVICES
0
FOUNDER-BUILT
0
OUTSOURCED CODE
THE CORE CHALLENGE
Keeping a WhatsApp Web session alive independently of the main API, without it taking down registration or billing when it inevitably needs a restart — while also fixing the usual first-product list: broken auth, CORS mismatches, and a JSON serialization bug that made registration silently fail.
WHAT I BUILT & DELIVERED
A React frontend on Vercel, a FastAPI backend on Railway, MongoDB for storage, and a standalone Node/Puppeteer microservice purely for WhatsApp Web QR sessions.
Split the WhatsApp Web session handler into its own Railway service so it can restart independently
Fixed MongoDB auth failures, a broken JWT secret, and CORS mismatches between frontend and API
Built a two-step registration flow with email verification via Resend
Scoped CSV bulk import, Stripe/Payoneer billing, and a super admin dashboard
SELECTED VIEWS & SCREENS
Dashboard — campaign overview
01
Backend — API & session logic
02
CSV contact import
03IMPACT & RESULTS
The core send pipeline, auth, and session sidecar are stable in development, with billing and the admin dashboard scoped as the next milestones.
0
SERVICES RUNNING
0
SESSION SIDECAR
0
STEP ONBOARDING
0
PERSON BUILDING IT
THE KIND OF PRODUCT WORK THAT TEACHES YOU EVERY LAYER OF THE STACK.
