Compatibility and exports
What stays stable, what the package contains, and what can vary by site.
This page is for technical buyers. It separates the stable product contract from the listing-specific details so your team can tell what is safe to assume and what should be checked on the exact site.
Stable contract
These parts of the product stay the same regardless of which site or runtime backend is used.
- Capture truth: walkthrough media, timestamps, poses, and device metadata
- Rights, privacy, consent, and provenance metadata
- Package manifests and hosted-session contracts
- Buyer-facing licensing, export, and access rules
Site package contents
The site package gives your team everything it needs to run its own world model stack on that facility.
- Walkthrough video, timestamps, and camera poses tied to one real facility
- Intrinsics, depth, and geometry artifacts when the source capture supports them
- Site notes, provenance, privacy, and rights metadata
- Package manifest and reference material for building your own world model
Hosted evaluation outputs
Hosted evaluation is a managed runtime session on one exact site. Your team can run, review, and export without moving data into your own stack first.
- Repeatable runs on the same exact site
- Rollout video, failure review, and checkpoint comparison
- Dataset, raw bundle, and export generation tied to the listing
- A browser-accessible runtime session — no local setup required
What varies by listing
Not every site has the same artifacts or export options. Check the listing before assuming every lane supports the same depth of work.
- Depth and geometry coverage
- Available scenario variations and start states
- Robot assumptions and sensor requirements
- Export set, freshness state, and any restricted zones