Softwr

Cybersecurity · head to head

Ory vs Syft

Ory logo

Ory

Cybersecurity

Open-source identity, authentication, and permissions infrastructure

From
Free
Rated
-
Full reviewWebsite
Syft logo

Syft

Cybersecurity

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

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Ory production and Growth plans are billed annually ($770/year and $9,350/year), which is a larger upfront commitment than monthly-only competitors.; 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: Ory covers Authentication APIs, Syft covers Multi-format output.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Ory and Syft actually diverge.

Attributes where Ory and Syft differ
AttributeOrySyft
Pricing modelusage-basedOpen source, no licence fee
Platformsweb, apimacOS, Linux, Windows, Docker

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

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 Ory

  • Authentication APIs
  • Permissions engine
  • Machine-to-machine tokens
  • B2B organizations
  • SAML SSO
  • Multi-region deployments

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.

Ory

  • Adding self-hosted or cloud identity to a new productnot Syft
  • Implementing fine-grained permission checksnot Syft
  • Supporting B2B organizations and multi-tenancynot Syft
  • Building machine-to-machine authentication for microservicesnot Syft

Syft

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

Where each one falls short

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

Ory

  • Production and Growth plans are billed annually ($770/year and $9,350/year), which is a larger upfront commitment than monthly-only competitors.
  • SAML SSO and multi-region deployments are reserved for the custom-priced Enterprise tier.
  • Usage-based pricing across aDAU, M2M tokens, and permission checks makes cost estimation more complex than flat per-MAU billing.

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

Ory

Free
  • DeveloperFree
    • Community support
    • No production environments
  • Production$64/month
    • $21 monthly credit included
    • 1 production environment
    • 3 staging environments
  • Growth$779/month
    • $255 monthly credit included
    • 2 production environments
    • B2B organizations (max 3)

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 Ory if

  • You need authentication apis.
  • You want to start without paying.
  • You work on web, api.
  • You also want permissions engine.
Ory 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 Ory or Syft better?
Neither clearly leads. Ory 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, Ory or Syft?
Ory starts at Free and Syft at Free.
Does Ory or Syft run on more platforms?
Ory runs on web, api. Syft runs on macOS, Linux, Windows, Docker.
Can I use Ory for free?
Both have a free tier, so you can try either at no cost before committing.
What is Ory best used for?
Ory is most often used for adding self-hosted or cloud identity to a new product, implementing fine-grained permission checks, supporting b2b organizations and multi-tenancy, building machine-to-machine authentication for microservices. Of those, adding self-hosted or cloud identity to a new product and implementing fine-grained permission checks are not what Syft is typically brought in for.
What can Ory do that Syft cannot?
Ory covers Authentication APIs, Permissions engine, Machine-to-machine tokens, B2B organizations. Syft covers Multi-format output, Broad ecosystem coverage, Binary classifiers, In-toto attestations.

Answered from the vendors’ own pages

Ory: What does Ory cost?

Ory has a free Developer tier, a Production plan at $770/year including a $21 monthly credit, a Growth plan at $9,350/year including a $255 monthly credit, and custom Enterprise pricing.

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.

Ory: How is usage metered?

Beyond the included credit, Ory charges per average daily active user (aDAU), per machine-to-machine token, and per permission check, with lower per-unit rates on the Growth plan.

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.

Ory: What payment methods are supported?

Ory accepts credit cards (Visa, MasterCard, Amex) and bank transfer, processed via Stripe.

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 Ory

More on Syft

Keep looking

Other head to heads