Scalr

Your GitHub Actions pipeline runs terraform apply. But do you know which Terraform version is running where, and which workspaces are pulling an outdated module? Scalr gives you that in one place: Metrics track plan/apply duration and queue wait times across every workspace. Reports show Terraform versions, modules, and providers in use, with drill-down to fix outliers.

Terraform Cloud's renewal price hike forced Primer to finally make a platform call they'd been putting off. The result: about 150 workspaces migrated to Scalr in a month, including a redesign. Since moving, Primer has run self-hosted runners and no longer worries about concurrency; queue wait times just aren't a concern anymore. Read how they did the migration, what was hardest, and what changed after: https://lnkd.in/dS9RJfeA

🎯 RBAC That Matches Your Org Chart Granular permissions down to the workspace and environment level. Platform teams get broad control. App teams get exactly what they need. That means devs and engineers can self-serve within their own scope, provision workspaces, run plans, and manage their variables without a platform team member in the loop for every request. Access control that scales with your org, not against it. #DevOps #PlatformEngineering #Terraform #OpenTofu

🔁 Scalr doesn't force one way of working. It plugs into your existing workflows. Use GitOps with plan-approve-apply through pull requests. Or apply-before-merge for teams that want changes live the moment a PR merges, no manual approval step. Or skip Git entirely and run through the Terraform or Tofu CLI directly. Multiple options, same platform. Switch per workspace, per team, per project, without migrating to a different tool to do it. Your process shouldn't have to bend to fit the tool. #Terraform #OpenTofu #GitOps #DevOps

⚡ Need more concurrency? Scalr increases it free of charge, no upsell, no tier upgrade. You can also scale it yourself. Every self-hosted agent you deploy adds 5 concurrent runs on top of what Scalr.io runners already allocate, and there's no limit on how many agents you can run. More agents, more throughput, on your terms. #OpenTofu #Terraform #PlatformEngineering #DevOps

🔍 Ask your AI assistant which of your workspaces have drifted. No dashboards, no manual checks. Scalr's MCP server now includes a Drift Detection Reports tool: query drifted infrastructure right from your AI assistant or automation workflow. See more in the comments

🔌 Two Scalr features that work well together: Run Triggers — when Workspace A applies, Workspace B starts automatically. No glue or manual handoff. Remote State Consumers — workspaces explicitly declare which other workspaces can read their outputs. Workspace B pulls VPC IDs, subnet CIDRs, and security group IDs directly from Workspace A's state using terraform_remote_state. No hardcoded values, no copy-paste. One applies, the next starts, and the outputs are already there. See the docs in the comments.

Feature Spotlight: Storage Profiles Most IaC platforms store your data on their own infrastructure. With Storage Profiles in Scalr, you configure your own cloud storage (S3, Azure Blob, Google Cloud Storage) and keep full ownership of: - Terraform and OpenTofu state files - Plan and apply logs - Code artifacts Everything lands in your environment, under your control.

‼️ Scalr now supports Bring Your Own Key (BYOK) encryption. If your security or compliance team requires customer-managed keys, you no longer have to compromise. Bring your own KMS and take full control over how your sensitive Terraform and OpenTofu metadata is encrypted at rest. Your infrastructure automation platform should work with your security posture, not against it. BYOK is available now. Link in comments.

🚨 New feature alert: OCI Sourced Modules 🚨 OpenTofu's oci:// module source scheme lets you store and version Terraform modules as OCI artifacts alongside your container images. The new OCI registry integration in Scalr handles the credentials part for you. You store your registry credentials once in Scalr, and every plan and apply run can authenticate with your private registry automatically. You don't have to set environment variables, hardcode secrets, or configure anything per workspace.