Ortelius vs OWASP Dependency-Track

Ortelius connects software inventory to deployment information so teams can trace packages and versions to the endpoints where they run. It accepts SPDX and CycloneDX SBOMs and can create an SBOM with Syft when one is missing. It checks inventory against OSV.dev for newly disclosed vulnerabilities every ten minutes, tracing affected packages through artifacts and deployments to endpoints. Its post-deployment security dashboard brings together project security signals, versioned SBOMs, live deployments and vulnerability detection, and correlates OpenSSF Scorecard results with deployed packages and versions. Ortelius describes the dashboard as continuously aligned with NIST 800-218 SSDF. The product is available as SaaS or on-premise/self-hosted software, with REST and GraphQL APIs protected by JWT middleware. A GitHub App supports installation connections and repository onboarding, but onboarding does not attach an SBOM. Ortelius OS Free costs nothing, with up to 5 components; DeployHub Enterprise costs $40 a month, billed $40 / component / month.

OWASP Dependency-Track is a free, self-hosted platform for managing software-component risk across a supply chain. It builds inventories from software bills of materials and identifies vulnerable components, supporting CycloneDX SBOM, HBOM, VEX, and VDR documents for ingestion, analysis, and production. Components can be matched against NVD, GitHub Advisories, OSV, OSS Index, Snyk, Trivy, and VulnDB, while integrated EPSS support helps prioritize mitigation. Integrity checks flag components when published hashes differ from those served by an upstream registry. A Common Expression Language policy engine evaluates component rules and can break a build when a policy fails. Alerts can be filtered by event fields and sent to Slack, Teams, Mattermost, email, or webhooks. API and web interfaces are available, with least-privilege portfolio access and single sign-on through OpenID Connect, Active Directory, and LDAP. Version 5.1 uses separate API and frontend container images, supports Kubernetes, and requires PostgreSQL.