AWTS is modular and highly configurable and customizable out-of-the-box (sic).

However it can also be extended with your own data sources and analytics tools.

The default method is to just use the AWTS modules that make sense for you, and build out the rest of your proprietary environment as 'normal'; treating AWTS as a suite of APIs to help with boilerplate integrations and common-case functionality.

However, you can also build new modules of your own simply by implementing the same API contracts as the AWTS modules do and adding some small administrative logic to register your own modules with mux. By doing this, your proprietary data becomes a first-class part of your AWTS environment and can be fully used across dashboards, the execution engine, and everywhere else.

Please contact us for documentation and support on creating custom AWTS modules.