Publish a secure SBOM transparency portal.
Share minimal component data publicly while granting deeper access to approved customers.
Public component disclosure
Customer access workflows
NDA-protected SBOM sharing
Automatically generate, publish, and maintain your open-source disclosure pages, directly from your CI/CD pipelines.
Publish software component transparency without exposing sensitive information.
The Exodos SBOM Trust Center lets you share selected SBOM data publicly.
Approved customers and partners can request deeper visibility when needed.
Control exactly what information is visible, who can access it, and under which conditions.
No static SBOM documents.
No manual disclosures.
Just a secure, continuously updated transparency portal.

Share minimal SBOM data publicly while granting deeper visibility through controlled customer access.
Share minimal component information.
Customers request deeper visibility.
Grant access manually or automatically with optional NDA.
Not all SBOM information should be public.
The Trust Center allows you to define visibility levels for different audiences, ensuring sensitive software details remain protected.
Publish a minimal component inventory that typically includes:
Component name
License
Package or project URL
This provides transparency while protecting implementation details.
Customers who require deeper insight can request access directly through the Trust Center.
Once approved, they can access extended SBOM information, depending on your configuration.
Examples include:
Component versions
Dependency metadata
SBOM generator information
Additional software metadata
Administrators can configure exactly which fields appear in each view.
Visibility settings allow you to:
define public component disclosures
control which metadata is visible to authenticated users
filter sensitive SBOM fields
tailor transparency levels to different audiences
This ensures that transparency remains intentional and controlled.
Customers and partners can request access to additional SBOM information directly through the Trust Center.
Administrators can choose how requests are handled:
Manual approval for each request
Automatic approval policies
Restricted access by default
This ensures detailed SBOM information is only shared with verified stakeholders.
Organizations can require an NDA before granting extended access to SBOM information.
This allows companies to safely share deeper software supply chain insights while protecting intellectual property and architectural details.
Once the NDA is completed and approved, users gain access to the configured extended SBOM view.
Transparency should never come at the cost of security.
The Trust Center includes built-in mechanisms to ensure secure information sharing:
authenticated user access
approval workflows
access control policies
full audit trails
attribute-based access control
Administrators can track who accessed which information and when, providing accountability and compliance visibility.
The Trust Center is connected directly to your SBOM inventory.
As your software evolves, the published information automatically updates.
No outdated disclosure pages.
No manual updates.
No fragmented SBOM distribution.
Your transparency portal always reflects the latest state of your software supply chain.
See how our automated pipeline works from start to finish.
Up and running in minutes.
Share package name, license, and project URL.
Customers request deeper visibility directly from the portal.
Admins approve access automatically or manually and optionally require NDA.
Control exactly who can access your SBOM transparency portal.
Attribute-based access control allows you to define policies based on organization, role, or approval status — ensuring only authorized stakeholders see detailed SBOM information.
Require customers or partners to sign an NDA before accessing extended SBOM details.
This ensures sensitive software supply chain information is only shared under clear legal protections.
Define exactly which SBOM fields are visible to different audiences. Public views can expose only minimal component information while sensitive metadata remains protected.
Provide software transparency without exposing sensitive details.