FAQ
Straight answers about what Blueprint sells.
Direct answers for first-time buyers evaluating the product.
What is a Blueprint world model?
A digital environment built from real capture of one indoor facility and one workflow lane. It is not a generic benchmark scene or a synthetic environment generator — it represents one exact place.
What does a buyer actually receive with the site package?
The walkthrough media, timestamps, camera poses, intrinsics, site notes, and any available depth or geometry artifacts for that facility. Privacy, rights, and provenance metadata are included so your team knows what it can use and how.
What is hosted evaluation?
A Blueprint-managed runtime session on one exact site. Your team can rerun tasks, review failures, compare checkpoints, and export results without downloading or moving data into your own stack first.
What is a session-hour?
One hour of self-serve hosted runtime on one exact site. It covers the live session time used to run, rerun, inspect, and export results.
Why not just use a generic sim?
Generic sim is useful for broad pre-training and early iteration. Blueprint matters when the question depends on one exact site: its real geometry, occlusions, handoff points, and failure modes.
What formats and exports should we expect?
The exact export set depends on the listing, but the public docs and listing notes should tell you what is stable versus what varies. Common outputs include walkthrough video, timestamps, camera poses, rollout video, dataset exports, and raw run bundles tied to the hosted session.
Who can see our facility data?
Access follows the rights, privacy, and consent rules attached to the site. Blueprint keeps those controls on the listing instead of implying open access by default.
How close is this to a deployment guarantee?
It is not a deployment guarantee. The point is to ground the team on the real site sooner and cut bad assumptions earlier, not to replace stack-specific validation, safety review, or on-site signoff.
How fresh is the site data?
Freshness is a property of the listing, not a vague promise. If a package is stale, that should be visible as a refresh problem instead of being hidden in sales copy.
Can this work with different robots and runtimes?
Yes. The stable contract is the capture truth, the rights and provenance metadata, the site package, and the hosted-session contract. The runtime backend can change without changing that buyer-facing contract.
What if the exact site we care about is not in the catalog?
The public catalog is the starting point, not the full inventory. If your team needs a specific facility, use the contact path and say which site, workflow, and robot question matter.