Echo

• Docker could bundle its hardened image line with Docker Container Registry. That would make Echo's core artifact easier to replace.
• Chainguard sells hardened containerized images into the same market, and SiliconANGLE names it as the competitor in this market, so a head-to-head on catalog coverage and price could arrive before Echo's automation economics compound.
• Echo markets adoption as a single line change, and that same line points back at upstream artifacts or at a rival, which caps switching cost and pricing power.
• A malicious component shipped through an Echo artifact would undercut the promise Echo sells on. A missed patch commitment on a headline CVE would do the same, and Echo's SLA excludes some CVEs whose fix is not isolated or compatibility-preserving.
• Minimus raised $51 million in this category and then wound down, telling customers that the business and investment climate left it unable to continue, which is direct evidence that funded execution in this market does not guarantee a sustainable business.
• Elhadad told Information Security Media Group that Echo will continue developing both platforms initially and that maintaining two will need additional engineering resources, so absorbing the acquired lineage competes for the same engineers who maintain the catalog.

Echo sells the removal of inherited vulnerabilities from the software layer its buyers did not write. Its case studies describe the work that replaces: Varonis found that fixing a single container took two to three weeks of dependency tracing, cryptography validation and retesting, and Port found that a single customer-reported CVE cost one to three developer days, with fixes Port could not reuse across images.

The buying trigger the record documents most clearly is somebody else's scanner. Port's study states that large enterprises routinely scanned its images with their own security tools before adoption, and that a high-severity finding stalled everything. Echo sells directly to that moment, promising that customers can scan clean with their own tools without waivers or overrides.

Regulation supplies a second, dated reason to act. The European Commission records that the Cyber Resilience Act entered into force on 10 December 2024, that its reporting obligations apply from 11 September 2026, and that it requires manufacturers to handle vulnerabilities across a product's lifecycle. The scale of the underlying problem is less independently established: the freshest third-party figure in the record, 87 percent of audited commercial codebases carrying at least one open-source vulnerability, is a Black Duck study cited by SiliconANGLE. [s9, s10, s26, s28, s18]

Echo ships prebuilt artifacts, and each family keeps the workflow the customer already has. Container images are adopted by swapping the upstream image in a Dockerfile for Echo's alternative. Libraries keep the same names, versions and installation methods, with the customer pointing at Echo's repository instead. OS packages work with standard package managers and can be mirrored through internal JFrog, Nexus and custom repositories. Hardened virtual machines are offered for early access.

Supply-chain provenance ships with the artifacts. Echo states that images are built on its controlled build infrastructure at SLSA Level 3, signed and attested, and delivered with SBOM, provenance and VEX metadata, in both SPDX and CycloneDX. For federal work, each FIPS image uses a CMVP-validated cryptographic module and images are pre-hardened against DISA STIG.

Maintenance is what the customer is actually buying, and two documents state it differently. The product pages promise triage within 24 hours and fixes within seven days for critical and high CVEs. The Images and Libraries SLA commits to commercially reasonable efforts within seven business days, subject to eligibility criteria that require an isolated and compatibility-preserving fix. FIPS-validated components follow the validated module's update stream regardless of those timelines.

Behind the catalog is an automation pipeline. SecurityWeek reports that when a new flaw appears, agents research it, identify the affected images among more than 600, seek or build fixes, run compatibility tests and open pull requests. A newer line applies frontier models to find vulnerabilities before a public identifier exists, with Echo developing and backporting patches and coordinating disclosure as a CNA. [s4, s5, s6, s12, s13, s14, s29, s34, s22]

SiliconANGLE names Chainguard as the competitor in this market, describing it as supplying hardened containerized images and repository scanning. Echo's own account of the category is more pointed: its acquisition post argues that a market of several vendors is consolidating around two players, Echo and Chainguard.

Echo points to the August 2026 Minimus purchase as the evidence, and the same deal complicates the claim. Minimus raised $51 million, employed 73 people, and told customers it could not continue in the current business and investment climate. Echo bought the assets. Elhadad told Information Security Media Group that about 90 percent of open-source images use foundations similar to Echo's, while about 10 percent use the Minimus approach. Echo plans to use Minimus to serve the remaining 10 percent.

