We detected 622 customers using Scalr, 4 companies that churned or ended their trial, and 4 customers with estimated renewals in the next 3 months. The most common industry is Software Development (28%) and the most common company size is 51-200 employees (26%). Our methodology involves discovering URLs with known URL patterns through web crawling, certificate transparency logs, or modifications to subprocessor lists.
About Scalr
Scalr provides a remote operations backend for Terraform and OpenTofu that executes runs and stores state centrally, enabling team collaboration through native CLI workflows, GitOps automation, or no-code provisioning while offering policy enforcement, cost optimization, and self-service capabilities for developers and platform teams.
📊 Who in an organization decides to buy or use Scalr?
Source: Analysis of 100 job postings that mention Scalr
Job titles that mention Scalr
i
Based on an analysis of job titles from postings that mention Scalr.
Job Title
Share
DevOps Engineer/SRE
42%
Cloud Engineer
26%
Backend Engineer
8%
Solutions Architect
5%
I noticed that 97% of roles mentioning Scalr are individual contributors, with DevOps Engineers and SREs making up 42% of all positions. The 3% leadership roles are Associate Directors and Directors focused on Cloud Engineering and Infrastructure Management Platforms. These leaders are responsible for purchasing decisions around automation frameworks and infrastructure as code tools. They're prioritizing implementation of automation frameworks, observability platforms, and configuration management to enable their teams to scale.
The day-to-day users are predominantly DevOps engineers, SREs, and cloud engineers who leverage Scalr for infrastructure provisioning and Terraform management. These practitioners are deploying multi-cluster Kubernetes environments, managing CI/CD pipelines, and automating infrastructure deployment across AWS and Azure. One posting specifically mentioned working with product management to drive automation product adoption including Ansible and Scalr inside the organization. The hands-on work involves creating Infrastructure as Code templates, managing cloud resources, and ensuring security compliance across deployments.
The pain points center on scaling cloud operations and enabling developer self-service. Organizations want to provide centralized management and decentralized deployment of infrastructure with full visibility and control. They're seeking automated solutions for cloud and application team requirements and ways to increase developer velocity while maintaining governance. Companies are focused on delivering a platform that allows organizations to use Terraform and OpenTofu at scale, which directly reflects Scalr's core value proposition of enabling DevOps teams to automate cloud management efficiently.
🔧 What other technologies do Scalr customers also use?
Source: Analysis of tech stacks from 622 companies that use Scalr
Commonly Paired Technologies
i
Shows how much more likely Scalr customers are to use each tool compared to the general population. For example, 287x means customers are 287 times more likely to use that tool.
I noticed that Scalr users are infrastructure-focused companies operating sophisticated cloud environments at scale. The extremely high correlation with Spacelift, another infrastructure as code platform, tells me these companies are deeply invested in managing complex Terraform and cloud deployments. They're likely mid-market to enterprise B2B companies running distributed systems that need governance, compliance, and centralized control over their infrastructure.
The pairing with Docker Hub and Pulumi reveals a company committed to modern infrastructure patterns. These aren't just using one approach but multiple infrastructure as code tools, suggesting they have diverse teams or complex requirements that demand flexibility. The SonarQube Cloud correlation is particularly telling because it shows they're applying software engineering rigor to their infrastructure code, treating it with the same quality standards as application code. Meanwhile, the Pagerduty connection indicates 24/7 operations where uptime matters critically, likely serving customers who depend on their services around the clock.
The full picture suggests these are engineering-led organizations in growth or mature stages. They've moved past startup chaos into standardized, repeatable processes. The OneLogin presence points to companies managing significant headcount with security and compliance requirements, probably 100-plus employees dealing with SOC 2 or similar certifications. These aren't product-led growth companies experimenting with free tiers. They're sales-led or enterprise-focused businesses where reliability, security, and governance justify significant infrastructure investment.
👥 What types of companies is most likely to use Scalr?
Source: Analysis of Linkedin bios of 622 companies that use Scalr
Company Characteristics
i
Shows how much more likely Scalr customers are to have each trait compared to all companies. For example, 2.0x means customers are twice as likely to have that characteristic.
Trait
Likelihood
Funding Stage: Seed
21.4x
Industry: Software Development
9.4x
Industry: IT Services and IT Consulting
6.0x
Industry: Technology, Information and Internet
5.0x
Country: GB
2.1x
Company Size: 51-200
1.7x
I noticed that Scalr's customers span an incredibly wide range, but they share a common thread: they're building or operating technology-intensive businesses that require sophisticated infrastructure. These aren't just software companies. I see financial services platforms processing billions in transactions (Capital.com, Paysend), healthcare organizations managing sensitive patient data (AstraZeneca, Press Ganey), and even traditional industries undergoing digital transformation (Aurubis Beerse in mining, Viega in construction). What unites them is that technology is core to their operations, not peripheral.
The company stages are all over the map, which is telling. I see seed-stage startups with under 20 employees (Bench, Partsimony), Series A and B companies scaling rapidly (Encord, Genesis Molecular AI), and massive enterprises with 10,000+ employees (AstraZeneca, Essity, Airbnb). The majority, though, fall into that critical growth phase: 50-500 employees, often with recent funding rounds, expanding their infrastructure needs rapidly.
Alternatives and Competitors to Scalr
Explore vendors that are alternatives in this category