Media, broadcast & mission
A livestream-and-chat platform rebuilt right after the audit failed it.
A real-time streaming + moderated-chat system re-architected from a 2,300-line monolith into modular components after a security and performance audit.
A private membership community ran its live video and real-time chat on a 2,300-line monolithic plugin. An audit found what monoliths hide: an authentication bypass in the chat-presence layer, N+1 query storms, cross-site-scripting exposure, and missing rate limits, real security and performance liabilities on a system members used live.
We ran the audit formally, cataloguing the critical, high, and medium findings, then re-architected the plugin from the monolith into single-responsibility modules: separate components for database, access control, real-time presence (Pusher), moderation, chat, REST API, webhooks, and shortcodes. An HLS player handles adaptive video, membership-gated channel auth closes the bypass, and moderation, bans, an API, and webhooks round it out. The rebuild shut the auth bypass, killed the N+1 queries, patched the XSS, and added the rate limiting the monolith never had.
- Members can trust a real-time system with live participation. The authentication bypass, XSS, and rate-limit gaps the audit found are all closed.
- A modular architecture replaced a 2,300-line monolith, so the platform can be maintained and extended instead of feared.
- Performance liabilities (N+1 query storms) were engineered out. The chat and presence layer scales with the audience.
- The audit-then-rebuild discipline means the fixes are documented and verifiable, not just “we cleaned it up.”
security holes found and closed
auth, XSS, and rate-limit gaps fixed
real-time chat + video under load
gated, membership-authed channels
Client name and identifying details withheld by design. Every figure here is drawn from the system we actually delivered.
More case studies
All workMembership & advocacy · Organization-wide platform
One operating platform for a 600,000-supporter organization.
ReadData architecture · Coordinated back-office systems
Four department systems that finally agree on who someone is.
ReadCommunications · Deliverability engineering
A self-hosted email operating system, built to survive Gmail.
ReadYour work would get the same discretion.
Tell us what's breaking. We'll tell you whether we've solved something like it. And if we take it on, your name stays yours.
Start with a diagnostic