Registry incumbents are the other side of the contest. Echo publishes migration guidance for teams leaving Docker Hardened Images and Bitnami Helm charts, which places Docker as both a distribution channel Echo mirrors into and a vendor selling an adjacent hardened line. Echo's counter is coverage and adoption rather than exclusivity, and Elhadad's stated argument is that a product an organization can fully roll out protects better than one promising the same vulnerability outcome. [s18, s13, s31, s19, s21]

Echo runs a sales-assisted enterprise motion. Pricing is quoted rather than listed, with two published models. Customers can pay per artifact or for the whole catalog based on engineering-organization size. Echo defines an engineer as anyone who committed to a private repository in the last 180 days. Every product page routes to a demo or a product expert.

Distribution rides infrastructure the customer already operates. Artifacts are mirrored to ECR, Azure Container Registry, Google Artifact Registry, JFrog, Docker, GitHub Packages, Nexus, Harbor and Red Hat Quay, and AWS and Azure marketplace listings are marked available for consumption. Echo says it supports AWS, Azure and GCP marketplaces.

The named-customer record is real. The trust center lists Aqua Security, Varonis, UiPath, EDB, Vectra AI and Webflow as organizations that reviewed and trust Echo, the April 2026 announcement named Varonis, EDB and UiPath, and Calcalist independently reported that Echo took over Minimus customer operations covering Blackstone, RBS and SentinelOne. Calcalist reported that Echo was deployed at dozens of organizations.

Demand generation runs through practitioner content. Echo's blog published eight posts between 5 and 21 September 2026 on STIG compliance, EPSS against CVSS, distroless alternatives and migration guides. [s3, s7, s11, s21, s32, s26, s8, s31]

Echo is the founders' second software supply-chain company. Calcalist reports that Eilon Elhadad and Eylam Milner sold their previous startup to Aqua Security for $100 million, and SecurityWeek identifies them as the founders of Aqua Security-acquired Argon. Calcalist's launch coverage records Unit 8200 and Ofek backgrounds for both, with Elhadad as CEO and Milner as CTO.

The pace matches the pattern. The company was founded in early 2025, closed its Series A four months after its seed, and by August 2026 was buying a competitor's assets in cash.

The about page lists offices in Tel Aviv, New York and California. Absorbing a second artifact lineage is the nearest test: Elhadad told Information Security Media Group that Echo will continue developing both platforms initially and that maintaining two will need additional engineering. [s21, s22, s24, s2, s19]

Echo's compliance posture is built for procurement review. Its SafeBase-hosted trust center lists SOC 2 Type 2, ISO/IEC 27001:2022 and FIPS 140-3, with ISO, SOC 2 and penetration test reports available on request. The FedRAMP material goes further than certification, offering continuous-monitoring and POA&M-ready reporting on fixed and unresolved vulnerabilities.

The vendor also puts its own vulnerability handling on the record. Echo operates as a CVE Numbering Authority and publishes a 90-day responsible disclosure timeline. It may escalate at day 45 and issue an advisory at day 60 if a maintainer does not respond or declines to collaborate. A public tracker lists the affected package, severity and first-detected date.

The concentration risk is inherent to the model. Customers source their foundational software from one vendor's build pipeline, so a compromise of that pipeline would put bad code into artifacts customers then pull. The published mitigations are the SLSA Level 3 pipeline with signed and attested artifacts. The published SLA promises commercially reasonable efforts, sets seven business days for critical and high severity findings and ten for medium and low, excludes CVEs whose fix is not isolated or does not preserve compatibility, and follows the validated module's own update stream for FIPS-validated components. [s11, s12, s17, s29, s35]

Add analyzed competitors to compare them side by side with Echo.

Echo targets enterprises whose engineering organizations inherit vulnerability debt from open-source infrastructure. Its trust center names Aqua Security, Varonis, UiPath, EDB, Vectra AI and Webflow as organizations that reviewed and trust it, and Calcalist reported that Echo took over Minimus customer operations covering Blackstone, RBS and SentinelOne, which puts regulated financial institutions in the buyer set alongside software vendors.

