Trust materials for security, privacy, legal, and procurement review.
Review the public diligence packet, understand what Roam states today, and see what moves under NDA once a real program is underway.
Proof materials
Sample manifests, checksums, delivery-packet examples, legal pages, docs, and demo surfaces are linked from one place.
Direct review paths
Security, privacy, legal, and restricted-environment reviews are explicit entry points, not hidden behind a generic sales CTA.
Ownership and handling stance
Customer ownership, retention and deletion handling, and demo boundaries stay visible and consistent.
Public proof ledger
Sample manifest
Example manifest structure showing delivery versioning, formats, checksums, and CRS metadata.
Why review it: Roam can describe delivery structure in a machine-readable way before a live program starts.
Boundary: This is an illustrative public example, not a customer-specific delivery commitment.
Checksum example
Example checksum file showing artifact validation format.
Why review it: Roam can expose integrity checks as part of the delivery packet.
Boundary: Checksums shown here are example values for public proof only.
Sample delivery packet
Public outline of a delivery packet with manifests, QA, artifact references, and caveats.
Why review it: Roam thinks in terms of delivery packets rather than isolated media files.
Boundary: Commercial terms, sensitive handling rules, and customer-specific destinations stay under NDA.
Acceptance criteria outline
Example definition-of-done checklist for coverage, metadata, and artifact integrity.
Why review it: Roam can frame output acceptance criteria in operational terms.
Boundary: Thresholds are illustrative and must be set in the actual engagement.
Sample data dictionary
Example field-level description of a delivery manifest and asset metadata.
Why review it: Roam can expose the data contract in a reviewable format.
Boundary: Does not imply every field is always present for every program.
Redaction report template
Public template for logging privacy-sensitive handling and redaction outcomes.
Why review it: Roam can turn privacy review into an operational artifact.
Boundary: Program-specific handling rules still depend on the engagement.
Delivery release notes template
Public release note template for delivery updates and artifact changes.
Why review it: Roam can communicate dataset changes over time in a structured way.
Boundary: Illustrative only.
Sample SOW outline
Public outline for scoping deliverables, review requirements, and mobilization assumptions.
Why review it: Roam scopes around operational constraints, not just visuals.
Boundary: Not a commercial offer or legal agreement.
Security questionnaire template
Template for handling common security and data governance review topics.
Why review it: Roam can support diligence with structured materials.
Boundary: Does not imply a certification or control not explicitly approved.
Sample dataset catalog
Live demo datasets, manifests, and gated artifact downloads.
Why review it: The public demo routes are real and runnable today.
Boundary: Demo subsets are not equivalent to a production program or customer packet.
Sandbox and readiness APIs
Short-lived demo keys, sample dataset listing, and readiness scoring.
Why review it: Technical evaluators can verify endpoint behavior and sample shapes now.
Boundary: Not a production API commitment.
Restricted-environment review packet
Private packet covering handling plans, chain-of-custody, and restricted-environment assumptions.
Why review it: Roam can route sensitive programs through a stricter review path.
Boundary: Not public and not implied by the public site alone.
Public stance
Customer data ownership
Roam treats customer program data as customer-owned. Customer-specific terms are finalized in the engagement.
Retention and deletion
Retention, deletion, and delivery controls are defined in the program agreement before mobilization.
Evaluation surface boundary
Sandbox keys, sample datasets, llms.txt, and MCP help buyers evaluate fit. They do not promise a broad self-serve production platform.
Public vs NDA-only
Public materials show packet structure and review paths. Customer-specific handling plans, chain-of-custody details, and restricted-environment materials stay gated.
Technical evaluation
ML engineers, simulation leads, GIS analysts, platform teams
Start with docs, sample data, format references, and the sandbox before opening a live program.
Public and available now through developer docs, sandbox APIs, and sample-data examples.
Validate technical fitLive program scoping
Founders, VPs, robotics PMs, autonomy leads, operations buyers
Scope environments, outputs, review constraints, and timeline through an intent-first intake path.
Public intake is available now; commercial and operational specifics are finalized in the engagement.
Start program scopingSecurity, privacy, and legal diligence
Security reviewers, privacy counsel, legal, procurement
Bring data handling, deletion, privacy-sensitive capture, and diligence questions in early.
Public diligence materials are available now; customer-specific review expands under NDA when needed.
Start diligence reviewRestricted-environment review
Defense autonomy, secure infrastructure, sensitive facility owners
Start NDA-first review for handling plans, access assumptions, delivery controls, and restricted environments.
Public materials explain the process; customer-specific handling stays gated.
Review restricted pathFrom evaluation to scoping
Need security, privacy, or procurement review?
Start with the trust materials, then move into the right diligence path without restarting the conversation later.
Raise NDA, security, privacy, and delivery constraints in the first conversation instead of after procurement restarts the process.
Need immediate scheduling? Use the programs inbox.