Multiple Deployments, One Config File

If you're building with AI agents, you probably don't have just one. Say you're building a lead aggregation pipeline. You've got one agent that scrapes company websites, another that pulls leads from LinkedIn, and a third that mines Reddit and community forums. They all share the same data models and scoring logic, they all run on a schedule, and they all live in the same repo. But each one deploys independently, so each one needs its own crewship.toml and its own deploy commands, which adds up fast. It works, but it's clunky. You end up duplicating build settings, keeping exclude lists in sync, and jumping between directories every time you deploy. We kept hearing this from teams building multi-agent systems, and honestly ran into it ourselves. So we fixed it. One file, multiple deployments You can now define multiple deployments in a single crewship.toml . Instead of one [deployment] section, use named [deployments.<name>] sections: [build] exclude = [ "tests" , "notebooks" ] [deploy