Softwr

Developer Tools · head to head

Depot vs Syft

Depot logo

Depot

Developer Tools

Cloud-based builds and CI runs 55x faster with less cost

From
Free
Free plan
Yes
Full reviewWebsite
Syft logo

Syft

Cybersecurity

Generates a software bill of materials from images, filesystems and archives

From
Free
Free plan
Yes
Full reviewWebsite

The short version

  • Each has a real cost: Depot developer plan minute limits may be insufficient for active development; Syft lockfile parsing can drop packages silently. An open issue filed in August 2026 reports the yarn v1 cataloguer returning 118 of 745 packages with no error raised, which means a complete bill of materials and an 84 percent incomplete one look identical to the caller.
  • They diverge on capability: Depot covers Depot CI, Syft covers Multi-format output.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Depot and Syft actually diverge.

Attributes where Depot and Syft differ
AttributeDepotSyft
Pricing modelUnknownOpen source, no licence fee
PlatformsCloud, GitHub, CLImacOS, Linux, Windows, Docker
CategoryDeveloper ToolsCybersecurity
Founded2022Unknown

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Depot

  • Depot CI
  • Container builds
  • GitHub Actions runners
  • Distributed caching
  • Build API
  • Depot Registry
  • Cross-platform builds
  • SSH debugging

Only in Syft

  • Multi-format output
  • Broad ecosystem coverage
  • Binary classifiers
  • In-toto attestations
  • Library and CLI
  • Pairs with Grype

What people use each for

The jobs each tool is most often brought in to do.

Depot

  • Accelerating Docker builds for container-based developmentnot Syft
  • Replacing GitHub Actions runners with faster infrastructurenot Syft
  • Distributing cache across Monorepo buildsnot Syft
  • Debugging failed CI builds interactively with SSHnot Syft

Syft

  • Producing a bill of materials for a customer or regulator that requires onenot Depot
  • Feeding an inventory into a vulnerability scanner rather than scanning images directlynot Depot
  • Recording what shipped in a build so a future disclosure can be answered quicklynot Depot
  • Public sector work where an SBOM is a contractual deliverablenot Depot

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Depot

  • Developer plan minute limits may be insufficient for active development
  • Startup plan at $200/mo is expensive for smaller teams
  • Business plan requires custom pricing consultation
  • macOS M2 runners not available on Developer plan

Syft

  • Lockfile parsing can drop packages silently. An open issue filed in August 2026 reports the yarn v1 cataloguer returning 118 of 745 packages with no error raised, which means a complete bill of materials and an 84 percent incomplete one look identical to the caller.
  • Fidelity varies sharply by ecosystem. Conan for C and C++, Haskell and Terraform get cataloguer support with no licence data, no dependency relationships and no file ownership, so a C and C++ shop gets the least from it.
  • Binary classification yields no licence or dependency metadata, and vendored or statically linked code is exactly where supply chain risk hides, so the blind spot and the risk overlap.
  • Incorrect CPE values and CPE collisions are recorded as open issues, and since Grype matches on CPE and PURL, an inventory error becomes a false negative in the security report downstream.
  • An inventory is not a risk assessment. Even a perfect bill of materials says a vulnerable version is present, never that the vulnerable function is called, and the triage burden lands entirely on the reader.

Pricing, plan by plan

Depot

Free
  • Developer$20/month
    • 1 user
    • 500 Docker build minutes per month
    • 2,000 Depot CI minutes per month
  • Startup$200/month
    • Unlimited users
    • 5,000 Docker build minutes per month
    • 20,000 Depot CI minutes per month
  • Business$undefined/custom
    • Custom pricing
    • Unlimited users
    • Custom monthly compute

Syft

Free
  • SyftFree
    • Apache-2.0
    • No usage limits
    • Community support
  • Anchore Enterprise$undefined/year
    • Policy enforcement and reporting
    • Federal and commercial tiers
    • Pricing not published, quoted on request

Which should you pick?

Choose Depot if

  • You need depot ci.
  • You want to start without paying.
  • You work on Cloud, GitHub, CLI.
  • You also want container builds.
Depot review

Choose Syft if

  • You need multi-format output.
  • You want to start without paying.
  • You work on macOS, Linux, Windows, Docker.
  • You also want broad ecosystem coverage.
Syft review

Questions people ask

Is Depot or Syft better?
Neither clearly leads. Depot starts at Free and Syft at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Depot or Syft?
Depot starts at Free and Syft at Free.
Does Depot or Syft run on more platforms?
Depot runs on Cloud, GitHub, CLI. Syft runs on macOS, Linux, Windows, Docker.
Can I use Depot for free?
Both have a free tier, so you can try either at no cost before committing.
What is Depot best used for?
Depot is most often used for accelerating docker builds for container-based development, replacing github actions runners with faster infrastructure, distributing cache across monorepo builds, debugging failed ci builds interactively with ssh. Of those, accelerating docker builds for container-based development and replacing github actions runners with faster infrastructure are not what Syft is typically brought in for.
What can Depot do that Syft cannot?
Depot covers Depot CI, Container builds, GitHub Actions runners, Distributed caching. Syft covers Multi-format output, Broad ecosystem coverage, Binary classifiers, In-toto attestations.

Answered from the vendors’ own pages

Depot: How much faster are Depot runners compared to GitHub Actions?

Depot runners offer 30% faster CPUs and 10x faster networking than standard GitHub-hosted runners, enabling builds to complete significantly faster.

Source
Syft: Does Syft find vulnerabilities?

No. It produces an inventory. Grype, from the same company, matches that inventory against vulnerability feeds. They are separate tools and the distinction is frequently lost.

Depot: What is included in the Developer plan?

Developer plan ($20/month) includes 500 Docker build minutes, 2,000 Depot CI minutes, 2,000 GitHub Actions minutes, 25 GB storage, unlimited concurrency, and community support.

Source
Syft: Does anything in the Anchore stack do reachability analysis?

No. Neither Syft, Grype nor the commercial Anchore platform performs call graph or reachability analysis, so none of them tells you whether a vulnerable code path is actually invoked.

Depot: Can I use Depot with my own AWS account?

Yes, Depot Managed allows deployment within customer AWS accounts. This is available to interested customers; contact sales for details.

Source
Syft: Is it a CNCF or OpenSSF project?

No. It is single-vendor open source owned by Anchore, with no foundation governance. That is a different licence risk profile from Sigstore.

Syft: What does Anchore Enterprise cost?

Not published. The pricing page is contact-sales only, with named but unpriced commercial and federal tiers.

Syft: How do I know my SBOM is complete?

You largely cannot, which is the honest answer. Silent partial parsing is a known open defect, so a bill of materials used for compliance should be spot-checked against a known dependency list.

Share

Related pages

More on Depot

More on Syft

Keep looking

Other head to heads