Earthly Technologies

• An actively maintained build tool with vendor-backed updates, security patches, and compatibility guarantees is required; the vendor ceased active maintenance effective July 16, 2025.
• A vendor-supported commercial remote runner product is required; the vendor discontinued Satellites and related commercial services as of that date.
• Enterprise environments require validated support for proxies and TLS interception and the toolchain cannot be validated to operate in those conditions.

• Centralized policy instrumentation intended to allow organization-level enforcement of standards and workflows through hooks in authoring, PR checks, and deployment gates.
• Multi-stage enforcement model that integrates policy evaluation across authoring and deployment stages.

Validation gap: public materials describe conceptual capabilities but provide limited technical details on policy language, testing and versioning workflows, auditability, and operational behavior at scale; these should be validated with vendor technical documentation and a pilot.

• Major review aggregators (Gartner Peer Insights, G2, TrustRadius, Capterra) did not surface attributable, verifiable Earthly listings in the captured sources.
• Community discussion platforms (Reddit, Hacker News) contain high-signal commentary about Earthfiles and the 2025 shutdown; these sources reflect individual user experiences and should be interpreted as anecdotal input.
• Vendor-published testimonials and performance claims are available but are marketing-controlled; methodology and baselines are generally not documented publicly.

Vendor pages present quantitative outcomes such as reported build time reductions and an aggregate build volume metric. These artifacts are vendor-published and do not include independently verified instrumentation or methodology in the publicly available materials reviewed here.

Critical evaluation:

• Vendor-presented case metrics likely reflect selected customers or specific configurations and should be validated through reference checks and pilot projects.
• Performance claims tied to commercial remote runners are less applicable to new buyers after the announced shutdown of those services.

• Company size: mid-market to enterprise organizations with large engineering organizations and many services and repositories.
• Industries: SaaS, fintech, marketplaces, and other organizations with compliance or reliability requirements and frequent code changes.
• Roles: Platform engineering, DevOps leadership, security and compliance engineering, and developer experience teams.
• Typical pain points: scattered standards and process documentation, PR review overhead related to automated code changes, inconsistent enforcement of deployment readiness, and fragmented CI definitions across repositories.

Earthly Technologies' current product offering includes Earthly Lunar, described by the vendor as a platform intended to implement engineering guardrails and to make engineering standards and developer workflows enforceable across the software development lifecycle through authoring hooks, pull request checks, and deployment gates. The vendor describes the product as converting standards and process documentation into enforceable controls.

Historically, Earthly developed Earthfiles (Earthfile): a container-focused build-definition approach with syntax and concepts similar to Dockerfile and Makefile, implemented via the open-source Earthly CLI and previously supported by commercial remote runners (Earthly Satellites / Earthly Cloud). Vendor documentation characterizes Earthly as a CI/CD-oriented framework intended to support repeatable builds across environments.

Important market context: the vendor publicly announced a shutdown of Earthly Satellite (the commercial remote runner offering) and an end to active maintenance of the Earthly open-source project effective in mid-2025. The Earthly CLI was stated to remain usable but without ongoing feature development or merged PRs. This change introduces material product and support risk for organizations considering Earthfile-based adoption in 2026.

• Earthly Lunar targets platform engineering, DevOps, and security/compliance stakeholders who are responsible for organization-wide standards enforcement across many repositories and services and who prefer centralized policy instrumentation rather than per-repository CI script changes.
• Earthfiles / Earthly CLI historically targeted engineering teams seeking reproducible, containerized build definitions and portability across CI providers, particularly in monorepo or multi-language stack contexts.