For OEM and Tier-1 partners who want to bring the methodology in-house.
FieldSpace's primary ICP is AV operators and the insurers underwriting them. This page is for OEM and Tier-1 validation partners who want to run the deterministic methodology inside an existing safety case program on a per-engagement basis.
What an OEM or Tier-1 partner can review
Inside a partner program, FieldSpace contributes the same deterministic evidence layer that backs the operator-side product. Replay, per-claim traces, low compute footprint, and disagreement cases against the partner's stack.
Deterministic replay
Same scene, same observer output, same audit trail. Useful for public benchmarks, customer logs, and edge-case regression suites.
Traceable triggers
Hazard decisions carry source tracks, derived risk quantities, timing, and the reason a warning was emitted.
Low evaluation overhead
The observer path does not require a new training pipeline, labeling program, or GPU-heavy retraining loop to start producing evidence.
Reviewable safety path
Under NDA, the safety path can be inspected closely enough for partner engineers to challenge assumptions and reproduce results.
Three engagement tiers, all capital-light
Log study
- ›Send us your MCAP drives
- ›We run Safety Observer offline
- ›Side-by-side hazard comparison
- ›Traced disagreements report
On-vehicle shadow
- ›FieldSpace on your dev fleet
- ›Live shadow against production stack
- ›Quarterly safety-case deliverables
- ›No actuator authority in the default evaluation scope
Production path
- ›ASIL decomposition review
- ›Commercial model after pilot evidence
- ›Safety-case support artifacts
- ›Source escrow included
Starts with logs, then integrates where useful
Your perception stack already produces object tracks and ego state. That's all we need. We publish hazards and a cost-map on an interface your team can review before deciding whether it belongs in a live shadow or planner path.
- ›ROS 2 interface for pilot and bench integration.
- ›AUTOSAR/SOME-IP mapping available for partner review.
- ›gRPC with protobuf schema for custom platforms.
- ›Simulation and replay interfaces by pilot scope.
service FieldSpace {
// your perception ⟶ our stack
rpc PublishTracks(stream TrackBatch)
returns (google.protobuf.Empty);
// our stack ⟶ your planner
rpc StreamHazards(HazardRequest)
returns (stream HazardFrame);
rpc StreamCostMap(CostMapRequest)
returns (stream CostMapFrame);
// fallback trace stream
rpc StreamMrmState(google.protobuf.Empty)
returns (stream MrmPhaseUpdate);
}Mutual NDA first. Source access second.
We'll sign your standard NDA and follow it with a 20-minute deep-dive with your safety, perception, and validation leads. Slides are welcome but optional.