PROPRIETARY
Integration of Third-Party Applications within our COTS Products
As part of our commitment to delivering a robust, fully integrated Commercial-Off-The-Shelf (COTS) product, we have embedded and integrated several trusted third-party web applications, toolkits, libraries and SDKs. These components are critical to ensuring seamless functionality, optimal performance, and a unified experience across the platform. When deploying our product(s) in a self-hosted environment, customers have two distinct options for configuring these integrated third-party toolkits:
Option 1: Pre-Packaged Integration via Shared Database Connection String [Recommended]
Customers choosing this option share their Database Connection String (Server Name + Port Number) with us prior to deployment. This enables us to pre-configure and embed the third-party toolkits within the COTS application, ensuring a seamless, secure, and fully supported deployment.
Alternatively, we can configure this at time of deployment via you providing Keyboard and Mouse access via a Webex session.
Benefits of Option 1
Fully Integrated Experience: All toolkits are embedded and tightly integrated within the main application. No additional configuration is required post-deployment.
End-to-End Support: Our team provides full technical support for both the COTS application and all embedded third-party components.
Continuous Feature Delivery: Customers automatically receive all updates and new features made available within the integrated toolkits as part of our standard release cycle.
Cybersecurity Assurance: Configuration is handled by our team following best practices and vetted security protocols, reducing the risk of misconfiguration and vulnerabilities.
Lower Operational Overhead: No need to manage credentials, setup, or integration of third-party components separately.
Option 2: Customer-Managed Credentials via Waiver [Limited Support & Features]
Alternatively, customers may choose to receive and manage the admin credentials for the third-party toolkits directly. This path requires the customer to sign a waiver acknowledging that:
Our team cannot provide support for the third-party toolkits.
The customer will not receive automatic updates or new features for the third-party toolkits.
Any issues arising from misconfiguration, security exposure, or compatibility will fall outside our support scope.
Should support be required later, the customer will be required to revert to Option 1, and the application will need to be redeployed accordingly.
Why Option 1 is Strongly Recommended
Choosing Option 1 aligns with best practices for integration, cybersecurity, and long-term support:
✅ Integration: Our team ensures all toolkits are configured, tested, and embedded to work as a unified system—reducing friction and incompatibility risks.
✅ Cybersecurity: We follow secure configuration protocols, reducing the risk of credential leakage, mismanagement, or exposure from improperly handled third-party applications.
✅ Support: We stand behind our integrated deployments with full lifecycle support. This includes troubleshooting, updates, and new feature rollouts—all of which are not available under Option 2.