Scalr is a commercial Terraform and OpenTofu automation platform billed per run. Pages here cover replacing it with self-hosted Terrakube or Atlantis.
Scalr against self-hosted Terrakube: environments and workspaces, remote backend compatibility in both, agents against executors, OPA policy, private registry, identity, and the trade between per-run billing and running the platform yourself.
For teams that use Scalr mostly for pull request plans and applies: Atlantis in your own infrastructure, its conftest policy checks and locking, and what it does not provide (state hosting, a module registry, a workspace UI).
Moving workspaces from Scalr to Terrakube: pulling state through the remote backend, recreating environments, variables and VCS links, porting OPA policies, replacing Scalr agents with Terrakube executors and switching each workspace's backend configuration.
Cost of ownership by component: Scalr's per-run billing, which counts dry runs as well as applies, its published volume examples and the runs it excludes, against Terrakube's free software, hosting, executors, migration and operations.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.