Continues Integration system which has been developed for distributed networking execution environment. It started its life serving builds and tests in a commercial environment early days well before continues integration became a standard well-applied best practice in the industry. The code was open-sourced and was used by multiple local development teams known to the author. Later on alternative CI systems, like Jenkins and BuildBot, gained popularity, established big communities and evolved more, covering functionality of ExecKit, like automated remote execution abilities. Drop of usage of ExecKit caused the project being declared as Inactive.
Positive response from beta testing. Unexpected variety of features to define testing targets. Flexibile and easy to troubleshoot.