Skip to content

About OptScale#

Our cloud management platform is all about flexible provisioning scenarios and efficient cloud bill control.

Hystax OptScale primary capabilities#

  • Pool Transparency

Pool breakdown and transparency across all business units, users, projects and individual cloud services. The customer sets soft and hard limits.

  • Simple multicloud asset provisioning workflow via dashboard or API

A single OptScale dashboard is used to manage hybrid clouds along with the virtual machines, volumes and network settings. Custom and mandatory tagging is supported. Custom TTL rules can be created to clear out workloads according to customer's policies.

  • Flexible alerts and notifications

Custom notifications about all related events, e.g. immediate workload volume increase, pool forecast overdraft or unusual behavior.

  • Swift user creation and business units distribution

Step-by-step guides for configuring user settings, organization subdivisions, pools and quotas assignments.

  • Seamless Hybrid Cloud Migration

Cloud migration and cross-cloud disaster recovery with RPO/RTO of seconds and minutes that provide workloads mobility between public and private platforms. Complex migration scenarios and orchestration are implemented to save machine metadata and network settings.

More features are just around the corner and will be introduced shortly! Extensive support documentation is on the way as well.

How it works#

OptScale is dedicated to improve cloud usage experience but does not actively interfere with processes in your environment since it only requires Read-Only rights for the connected cloud account which is used as the main data source for all recommendations.

The following data is used:

  1. Billing info - all details related to cloud expenses.
  2. State of resources (for actively discoverable types) in the cloud - necessary for applying Constraints like TTL and Expense limit as well as for OptScale's Recommendation Engine.
  3. Monitoring data from the cloud used for identifying underutilized instances.

Naturally, every cloud platform differs in the way the above data is obtained.

Amazon Web Services (AWS)#

1. Billing information is retrieved from the Cost and Usage Report (CUR) located in a designated S3 bucket in the cloud:
2. Resource discovery is performed via Discovery API:

3. Amazon Cloud Watch is used as the source of monitoring data.

Microsoft Azure#

1. Billing information is acquired via Billing API:
2. Resource discovery is performed via Discovery API:

3. Cloud's Monitoring service is used as the source of all monitoring data.

Kubernetes#

Kubernetes clusters require installation of Prometheus which is a pull-based monitoring tool used for:
  • collecting metadata on pods and nodes;
  • resources discovery;
  • hardware utilization on nodes. This consumption details are recalculated into Expenses based on the detected / user-defined cost model.