Simplify, Speed, & Scale Cloud Infrastructure Delivery

Built to ease your workload, increase DevOps productivity, and control costs and compliance

Torque Features

Self-service

Enable your users to access cloud infrastructure environments as a service (EaaS) through a GUI portal, your CI/CD tools, and a CLI

Seamless CI/CD integrations

Natively integrate into your organization’s DevOps ecosystem and CI/CD pipeline to support continuous environments

Managed Cloud Costs

Eliminate uncertainty and avoid over-spending in your cloud accounts with the ability to automatically tag and de-commission resources, embed policy management, and provide Role Based Access Control to resources

Torque *Integrations*

Torque Integrations

Access hundreds of battle-tested Shells and plug-ins to provide a network environment complete with the technologies you already use in your ecosystem.

See All Integrations

Frequently Asked Questions

Check out the answers to some of our commonly asked questions. Have a question of your own? Contact us!

Torque is a managed Infrastructure as Code solution. It was designed and built to solve the main pain points of infrastructure as code. When modeling your environments with Torque, you can focus on defining your application requirements (e.g. artifacts, variables, networking & compute requirements and test data) while we set up the required infrastructure for you, by translating your application requirements into either AWS Cloud Formation or ARM template

Torque includes out-of-the-box plugins and an extensive REST API for your existing CI/CD and DevOps tools enabling you to easily deploy environments directly from your own release pipeline.

Torque automatically tags cloud resources in environments, and therefore helps leverage automation for properly and consistently tagging cloud resources. Environments in Torque represent business activities like development, testing, troubleshooting, security assurance, staging and production. This means Torque can automatically connect cloud consumption with the business purpose and tag accordingly. It also means you don’t need to hope everyone remembers to tag resources or stick to tag naming conventions across teams, cloud providers, manual and automated cloud usage – it just happens as part of your normal operation. This is a critical foundation for ongoing cloud cost optimization and cloud governance.