Recommended Free Tools
Quali announced on January 19, 2021, that it had raised $54 million in a Series C round co-led by Greenfield Partners and Jerusalem Venture Partners (JVP). The company said it would use the capital to expand its customer base and partnerships, accelerate CloudShell development, strengthen its market position and hire more staff. Contemporary coverage described the financing as bringing Quali’s total funding to roughly $100 million, although a later 451 Research profile reported $102.9 million.
This was a historical financing announcement, not a new 2026 funding event. Its significance was Quali’s attempt to make complete development, testing and demonstration environments self-service across public cloud, private infrastructure, hybrid systems and physical equipment.
What Quali raised and who invested
The official announcement said Quali raised $54 million in new funding on January 19, 2021. Greenfield Partners and Jerusalem Venture Partners co-led the round. Calcalist reported that Kreos Capital and Hamilton Lane also participated, although Quali’s release did not list every investor.
Calcalist and later industry coverage identified the financing as a Series C. VentureBeat said the round lifted Quali’s cumulative funding to nearly $100 million; a later 451 Research profile put the total at $102.9 million. “Roughly $100 million” is therefore the safest description without implying that the sources agree on one exact total.
#1 Best Overall
Quali said the proceeds would support:
- Expansion of its enterprise customer base
- New partnerships and broader market reach
- Further CloudShell product development
- Brand and market-position investment
- Hiring and team growth
Quali’s funding announcement contains the company’s stated use of proceeds.
The infrastructure problem Quali was addressing
Quali was not merely selling another cloud dashboard. Its target problem was the repeated assembly and operation of complete environments: networks, virtual machines, storage, applications, services, connectivity and sometimes physical laboratory equipment.
In a large enterprise, a developer, tester, sales engineer or customer-support team may need an environment that resembles production but is temporary. Building it manually can require tickets, specialist intervention, cloud-account permissions and coordination across several infrastructure teams. Teardown is another challenge: abandoned resources continue generating bills, while inconsistent cleanup can create security and compliance exposure.
Quali’s proposition was to model these combinations as reusable blueprints, publish approved choices through a catalog and let authorized users request environments through governed workflows. That approach aimed to reduce repetitive provisioning work while preserving controls over access, configuration and cost.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #2
How CloudShell worked
CloudShell was the flagship product discussed in the 2021 financing coverage. The following workflow summarizes its reported capabilities; it is a conceptual explanation, not an independent performance test.
- Model the environment. Teams assembled infrastructure and application components into reusable blueprints. CloudShell supported physical and virtual resources, rather than limiting a blueprint to one cloud provider.
- Store and manage blueprints. Reusable definitions could be maintained with source-control systems such as GitHub and Bitbucket.
- Offer governed self-service. Authorized users selected an approved environment instead of requesting every component manually from an infrastructure specialist.
- Provision the stack. CloudShell automated setup across public cloud, private cloud, hybrid and on-premises infrastructure, according to the selected blueprint and policies.
- Track ownership and spending. Reported capabilities included role-based access, separation of duties and cloud-cost visibility or attribution.
- Destroy temporary resources. Automated teardown was intended to reduce orphaned environments and make the full environment lifecycle repeatable.
This placed CloudShell above the level of an individual virtual machine or storage volume: the unit of automation was a usable environment containing the resources and software a team needed.
Who was the intended customer?
Quali’s target market consisted of organizations where infrastructure was heterogeneous, environments were created frequently and specialist teams had become a bottleneck. Relevant groups included:
- DevOps and platform-engineering teams supporting many developers
- Quality-assurance and test organizations that needed repeatable environments
- Sales engineers building demonstrations and proofs of concept
- Telecommunications and network laboratories
- Technology manufacturers and data-center operators
- Financial-services companies with strict governance requirements
- Software vendors operating across multiple clouds or hybrid infrastructure
VentureBeat cited Cisco, Microsoft, Dell and Verizon among Quali’s customers, while Calcalist also mentioned Bank of America. Those references were reported customer claims, not independent customer-outcome studies.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesRank #3
Calcalist reported approximately 150 large customers and about 130 employees in January 2021. Quali planned to approach 200 employees by the end of that year. Those figures describe the company at the time of the announcement and should not be read as current operating statistics.
Where CloudShell fit among adjacent tools
| Category | Primary job | How CloudShell differed |
|---|---|---|
| Infrastructure-as-code tools | Declare and provision infrastructure | Added an environment-level catalog, self-service experience and lifecycle workflows around underlying automation |
| Cloud-provider consoles and catalogs | Manage resources inside one provider ecosystem | Targeted combinations spanning public cloud, private infrastructure, on-premises systems and physical equipment |
| CI/CD platforms | Build, test and release software | Supplied the environments and infrastructure those pipelines required |
| FinOps products | Allocate, analyze and optimize cloud spending | Connected cost visibility to provisioning, ownership and teardown rather than focusing only on billing analytics |
| Lab-management systems | Reserve and operate physical test equipment | Extended environment orchestration across physical and cloud resources |
| Internal developer portals | Present service catalogs and workflows | Provided prebuilt infrastructure-environment orchestration and governance that could sit behind a portal |
A later 451 Research assessment discussed first-party cloud services and vendors including VMware, Red Hat, IBM, SUSE, HPE, CoreStack, Cloudify, HashiCorp and Morpheus Data as relevant competitive or adjacent offerings. That later market context should not be mistaken for an investor statement made during the 2021 round.
Why the financing mattered in 2021
The investment arrived as enterprises expanded cloud use but still struggled with scarce cloud expertise, inconsistent configurations and slow access to development and test environments. Infrastructure-as-code had made individual resources more repeatable, yet many organizations still lacked a convenient way to package an entire, policy-compliant environment for non-specialist users.
Quali’s investment thesis, as reflected in its positioning, was that enterprises needed self-service without handing every developer unrestricted permissions. A catalog of approved blueprints could standardize deployments, while role-based controls, cost attribution and expiration policies could address governance and spending.
That did not mean Quali invented cloud automation or replaced Terraform, cloud-provider services, CI/CD, FinOps or internal portals. Its claimed distinction was abstracting heterogeneous components into complete environments and managing the request-to-teardown lifecycle.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Risks and limitations of the platform approach
Blueprint maintenance
Reusable templates only remain useful when they track security requirements, provider APIs and internal standards. A platform team can reduce end-user effort while taking on substantial maintenance work behind the scenes.
Permission and secrets design
Self-service still requires careful role-based access control, secrets handling, approvals, account boundaries and audit logging. A poorly designed catalog can make unsafe infrastructure easier to create.
Cost control is not automatic
Provisioning automation may increase spending if temporary environments do not expire, if large resources are selected by default or if production workloads are counted in the same billing model. Cost visibility helps only when teams act on it.
Best Value
Overlap with existing platforms
Organizations may already operate a Terraform platform, cloud-native service catalog, internal developer portal, CI/CD system or FinOps product. The business case depends on reducing duplicated work rather than adding another interface.
Integration and portability
Buyers should examine supported clouds, virtualization systems, networks, physical equipment and deployment models. They should also understand how easily blueprints, policies and automation logic can be exported if the platform is replaced.
How Quali’s products are positioned now
Quali’s current portfolio separates CloudShell from Torque. The 2021 financing story centered on CloudShell; current product pages position Torque as a broader infrastructure control plane for discovery, governance, deployment, cost management, drift and day-two operations. Current Torque materials say it can use assets such as Terraform, AWS CloudFormation, Helm, Kubernetes, CloudShell and Ansible.
Those current capabilities should not be backdated to January 2021. Likewise, CloudShell’s current description of no-code and low-code infrastructure building blocks explains product continuity but does not prove that every present feature existed at the time of the funding announcement.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallQuali’s current pages also advertise a Free tier, a Pro price of $19 per provisioned environment per month and Enterprise pricing by quote, with pricing observed in August 2026. The metric is provisioned environments, not a universal per-user or per-resource price, and the company’s pricing can change. CloudShell’s product page promotes a free 30-day trial and demo rather than a generally applicable public price.
See Quali Torque, Quali CloudShell and Quali’s pricing page for current product information.
Questions enterprise buyers should ask
- Is pricing based on provisioned environments, users, resources, concurrency or committed capacity?
- Does an environment include continuously running production workloads?
- Can existing Terraform or CloudFormation assets be imported without extensive rewriting?
- How are secrets stored and delivered to provisioned systems?
- What happens when only part of a deployment succeeds?
- Does the platform detect and remediate drift, or only report it?
- How granular are approval, security, cost and runtime policies?
- What happens if the control plane is unavailable?
- Can customers export definitions and automation logic?
- Do data residency, air-gapped operation and private-deployment requirements match the available model?
Bottom line on the $54 million round
Quali’s $54 million Series C gave it capital to scale an enterprise-infrastructure abstraction layer at a time when companies wanted cloud speed without surrendering governance. CloudShell’s core idea was to turn complex, mixed infrastructure into repeatable environments that authorized teams could provision and retire through self-service workflows. The round was important as a snapshot of that market shift, but it should be read as January 2021 funding news—not as evidence of a new financing or independently verified business outcomes in 2026.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
