For the latest on new releases or to become a Design Partner to share your input, sign up below.
Execute a Couple of Commands:
build and apply
torque deployment build local
torque deployment apply local
torque deployment build prod
torque deployment apply prod
Create Deployment Objects by Selecting a List of Deployment Provider Implementations
torque deployment create local torque.docker_compose.V1Provider
torque deployment create prod torque.do.V1Provider torque.k8s.V1Provider
Create a DAG Representing Your Cloud Architecture
Create Torque Workspace
torque init my_workspace
To Deploy to DigitalOcean, Kubernetes, and Docker Compose
An Example of Torque at Work
Kubernetes and Terraform, coupled with all services that cloud providers offer these days, have provided incredibly powerful tools for running cloud systems. However, the level of complexity they introduce can be daunting for many teams, often creating technical debt accumulation, slowdowns, and roadmap disruptions for refactorings or rearchitecting.
Torque allows engineers to design and easily evolve their systems without being constrained by fragile manual configurations of development environments and cloud deployments.
Being removed from static configuration files gives software engineers the power to deliver new features fast without breaking things or accumulating technical debt.
Why Torque Framework?
Cloud Beyond Terraform and Kubernetes
Make big changes fast, with a few simple commands.
Torque is a new kind of open-source framework for development operations. It elevates work from the configuration level of HCL, YAMLs and scripts, to the level of architecture design, powered by code libraries.
By installing different code libraries you can:
keep your local dev environments, build pipelines and deployments always in sync
use branch-based deployments
easily switch cloud providers
create hybrid dev environments (local + remote)
experiment with new technologies using just a few commands and easily undo changes
rely on your architecture dependency graph as a single source of truth to plan and execute changes
Because Torque is cloud agnostic, and can be adopted one component at a time, getting started does not require a significant change to your current architecture, preferred tools or development practices.
Why Use Torque Cloud Framework?
Infrastructure as Code tools like Kubernetes and Terraform (and countless other services cloud providers now offer), are incredibly powerful for running cloud systems.
However, the level of complexity they introduce can be daunting for many teams, often creating technical debt accumulation, slowdowns, and roadmap disruptions for refactorings or rearchitecting.
Unlike static configurations, components are effectively self-aware and self-configurable, meaning your system can be built and deployed to any environment with any required functionality that your installed code libraries support.
You can even run any of your favorite tools (like Terraform), or deploy to your favorite platforms (like Kubernetes), through code libraries, so you gain their functional benefits without manually managing their configurations.
What is Torque Cloud Framework?
Built specifically for managing cloud system architectures, Torque is a framework that, when installed in your codebase, helps to implement development operations for your architecture, the way you design it.
Instead of making changes to every deployment by editing static configuration files, you use simple commands that modify your architecture dependency graph.
Through installed code libraries that describe the components of your system, Torque turns each new change into concrete configurations across every cloud deployment and development environment.
Whenever you need to, install different open-source code libraries, fine tune each implementation to suit your own needs, or write your own from scratch.
Torque's capabilities allow you to:
operate on a higher design level, and with just a few commands add new applications or services that also know how to interconnect
install open-source code libraries that implement all stages of each component from development to build pipeline to deployment
get a head start by installing code libraries, without losing the ability to customize any way you want
Why Terraform, Kubernetes, and Helm Don’t Actually Solve the Deployment Problem
Use Case: How to Add a New PostgreSQL Database With Just a Few Commands