The documented buying triggers differ by account rather than across the group. Port's case study describes enterprise customers scanning its images before adoption and stalling on a high-severity finding. Varonis's describes a FedRAMP program where every container in scope had to be remediated, FIPS-validated and kept clean. The other named organizations appear as customers without a stated trigger.

Two personas speak in the record. Security leaders supply the audit and risk outcomes, with UiPath's CISO quoted on eliminated CVE exposure in Echo's own announcement, while engineering leaders describe reclaimed developer time. Pricing reflects the same split, offering either per-artifact consumption or a catalog price set by the number of engineers who committed to a private repository in the last 180 days, both quoted rather than listed.

Echo's product claim is subtraction, because it removes the vulnerabilities other vendors help customers find before a customer pulls the artifact. Each family preserves the workflow it displaces. Container images are swapped in at the Dockerfile. Libraries keep their names, versions and installation methods while the customer points at Echo's repository. OS packages work with standard package managers and mirror through internal repositories.

The automation argument is about operating cost. SecurityWeek reports that agents research each new flaw, identify the affected images among more than 600, seek or build fixes, run compatibility tests and open pull requests. Echo describes the same pipeline as a software factory whose proprietary agents help its researchers investigate vulnerabilities and validate patches, and presents it as an alternative to traditional manual maintenance rather than as a claim about how rivals staff their own catalogs.

A newer line points the models outward. Echo says it runs frontier models across the open-source software customers depend on, validates findings, develops and backports patches, and coordinates disclosure upstream. Its disclosure page states that Echo is a CVE Numbering Authority operating a 90-day timeline, and names CVE-2026-7482, a critical Ollama memory vulnerability, as one it assigned. The National Vulnerability Database records that identifier as an analyzed heap out-of-bounds read with a base score of 8.8.

Durability of the advantage remains the open question. The acquisition adds inputs Echo did not hold before: Echo says Minimus technology, integrations, research and data broaden distro support and strengthen the agents behind the factory, and SiliconANGLE reports the same in its own words.

Echo sells into enterprises through a quoted, sales-assisted motion. Every product page routes to a demo or a product expert, and pricing is published as packaging logic rather than as a number: per artifact consumed, or the whole catalog priced by engineering-organization size.

Distribution rides infrastructure customers already run. Echo lists ECR, Azure Container Registry, Google Artifact Registry, JFrog, Docker, GitHub Packages, Nexus, Harbor and Red Hat Quay as fully supported registries, and AWS and Azure marketplace listings as available for consumption. It also integrates with the scanners that would otherwise raise findings, which is what makes the clean-scan promise legible to a customer's own tools. The reviewed integrations page shows broad compatibility rather than exclusive distribution, so nothing in it prevents a rival from mirroring to the same places.

Demand generation runs through practitioner content and named references. The blog published eight posts between 5 and 21 September 2026, including migration guides for teams leaving Docker Hardened Images, Bitnami Helm charts and public base images. Traction evidence is strong for the company's age and shallow on depth. Echo publishes no revenue or retention figure on its pricing, customer or trust pages, and the nearest customer-scale statement in the coverage is Calcalist's July 2025 line that the product was deployed at dozens of organizations.

Echo publishes its packaging logic and not its prices. The pricing page offers two models: pay per artifact, quoted on the number consumed, or access to every secure artifact priced by the size of the engineering organization. Buyers get a number by requesting a custom quote, and a startup plan exists on request.

Both units track how a buyer sizes its own exposure. Artifacts consumed map to the dependency surface being secured, and engineering headcount, defined as anyone who committed to a private repository within the last 180 days, scales with how much software the customer builds. Switching between the two models is possible through an Echo representative, within what the contract permits.

