January 2026 Summaries

Engineering organizations face challenges in enforcing standards within their rapidly evolving and complex systems, as traditional methods like scorecards, templates, and centralized CI/CD infrastructure often fall short due to their inability to adapt to varied workflows and unique team needs. These methods assume a uniformity that doesn't exist, as teams differ in architecture and constraints, leading to repeated failures and high compliance costs. A guardrails engine offers a solution by continuously observing software delivery activities and evaluating them against organizational standards in real-time, based on context, ownership, environment, and risk. This approach leverages signals from existing systems to create a common view of software processes, allowing policies to be applied flexibly and evolve with changing systems without requiring constant reconfiguration. This ensures that standards are enforced effectively at scale, providing timely feedback directly within development workflows, such as pull requests, and supporting a wide range of tools and CI/CD systems.

In an effort to understand the evolving challenges of platform engineering, Earthly conducted extensive interviews with industry professionals, revealing that the primary issue is not CI/CD speed but the "explosion of diversity" in tech stacks at scale. This diversity, driven by the freedom enabled by containers and microservices, leads to unique configurations for each development team, creating chaos that is challenging to govern. Common strategies to manage this chaos, such as CI/CD templates, manual checklists, and scorecards, each have limitations and fail to fully address the issue. In response, Earthly developed Earthly Lunar, a platform designed to provide global visibility and enforce engineering standards across diverse and complex CI/CD pipelines without impeding developer velocity. Lunar allows real-time monitoring of engineering practices, enabling compliance and security measures to be applied consistently, thus addressing the broader complexity of the software development lifecycle beyond production environments.