Hey PH — I'm Alex, the engineer behind RAID. Anytime we pulled in master we risked breaking our whole environment — builds would randomly fail, dependencies were missing, setup steps that worked last week suddenly didn't. The problem wasn't just the breakage. It was that nobody had written any of this down consistently. Every fix lived in someone's head, a Slack thread, or a Confluence page that was already six months out of date. RAID fixes that by letting you codify your workflows in a simple YAML profile that lives in your repo. Automated testing, manual testing, patching, proxy setup, full environment spin-up — defined once, runnable by anyone, anywhere, consistently. We've been running it in production for over a year. The next chapter is making it AI-first: built-in context generation and an MCP server that gives your AI coding tools the same understanding of your project that your senior engineers have. Open source. Docs at raidcli.dev. Would love feedback on: - First-time setup — does it make sense out of the box? - What workflows do you have that RAID doesn't handle yet? - Anything unclear in the docs?

Raid

Open-source development workflow orchestrator

Open-source development workflow orchestrator

Forum Threads

Request for feedback

Forum Threads

Request for feedback