The single reference for all 14 Boom Media SaaS apps: current status, what's actually working today, what's blocked, and step-by-step how to use each one. Built to live inside the admin and client dashboards — flip the view toggle to switch between the operator lens and the client lens.
One rule: no two apps do the same job. Each app owns a single lane; where jobs overlap, one app wins and the others call it. Reviews → Localey. Loyalty → Rewardee. Chat → Replyee. E-sign → Signnee. Signage/cameras → Displayee.
Current phase — internal & embedded. Every app is used with your own agency clients right now, embedded into their websites (widgets, portals, flows you run on their behalf) — not sold as standalone logins yet. Once each is proven in real client use, the suite gets white-labeled and sold to agencies & freelancers who resell to their own clients.
Shared rails. Apps don't each reinvent infrastructure — they share one Supabase database, Stripe billing, Resend email, Bunny CDN, and purpose-built engines (DocuSeal for signing, MediaMTX for video, RustDesk for remote support).
Send contracts, NDAs and agreements for legally-binding e-signature. Reusable templates, multi-signer, reminders, branded signing emails. Powered by self-hosted DocuSeal.
api.docuseal.com (cloud) instead of sign.boommedia.us — env mismatch to fix.sn_* migration ran; 0 webhooks configured.DOCUSEAL_API_URL=https://sign.boommedia.us/api and confirm the Coolify box is up./api/stripe/webhook; run sn_* SQL.Generates social/ad creative and AI-avatar videos (HeyGen) for clients. Deployed and in use.
Generates and publishes SEO blog content for client sites. The most mature build — used as the design/brand reference for the suite.
Tracks keyword rankings and SERP position for client sites over time.
Runs on-screen content (menus, promos, TV displays) and live security-camera streaming. Camera feature shipped & live — embedded inside the BOO console too.
/dashboard/admin; client at /dashboard/cameras & /cam/[id].?key=. XMEye/Gurapos cams need an on-site bridge.Embeddable AI chatbot (retrieval-augmented) with SalesIQ-style live-chat handoff. Chat & live chat only — not review replies (reviews live in Localey).
OPENAI_API_KEY on prod → ops ingest API can't run.002_live_chat.sql ran on db.boommedia.us; E2E not verified.OPENAI_API_KEY on prod.Generates dynamic, trackable QR codes (menus, links, campaigns) with scan analytics.
/client route and billing portal.Client-facing reporting dashboards — the reseller channel for the service industry. A standalone product, not a BOO feature. Surfaces data from other apps (e.g. Localey reviews) to clients.
/portal built.api/admin backend routes exist. Needs an admin dashboard built.Scans & monitors client sites for ADA/accessibility issues, plus Wordfence-style attack blocking/reporting. Never marketed as "makes your site compliant" (FTC precedent) — it scans & monitors.
@boom/shield) is spec-only.The loyalty engine — points, rewards, gift cards, and staff recognition (/rate). BOO consumes it: every order calls POST /api/external/earn to award points.
001→004 not run on db.boommedia.us; Stripe products ($29/$59/$99) + env vars pending.001→004 SQL; create Stripe products; set env vars.Clients review & approve content and video (timecoded comments). Also drives a feedback → GitHub issue → Claude Code auto-fix → PR pipeline (never auto-merges to prod).
Local reputation: review collection/management + citation building. The shared reviews engine consumed by BOO (restaurants) and Dashee (service-industry reseller). FTC rule: no review-gating.
Schedules & publishes social posts across Meta, Google Business and LinkedIn via their direct APIs (swappable adapter — moved off Ayrshare for cost).
pt_); client dashboard present.Remote-desktop support for clients, on a self-hosted RustDesk engine.
/admin pattern (stat cards → accounts table → engine/revenue side cards).| App | Client dashboard | Admin dashboard | Note |
|---|---|---|---|
| Addee | ✓ | ✓ | — |
| Bloggy | ✓ | ✓ | — |
| Displayee | ✓ | ✓ | admin at /dashboard/admin |
| QRcodee | ✓ | ✓ | — |
| Rankee | ✓ | ✓ | — |
| Replyee | ✓ | ✓ | — |
| Signnee | ✓ | ✓ | — |
| Approvee | ✓ | ✕ | needs admin UI |
| Assistee | ✓ | ✕ | needs admin UI |
| Compliee | ✓ | ✕ | needs admin UI |
| Dashee | ✓ | ✕ | api/admin only |
| Localey | ✓ | ✕ | needs admin UI |
| Posttee | ✓ | ✕ | needs admin UI |
| Rewardee | ✓ | ✕ | needs admin UI |
This file is fully self-contained (no external scripts/fonts) so it drops into any app. Two ways to use it:
1 · Help/KB route. Add a /help or /kb page in each app and iframe this file, or copy the relevant app section into the page. The Client / Admin toggle up top swaps which how-to steps show — point the client dashboard's help at the client view and the admin's at the admin view.
2 · Contextual panel. Each app card carries a data-search and data-status hook — a dashboard can deep-link to a single app's card. The status board + coverage table make this the one place to answer "what's live / what's blocked" without digging through repos.
Admin-only content (blockers, keys to rotate, migrations to run) is hidden in Client view via a CSS class — safe to expose the same file to clients as long as it loads in the client (default) view.