# Freight Secondary at Boston: deployment

Canonical ID: `3777333f-fdb8-402e-8a5e-f5babd56ee0d`

Secondary product deployment at Freight Farms operational region.

**Trust tier:** Catalog entry · 1 source · not yet field-verified

_Last updated: 2026-06-08_

- **Slug:** freight-farms-secondary-deployment
- **Status:** operational
- **Model:** [Freight Secondary](/models/freight-farms-secondary.md) (id: `a5001869-ae76-4994-8530-838b4c48a441`)
- **Company:** [Freight Farms](/companies/freight-farms.md) (id: `48b8c39a-b5bb-4b35-a738-ca499e43e7af`)
- **Location:** [Boston](/locations/boston.md) (id: `2861e3d7-c676-4cc6-9769-935e82f5177d`)

## Verification log (0, append-only)

_No verifications recorded._

## Sources (1)

1. https://rover.report

## Common questions

### What is the Freight Secondary deployment at Boston?

Freight Secondary, built by Freight Farms, is recorded as a deployment at Boston on the DEPLOY registry. Freight Farms operates the deployment directly.

### Who operates Freight Secondary at Boston?

Freight Farms, the manufacturer of Freight Secondary, operates this deployment directly. This is a maker-deploys-its-own-product arrangement rather than a customer pilot.

### Have there been incidents at the Freight Secondary deployment at Boston?

No active incidents affecting this deployment are recorded on the DEPLOY registry. Absence of recorded incidents is not a guarantee no incident occurred; DEPLOY records only sourced incidents and suppresses retracted ones.


_API: GET /v1/robots/3777333f-fdb8-402e-8a5e-f5babd56ee0d · feeds: GET /v1/feeds?deploymentId=3777333f-fdb8-402e-8a5e-f5babd56ee0d · canonical URL: /deployments/freight-farms-secondary-deployment_