RelayOps
RelayOps gives distributed product teams one workflow for incident ownership, response, communication, and reporting. Permissions, tenant boundaries, realtime updates, and audit history remain explicit throughout.
- Role
- Product architecture · Frontend · Backend · Delivery
- Stack
- React 19 · TypeScript · Express 5 · MongoDB · Socket.IO · TanStack Query · Zod · Playwright

Context
Distributed teams often reconstruct incident ownership, deadlines, and decisions across several tools.
The interface needed to expose permissions, responsibility, SLA state, and history without becoming a dense control panel.
Response
A focused workflow combines workspace context, assignment, SLA snapshots, comments, timeline entries, notifications, audit history, and analytics.
The independently deployable frontend and API share validated contracts. URL state keeps incidents, filters, sorting, and saved views addressable.
Contribution
- Designed the product architecture and responsive interface system.
- Built the React application, Express API, shared contracts, realtime layer, and MongoDB model.
- Implemented session security, CSRF protection, tenant authorization, lifecycle email, and role capabilities.
- Created the test, CI, and Render deployment pipelines for both services.
Engineering challenges
- Keeping optimistic state aligned with transactions and realtime revisions.
- Enforcing tenant and workspace permissions at both interface and API boundaries.
- Supporting keyboard, touch, reduced motion, color themes, and narrow screens.
Delivered evidence
- Delivered independently buildable frontend and backend services.
- Created 29 test/spec files spanning contracts, business rules, integration behavior, UI states, accessibility, and browser workflows.
- Targeted coverage reports 96.29% for backend critical rules, 86.36% for frontend critical state, and 100% for shared contracts.
- Documented architecture, data boundaries, accessibility, deployment, and product tradeoffs.








Evidence and publication note
Verified from the public repository, project documentation, reports, and live Render services on 5 August 2026. Coverage figures apply only to the named critical surfaces.