Lanuch Control

Launch Control is a content-launch engine for nonprofits and small teams. You give it one goal and an event, for example "Get 100 volunteers to our Saturday Ocean Beach cleanup" (surfrider.org, Ocean Beach SF), and a team of Opus 4.8 agents plans, produces, and runs a full week of social content engineered to drive people to that event. How it works, end to end (multi-agent orchestration): 1. Plan + understand. A planner agent studies the goal, the event, and the brand's website, and does live market research with the Bright Data API to learn what actually performs on each platform right now. It produces a 7-day, multi-platform plan where every post has an objective and the days ladder toward the event, with a shared weekly theme. 2. Write. A writer agent turns each slot into platform-native output across five content types: UGC videos, motion launch videos, images, stills, and plain text, with the media rendered through fal. 3. Adversarially review + regenerate. A reviewer/judge agent (also grounded in fresh Bright Data research) critiques every post against that platform's norms and a quality rubric. If it doesn't pass, it sends specific feedback and the writer regenerates, looping until it clears the bar. A multimodal Opus visual critic also looks at each rendered image or video keyframe and grades it for on-brand, on-intent, and "AI-slop" cleanliness, re-rendering failures. 4. Publish. Approved posts go out natively to X, LinkedIn, Instagram, and TikTok via the Zernio API, each with platform-specific copy and media. 5. Create the event. It spins up the real RSVP/event page automatically through the Luma API. 6. Schedule + adapt. It schedules the whole week to crescendo on event day, and checks a Weather API for the event days, automatically rescheduling and adjusting posts if rain is coming for an outdoor event. 7. Engage. A watcher monitors and replies to every comment on its own (via the Zernio inbox), in the brand's voice, and decides what to schedule next. Stack & how it fits together: a Next.js app on Vercel; Supabase for auth, Postgres, and storage (plans + the Asset Bay of brand assets the writer pulls from); Opus 4.8 running the planner → writer → adversarial-reviewer loop; Bright Data for the research that grounds both planning and review; fal for media generation; Zernio for connecting accounts, publishing, and the comment inbox across all four platforms; Luma for real event pages; and a Weather API for forecast-aware rescheduling. The Channels view renders each post inside a realistic native skin (X timeline, LinkedIn feed, IG grid, TikTok profile) using only real connected-account data, no mocked numbers. New users get a free week, then bring their own Anthropic + fal keys (a graceful CTA paywall). Schedule + weather-aware rescheduling (with generative UI). It schedules the whole week to crescendo on event day, then checks the Weather API for the event date. For an in-person or location-based event, if the forecast looks bad, it doesn't silently guess. It surfaces a generative UI pop-up that explains the weather risk and asks you how to handle it: reschedule the event to the next good-weather day (which then cascades, updating the Luma event date and re-timing the whole week of posts around it) or pick another option. Your call drives the plan. This is all live right now. We built and launched every one of these accounts today, and the engine is actively posting to and monitoring them: Claude Coder on X, Claude Coder on LinkedIn, claude_build_day on Instagram, and Claude Coder on TikTok. Go check them. If you comment on our Instagram post (@claude_build_day), Launch Control will automatically reply to your comment on its own (until our API credits run out). We open-sourced it as we built it, and announced the launch on LinkedIn through my post (@Manny2Techy). It's live for anyone to get on and try right now. Link to opensource post:https://x.com/Manny2techy/status/2065895792267702481?s=20