Technology Platform

FittedCloud is a dynamic resource optimization solution for public clouds. It uses patented technology to constantly monitor and adjust cloud resources based on application utilization. It resizes resources with zero or minimal impact to applications. The solution architecture is composed of four major components.

Information Collector

The FittedCloud Information Collector uses APIs to constantly monitor customer environments. It collects utilization information for managed resources and stores it in a database.

Decision Engine

The FittedCloud Decision Engine uses machine learning and other algorithms to analyze the collected information and make optimization recommendations. Machine learning predicts resource utilization based on past usage. In some cases, recommendations are based on real time information.

Optimization Agents

Resource-specific Optimization Agents execute the recommendations prepared by the Decision Engine. Execution is completely transparent to the application, wherever possible. (Note: For EC2 compute and EBS, agents need to be installed on customer instances). In certain cases, customers must confirm actions prior to executing recommendations. Agents also ensure that resource utilization is monitored constantly and any further adjustments (up/down) are performed as needed.

Reporting Tools

Fitted Cloud Reporting Tools provide information on service utilization and cost savings. The reporting timebase is user selectable.

Deployment Options

FittedCloud solutions can be deployed in two ways depending on the customer’s needs.

SaaS/Hosted: Fitted Cloud manages the Decision Engine, Information Collector and Reporting Tools, ensuring they are always up-to-date and optimizations will be the least disruptive. Customers deploy the Optimization Agents in their environments. There are no upfront cost with this option.

Enterprise: All Fitted Cloud components are deployed in the customer’s environment. There are multiple reasons customers may want to run it within their environment. The key difference here is that customers will not have to share any IAM credentials. There is a small initial startup cost with this option.

Both deployment options offer identical features and functionality and are extremely secure. The only variance is in the setup process.