DigiFX has not published an open-source program. Nothing in the product material behind this knowledgebase names a public repository, a license under which DFX code is released, or a contribution process. What is documented is the developer-facing surface: the APIs, SDKs, and integration points through which outside code connects to the platform.
01The documented developer surface
DFX Agency lists an APIs and SDKs area covering APIs for software development, kits for custom development, and support for third-party developers. Its cross-compatibility area separately lists APIs for third-party integrations alongside VR and AR hardware support.
DFX Exchange lists API access covering trading APIs, data feeds, and custom integrations.
On the platform side, two runtime-package components are explicitly integration-shaped: Product API Integration, described as active data integration from vendors for fields such as price, rating, and product information; and Main Capture System, described as lidar scanning, anchor systems, and generation for API integration.
None of these list an endpoint, an authentication model, or a documentation URL. Developers asking for access should be routed to DigiFX rather than pointed at a public spec that does not yet exist.
02Scripting and extension inside the tools
Customization does not always require an API. DFX Create includes visual scripting languages and a JavaScript implementation for triggering events and responses, and supports importing external assets into its library. Its export paths include popular game engines, ARKit and ARCore integration for mobile AR, and integration with 3D printing software. DFX Stream exposes the same visual-scripting model for interactive overlays and trigger-based events.
For most customization requests, this in-tool scripting layer is the realistic answer, not a code-level integration.
03Third-party ecosystems the software targets
The suite is built to interoperate with outside platforms rather than to replace them. Documented targets include VR and AR hardware from several vendors, app stores for publishing, existing social accounts for connection and cross-posting in DFX Social, multi-exchange support and real-time price feeds in DFX Exchange, and hardware wallets from Ledger and Trezor.
04What has not been stated
Two open items are worth naming rather than glossing:
- No licensing posture. There is no statement about whether any DigiFX code is, or will be, released under an open-source license, and no repository is referenced anywhere in the reviewed material.
- No attribution page. The DigiFX microsites are built on widely used open-source web libraries — jQuery, Bootstrap, Flexslider, Lightbox, and Masonry among them — loaded directly by the site pages. No third-party notices or attribution page was found in the site material. Whether one is needed is a legal question for DigiFX, not something this page should assert either way.