Boost Developer Productivity with Self-Service Cloud Access

Yes! Our Torque platform allows you to determine who can create environments and modify infrastructure, and who can only view and deploy the environments. This includes restrictions on who can set maximum duration for an environment runtime or who can apply or change the tag to an environment before launching. Torque draws the line between those who orchestrate environments and those who consume them.

Quali’s Torque is not intended to replace Terraform for scripting. In fact, Torque embraces and extends the value of your existing Terraform scripts.

The Torque platform is designed to help our users seamlessly and safely access and rapidly deploy their existing Terraform scripts. Torque is unique for its ability to automatically identify and map multiple configuration types (Terraform, Helm, CloudFormation, Kubernetes, and vCenter) into a single repeatable blueprint. This eliminates the manual work required to configure Terraform scripts to work alongside Helm Charts or Kubernetes manifests, while also making those complete environments repeatable.

Further, Torque ties Terraform-configured infrastructure elements to business context–who owns it, operates it, its purpose, the application and/or business that it enables, and what the infrastructure costs to operate.

Think of Quali’s Torque as a unified control plane for all your infrastructure assets.

The Torque platform was designed to enhance your existing workflows. That means automating the entire lifecycle of environments directly where–and when–they’re needed. Torque will automatically deploy the right environment at the onset of a new stage of the CI/CD pipeline, then shut that environment down after that stage is complete. Torque currently support deployment on infrastructure within Jenkins, Azure DevOps, and CircleCI.

Yes. With Torque, infrastructure teams can enforce security and compliance by configuring environment blueprints with secrets and cloud account credentials securely embedded (and invisible to the user) to conform to policies that mitigate business risk. Torque’s policy engine, powered by Open Policy Agent (OPA), can embed guidelines for user access, cost, usage, and governance into the infrastructure provisioning process.

Quali’s Torque supports policies based on Open Policy Agent. Those with Admin permissions can set individual policies to allow or prohibit activity that doesn’t adhere to your standards, including launching specific cloud platforms or services, instance types, or configurations such as public AWS S3 buckets.

Admins can choose to apply these policies to all users in their Torque account or to apply to individual Spaces, which can be tailored to support specific teams or infrastructure.

Torque can automate the orchestration of a new environment in minutes. Torque allows you to discover and import infrastructure definitions directly from your GitHub, GitLab, and Bitbucket repositories, then automatically orchestrates a YAML file consisting of the specific assets you choose to import. This eliminates manual provisioning tasks that often slow the process down, and makes those environments repeatable so you can launch them any time you will need them in the future.

Quali’s Torque allows you to view the underlying infrastructure within your entire environment. This level of introspection allows you to verify that the environment is built and configured to meet your specific needs before you deploy.

Torque also detects application drift in your infrastructure assets automatically, and notifies admins in the event of any unexpected changes that may disrupt the environment. These notifications include details on the specific change so your infrastructure admins can resolve the issue rapidly.

Those who integrate their environments with a CI/CD or ITSM tool can carry out their day-to-day tasks with the peace of mind that all their environments are up to date and managed continuously.