RaidRunner
7/11/2026
The landing page is a weekend clone, but the actual product is a small Twitch-adjacent SaaS with a scheduling engine, live-status system, and an AI/MCP integration a prompt can't fake.
You can clone the retro-styled landing page in a weekend, but not the streamer/team network already scheduling real raid trains on the platform.
Low effort for the landing page, but the real product requires building a full scheduling backend with live Twitch status and OAuth — worth it only if you genuinely want to compete in a small, already-crowded raid-train-tools niche rather than as a portfolio flex.
Niche but persistent demand within the Twitch streamer growth-hacking community; multiple competing tools already exist for the exact same "raid train" coordination problem.
$20-75 (Vercel/Next.js hosting, Postgres DB, Twitch API calls, image generation compute)
Free-to-use community tool with no visible monetization; a clone could monetize via premium team/event tiers, sponsored overlays, or an API tier — similar to how R3dLabs sells AI chatbot credits.
R3dLabs / FirePanel, RaidPal, TwitchTrains.com, Discord-based raid train communities (e.g. Streamers Paradise)
unclear — currently free for streamers with no visible pricing page; likely funded by ads, sponsorships, or future premium team/API tiers
Very small (~100-500 visits/day per third-party estimate), niche audience, likely flat-to-growing with new ChatGPT/MCP feature push
Next.js (App Router) + Supabase (Postgres, Auth via Twitch OAuth provider, Realtime) + Twitch Helix API + Vercel
Supabase Next.js SaaS starter (or T3 Stack) with Twitch OAuth added via NextAuth/Supabase Auth custom provider
- 1.Scaffold Next.js app, port the static landing page, feature grid, and FAQ schema
- 2.Add Twitch OAuth login via Supabase Auth / NextAuth Twitch provider, storing minimal user profile
- 3.Model DB schema: users, events, slots, teams, team_members, messages, waitlist_entries
- 4.Build event/slot scheduling CRUD + a queue/waitlist + slot-trading logic as server actions/API routes
- 5.Add a cron/worker (Vercel Cron or Supabase Edge Function) polling Twitch Helix 'get streams' for live status per participant
- 6.Implement iCal feed generation (ics library) and CSV export endpoints
- 7.Build a public REST API + an MCP server route (/mcp-connector) exposing events/lineups to ChatGPT tools
▸Technical evidencefacade · hidden · 9 signals · DR 24ShowHide
A prompt can nail the Next.js marketing page — the retrowave hero, SVG feature icons, FAQ schema, and static nav/routes for Events/Streamers/Teams pages with placeholder data.
Behind the facade sits Twitch OAuth login, a real database for events/teams/slots/messages, live-status polling of the Twitch API, a scheduling/queue/trading engine, iCal & CSV export, an image-generation service for lineup graphics, a public API for overlays, and an MCP server exposing the whole thing to ChatGPT.
Clonable and beatable — the fun kind.
Get the full build plan →