What the price buys is set by the SLA rather than the marketing pages. The published Images and Libraries SLA commits to commercially reasonable efforts, seven business days for critical and high severity findings and ten for medium and low, with eligibility conditions that exclude CVEs whose fix is not isolated or would break backward compatibility, and it follows the validated module's own update stream for FIPS-validated components. Echo argues the trade in its own terms on the FedRAMP page, which prices the do-it-yourself path at $127,000 to $255,000 per image and marks the equivalent Echo work as included.

Delivery is registry-native and asks for almost no deployment work. Customers repoint a Dockerfile line, a package source or a library repository at Echo's artifacts in the registries they already use, and let their existing scanners verify the result. Port's study reports that its integrations needed testing against the new builds and no code changes.

Operations carry the product's substance. Echo rebuilds artifacts continuously as fixes land, backports fixes to the versions customers already run, keeps workloads on those versions without forced migrations, and reports both fixed and unresolved vulnerabilities. A public CVE tracker lists affected package, severity and first-detected date.

A compatibility regression in a rebuilt artifact would surface inside a customer's production environment, which is what the compatibility testing exists to prevent. The SLA states the remaining exposure plainly: remediation depends on Echo's scanners detecting the CVE, on an isolated fix, and on an available upstream release, and where no official fix exists Echo may apply temporary mitigations subject to feasibility.

Echo's certifications are built for the procurement reviews its buyers run. The SafeBase-hosted trust center lists SOC 2 Type 2, ISO/IEC 27001:2022 and FIPS 140-3, with ISO, SOC 2 and penetration test reports available on request. The FedRAMP material adds evidence generation: CMVP-validated cryptographic modules, DISA STIG hardening, SBOMs in SPDX and CycloneDX, and continuous-monitoring and POA&M-ready reporting.

Echo also puts its own vulnerability handling on the record. It operates as a CVE Numbering Authority, publishes a 90-day responsible disclosure timeline under which it may escalate at day 45 and issue an advisory at day 60 if a maintainer does not respond or declines to collaborate, accepts encrypted reports, and maintains a public CVE tracker.

The structural trust question is concentration. Customers source their foundational software from one vendor's build pipeline, so a compromise of that pipeline would put bad code into artifacts customers then pull. The published mitigation is a SLSA Level 3 pipeline with signed and attested artifacts. Reviewed pages stop short of a published threat model or a third-party audit of the pipeline itself, and the SLA commits Echo to commercially reasonable effort.

Echo plugs into the container ecosystem on both sides rather than running a platform surface of its own. Inbound, artifacts are mirrored to the registries customers pull from. Outbound, integrations make scanners recognize what Echo ships, which is what turns a clean build into a clean report in the customer's own tooling.

The stated ambition is to become the layer others depend on. The about page frames Echo as creating the trusted source for agentic-ready software, and the acquisition post says the combination broadens Echo into a distro-agnostic secure-by-default platform. SiliconANGLE reports the same direction in its own words, writing that the Minimus purchase lets Echo expand the number of Linux distributions it supports. Cloud Native Now describes the resulting portfolio as spanning container images, virtual machines, libraries, serverless functions, OS packages and Helm charts.

Ecosystem dependencies cut both ways. Echo depends on the upstream projects it repackages and on registry and scanner cooperation it does not own, and Docker is at once a registry Echo mirrors into and the vendor of a hardened image line Echo writes migration guides against.

The founding team has built this company shape before. Calcalist reports that Eilon Elhadad and Eylam Milner sold their previous startup to Aqua Security for $100 million, and SecurityWeek identifies them as the founders of Aqua Security-acquired Argon. Both came through Unit 8200 and the Ofek technology unit, and they founded Echo in early 2025.

The repeat shows in pace. Echo closed its Series A four months after its seed for $50 million in total, and inside its second year it bought a competitor's assets for cash. The about page lists offices in Tel Aviv, New York and California and states no current headcount, so the company's size today is not readable from the reviewed pages or the fresh coverage.

Integrating and maintaining both platforms will require additional engineering capacity. Elhadad told Information Security Media Group that Echo is buying all of the assets, meaning the IP, the technology, the customers and the data, that Echo will keep developing both platforms initially, and that maintaining two will need additional engineering resources.