Abstract: Deployment of builds of upgrade, patches, and the like may be orchestrated using tables that reside outside the scope of any one environment, but that is accessible by the environments. The tables may define the activities that are pending or running in the system, as well as the dependency chains that prevent activities happening out of safe order (for example, a deployment happening on paying customers before happening in test environments). When a new build is available for deployment, it may be detected and new activities for that build listed as pending in the affected environments. Any activities having no prerequisite dependencies may start immediately, while those with prerequisites may wait for the prerequisite activities to be completed. The encoding of dependencies between activities and across environments may enable access to those from any deployment environment.