The Clarity SaaS platform hosted by Rego Consulting makes use of highly scalable Amazon Web Services infrastructure. The nature of this architecture provides an exceptionally enterprise-grade platform for Clarity, providing security, scalability, and high performance. A key aspect of the platform is the stability and scalability of Clarity, where the infrastructure will automatically scale up as Clarity workloads increase. As new users make requests in Clarity, or certain processes require heightened resources, the AWS infrastructure scales to accommodate that with no interruption. As such, certain customizations to Clarity restrict this ability. Any custom JARs that must be installed into the AWS infrastructure immediately expose potential risks, as these JARs are not developed or supported by Rego. In addition to the risks, the automatic scaling of the AWS resources cannot be fully realized. In order to provide the most stable, secure and supportable platform for Clarity, Rego will no longer support custom JAR file integrations as of the end of 2022. Rego has converted most customers from custom JARs to Rego-native integrations over the last year with great success. Major improvements to quality and stability are achieved.
Improvements after converting to Rego's native integrations:
No special logistics are necessary pre or post Clarity upgrades, the Rego integrations are native to Clarity on AWS.
Dramatic improvements to quality as the Rego integrations are native to Clarity on AWS, not generic custom JAR files
Significantly reduced costs, the Rego integrations involve a one-time fee, no subscription is required
Single source of support, all issues related to Clarity, integrations or backend AWS infrastructure are handled by the Rego team
We are executing this initiative with your best interests in mind, to improve the success and stability of your Clarity environments hosted by Rego. All custom JAR files will be removed from Rego-managed platforms by the end of 2022, without exception. We look forward to planning this important conversion with you.
Additional considerations:
Rego is not responsible for securing, supporting, managing, maintaining, assuring or custom JAR files
Rego cannot provide support or troubleshooting for custom JAR files, as they are not developed by Rego
Rego cannot provide comprehensive auto-scaling of AWS with custom JAR files