The MSys SBOM Generator analyzes Delphi projects and creates a standardized CycloneDX SBOM after a successful build. Package sources, versions, licenses, and Package URLs are documented right where the project is built.
Generate Software Bill of Materials (SBOM) directly from your Delphi projects
– without additional tools and ready for integration into existing workflows.
The generator maps compiled units to the packages and libraries used. This results in an SBOM containing origin, version, license information, and PURLs instead of just a list of technical files.
Generate Software Bill of Materials (SBOM) directly from your Delphi projects
– without additional tools and ready for integration into existing workflows.
The generated SBOM is provided as a CycloneDX JSON file. This format enables standardized use in security and compliance tools, as well as sharing with customers, partners, or auditors. It also facilitates integration into existing evaluation and monitoring systems. The focus is not only on creation but on direct further processing.
In addition to IDE integration, a CLI version is available that can be flexibly integrated into existing processes. It can be used both locally within the IDE and fully automated. Unlike generic SBOM tools, this solution is specifically developed for Delphi.
The system takes existing SBOMs into account and automatically supplements missing information.
This creates a complete and consistent SBOM – even with incomplete source data.
The SBOM plugin extends the Delphi IDE with an integrated function for analyzing and managing software components. As a developer, you can fully comply with your SBOM obligations without leaving the Delphi IDE.
The generated SBOM is provided as a CycloneDX JSON file.
This format enables:
- standardized use in security and compliance tools
- sharing with customers, partners, or auditors
- integration into existing analysis and monitoring systems
The focus is not only on creation, but on direct processing.
In addition to IDE integration, a CLI version is available that can be flexibly integrated into existing processes.
Typical scenarios:
- SBOM creation in automated builds
- Integration into CI/CD pipelines
- Processing of CycloneDX files in downstream systems
Can be used both locally in the IDE and fully automated.
The system takes existing SBOMs into account and automatically supplements missing information.
This creates a complete and consistent SBOM – even with incomplete source data.
This means:
- existing SBOMs are automatically adopted
- integration along dependencies (parent-child principle)
- automatic generation of virtual SBOMs for components without their own SBOM
- centralized management of this information
Unlike generic SBOM tools, this solution is specifically developed for Delphi.
This means:
- better detection of Delphi-specific components
- direct integration into the development process
- less manual effort
Additionally, there is a cooperation with Embarcadero to integrate the SBOM function even more deeply into the Delphi ecosystem in the future.
Many existing applications are based on legacy Delphi codebases.
This often leads to:
- incomplete documentation of dependencies
- lack of automated solutions
manual and error-prone processes
- no unified library management system
- components and dependencies are often distributed across the entire hard drive
Generic SBOM tools are often not suitable for this.
The Cyber Resilience Act (CRA) establishes new requirements for the security and transparency of software products.
Companies will need to:
- document deployed components
- make dependencies traceable
- provide SBOMs
Automated SBOM generation thus becomes a central component of modern software development.
A Software Bill of Materials (SBOM) is a structured listing of all components, libraries, and dependencies of an application.
It is typically provided in formats such as CycloneDX JSON and serves to:
The MSys Tool Suite extends Delphi and C++Builder projects in RAD Studio 12 and above with tools for task management, AI support, component transparency, and release processes. The plugins are installed together and are directly accessible in the IDE.
Many companies run business-critical software written in Delphi.
These projects are long-lasting, stable and economically significant. At the same time, the demands placed on software development are increasing: traceability, automation, secure supply chains, AI-powered analysis and regulatory transparency are increasingly becoming mandatory. The MSys Tool Suite bridges this gap. The suite extends RAD Studio 13 with a modular, Delphi-native tool layer. Tasks, AI access, SBOMs and IDE support functions are integrated directly into the development process as plugins. This ensures there are no disconnects between the IDE, the file system, source code management, assistance systems and compliance documentation.
The required plugins are installed together, appear in the MSys menu, and work directly within the context of RAD Studio. This avoids creating another platform alongside the IDE. The functions complement the existing development workflow where they are needed.
Whether it's a support request, a suggestion for improvement, or a new feature wish – you can easily submit your concern via our ticket system and track the processing status at any time.
Thank you! Your ticket has been created.
Vielen Dank für Ihre Unterstützung und Ihre Mithilfe zur Verbesserung des Produktes.
Thank you very much for your support and for helping us to improve the product.
Sign up here to receive information and updates about our SBOM Generator.
Disclaimer:
Our new software is currently in the beta phase. You can try it out for free and help us improve it by providing your feedback. Please note that this is a pre-release version which may still contain bugs.
This software is currently in the beta phase. This version is intended solely for testing and evaluation purposes.
The beta version may contain errors, limitations or unexpected behaviour. It is provided ‘as is’, without any express or implied warranty.
No warranty claims apply to the beta version.
You use the software at your own risk.
We accept no liability for any damage, loss of data or consequential loss arising from the use of the beta version.
Features may be modified, expanded or removed at any time. We are under no obligation to continue the beta version or to provide a final version.
By using this software, you agree that anonymised feedback may be used to improve the software – unless you object to this.
The beta version is not intended for use in production business environments or safety-critical scenarios.
