Softwr

Cybersecurity · head to head

Rhombus Systems vs Syft

Rhombus Systems logo

Rhombus Systems

Cybersecurity

Cloud-managed cameras, sensors and access control with a per-camera annual licence

From
$149/year
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

  • Only Syft has a free tier, so it costs nothing to try first.
  • Each has a real cost: Rhombus Systems the per-camera annual licence never ends and a camera without an active licence stops working, so the total cost over a ten-year hardware life is several times the hardware price.; 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: Rhombus Systems covers On-camera storage, Syft covers Multi-format output.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Rhombus Systems and Syft actually diverge.

Attributes where Rhombus Systems and Syft differ
AttributeRhombus SystemsSyft
Starting price$149/yearFree
Pricing modelPer camera per year licence plus hardwareOpen source, no licence fee
Free tierNoYes
PlatformsWeb, iOS, AndroidmacOS, Linux, Windows, Docker

Identical on both: 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 Rhombus Systems

  • On-camera storage
  • No NVR or server
  • AI search
  • Access control
  • Environmental sensors
  • Unlimited users
  • Ten year hardware warranty
  • Optional cloud archiving

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.

Rhombus Systems

  • A school district running video across dozens of buildings with no local IT at each sitenot Syft
  • A clinic group needing door access and cameras in one console under a single audit trailnot Syft
  • A logistics operator that wants to search for a specific vehicle across sites without scrubbing footagenot Syft
  • An office estate replacing ageing NVRs where nobody remains who knows how to maintain themnot Syft

Syft

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

Where each one falls short

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

Rhombus Systems

  • The per-camera annual licence never ends and a camera without an active licence stops working, so the total cost over a ten-year hardware life is several times the hardware price.
  • Cameras must be Rhombus, so there is no reuse of existing IP cameras and migrating away means replacing every device rather than changing software.
  • Cloud archiving is priced separately by retention and stream count, and long retention on multisensor cameras runs into five figures per camera, which can dwarf everything else in the quote.
  • On-camera storage is the default retention, so a camera physically stolen or destroyed takes its unarchived footage with it unless cloud archiving was paid for on that camera.
  • Analytics and integrations are good for mid-market needs but shallower than a dedicated enterprise VMS with a large third-party ecosystem, so specialist requirements like advanced LPR or forensic search hit limits.

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

Rhombus Systems

$149/year
  • Professional$149/year
    • Per camera per year
    • Cloud console and management
    • On-camera storage retention
  • Enterprise$199/year
    • Per camera per year
    • Everything in Professional
    • Flexible cloud archiving options
  • Cloud archiving$undefined/year
    • Priced separately by retention period and stream count
    • Multisensor cameras cost several times a single sensor camera
    • Long retention on multisensor models can reach five figures per camera

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 Rhombus Systems if

  • You need on-camera storage.
  • You work on Web, iOS, Android.
  • You also want no nvr or server.
Rhombus Systems 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 Rhombus Systems or Syft better?
Neither clearly leads. Rhombus Systems starts at $149/year and Syft at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Rhombus Systems or Syft?
Syft has a free tier; the other does not. Paid plans start at $149/year for Rhombus Systems and Free for Syft.
Does Rhombus Systems or Syft run on more platforms?
Rhombus Systems runs on Web, iOS, Android. Syft runs on macOS, Linux, Windows, Docker.
Can I use Syft for free?
Yes. Syft has a free tier, so you can try it without paying. Rhombus Systems starts at $149/year.
What is Rhombus Systems best used for?
Rhombus Systems is most often used for a school district running video across dozens of buildings with no local it at each site, a clinic group needing door access and cameras in one console under a single audit trail, a logistics operator that wants to search for a specific vehicle across sites without scrubbing footage, an office estate replacing ageing nvrs where nobody remains who knows how to maintain them. Of those, a school district running video across dozens of buildings with no local it at each site and a clinic group needing door access and cameras in one console under a single audit trail are not what Syft is typically brought in for.
What can Rhombus Systems do that Syft cannot?
Rhombus Systems covers On-camera storage, No NVR or server, AI search, Access control. Syft covers Multi-format output, Broad ecosystem coverage, Binary classifiers, In-toto attestations.

Answered from the vendors’ own pages

Rhombus Systems: Do I need an NVR or a server?

No. Cameras record on board and connect directly to the cloud console, which is the main operational reason organisations pick it.

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.

Rhombus Systems: What does the licence cost?

Roughly $149 per camera per year for Professional and about $199 for Enterprise, typically sold in one, three, five or ten year terms.

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.

Rhombus Systems: Is cloud storage included?

No. On-camera storage is the default. Cloud archiving is a separate charge priced by retention duration and number of streams.

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.

Rhombus Systems: Can I use my existing cameras?

No. The platform works only with Rhombus hardware, which is the trade-off for the zero-server architecture.

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 Rhombus Systems

More on Syft

Keep looking

Other head to heads