Evaluating and deploying DUST: buyer questions

A typical DUST pilot runs four to twelve weeks depending on the complexity of the application and the integration depth required. The pilot is structured in three phases. In the first phase — usually two to four weeks — Dust Identity works with the customer to select pilot objects, apply DUST coatings, enroll fingerprints, and validate authentication accuracy on the target substrate and in the expected operating environment. In the second phase, the customer's team performs authentication in their own workflows — incoming inspection, custody transfer, field verification — using the scanner hardware and DICE platform, typically supported by Dust Identity application engineers. In the third phase, Dust Identity and the customer review authentication data, identify any operational friction, and define the scope and architecture of the full deployment. Customers receive a pilot report documenting authentication accuracy, workflow integration findings, and deployment recommendations.

The stakeholder group varies by organization, but a typical enterprise deployment touches four functional areas. Supply chain and operations owns the deployment workflow: where DUST is applied, who performs authentication, and how authentication events are logged. IT and information security governs the DICE platform integration: API access, data governance, network configuration, and — for sensitive applications — air-gap or on-premise deployment architecture. Quality and compliance owns the authentication data record and its role in regulatory and customer-facing documentation. Procurement and program management drives the business case and vendor relationship. For aerospace and defense customers, a fifth stakeholder — legal or export control — is often involved early to address ITAR and data handling requirements. Dust Identity provides a deployment readiness guide and stakeholder briefing materials to support the internal alignment process.

No. DUST is designed to augment existing systems, not replace them. In most deployments, existing barcodes, serial numbers, RFID tags, and NFC labels remain in place and continue to serve their current functions. DUST adds a physics-based authentication layer underneath them. Existing ERP and MES integrations remain intact; DICE authentication events are written to those systems via API. If you currently use SAP HANA Cloud, for example, authentication confirmations and exception alerts can flow directly into your existing quality and inventory workflows. The only new infrastructure is the DUST application equipment — which for low-volume or field applications is as simple as a pen applicator — and the scanner hardware. Dust Identity's implementation team maps your existing data and workflow architecture before deployment begins to ensure the integration adds capability without disruption.

Retrofit tagging is supported and is a common deployment pattern, particularly for aerospace aftermarket, defense sustainment, and industrial equipment. For objects already in the field, DUST is applied at the next custody transfer or inspection event — incoming to a depot, incoming to an MRO, or at a scheduled maintenance check. The enrollment record created at that point documents the state of the object at time of tagging and becomes the baseline for all future authentication. For objects where provenance prior to enrollment is in question, the enrollment record can be flagged as a retrofit tag, preserving the distinction between factory-enrolled and field-enrolled items in the chain-of-custody data. For high-value assets where pre-enrollment provenance must also be documented, Dust Identity supports multi-source enrollment that attaches existing inspection records, historical maintenance logs, and supplier documentation to the new digital twin at the time of enrollment.

Total cost of ownership comprises four components: DUST material cost, scanner hardware, DICE platform licensing, and integration. At industrial scale, the DUST coating material itself costs approximately $0.00001 per item — a negligible variable cost for virtually any application. Scanner hardware costs vary by deployment type: handheld field devices, inline production scanners, and fixed inspection stations each have different price points, and Dust Identity works with customers to specify the right hardware mix for their volume and workflow. DICE platform licensing is structured around the number of enrolled objects and scan events, with enterprise pricing available for large programs. Integration costs are project-specific and depend on the existing systems landscape and the depth of ERP and MES integration required. Dust Identity provides a total cost model during the pilot phase so customers have a clear picture before committing to full deployment.

All authentication data in the DICE platform belongs to the customer. Dust Identity does not claim ownership of enrollment records, scan history, custody events, or associated documentation. On termination of a DICE subscription, customers receive a full export of their data in standard formats — JSON, CSV, and where applicable, blockchain records — within a defined transition period. The DUST coatings applied to physical objects remain in place permanently; they do not degrade or expire because the subscription ended. Objects already enrolled can continue to be scanned if the customer subsequently deploys alternative authentication software capable of reading the DUST fingerprint format, or re-enrolled into a new system. For customers with continuity-of-operations requirements, Dust Identity offers data escrow arrangements and open documentation of the fingerprint encoding format.

Application training is minimal. For pen and gel applicators — the DS-410 series and DS-700 epoxy — the learning curve is comparable to applying an adhesive or sealant. Operators learn consistent application volume, curing time, and quality verification in a half-day session. For UV-curable formulations, operators additionally learn to use the UV curing lamp and verify cure completeness. Inline and spray application in manufacturing environments is set up by Dust Identity application engineers and typically does not require operator training beyond standard equipment operation. Authentication training — performing a scan and interpreting the result — takes approximately one hour. The scanner interface presents a clear pass/fail result with confidence score; no technical expertise is required to interpret it. Dust Identity provides training documentation, video guides, and remote support during initial deployment.

No. Dust Identity works with customers across the full volume range, from single-asset tracking — a specific fleet of high-value tools, a consignment of critical spares, a set of research prototypes — to high-throughput manufacturing at millions of units per year. For very low-volume or exploratory applications, the DS-410 pen applicator and a handheld scanner enable deployment with minimal capital investment. Pilot programs can begin with as few as twenty to fifty objects. The DICE platform is priced to accommodate early-stage deployments and scales with volume. There is no minimum volume threshold for commencing a pilot or initial deployment.