Text-only edition of this page: /text/tiers.html
Flynn supports multiple engagement models scaled to the user. From a single sensor on a workbench to a thousand-asset fleet in an air-gapped facility. Specific terms are formalized through direct conversation with our team.
A 30–90 day engagement for business units proving Flynn in the lab, on the shop floor, or in the field.
For manufacturers embedding Flynn directly into commercial equipment at production scale. Flynn becomes the embedded intelligence inside your product.
For operators deploying Flynn across fleets, retrofit programs, new builds, or air-gapped environments.
| Pilot | OEM | Enterprise | |
|---|---|---|---|
| License form | Pilot engagement | Commercial · per-unit | Enterprise · deployment-scale |
| Source delivery | Precompiled binary | Precompiled binary (source optional) | Source on request |
| Integration support | — Direct contact | ✓ Co-engineering | ✓ Dedicated |
| Compliance package | — | On request | ✓ Included |
| Long-term support | 30d - 90d term | ✓ Source-stability | ✓ Multi-year contracts |
| Custom hardening | — | Case-by-case | ✓ Available |
| Deployment scale | Single asset · bounded | Per-product volume | Fleet-scale |
| NDA | As required | Required | Required |
| Pricing | Per engagement | Per-unit royalty | Deployment-scale |
| Typical onramp | Days to weeks | Weeks to months | Quarters |
For organizations deploying Flynn at scale, direct services are available — some today, others as the engagement framework continues to formalize.
A frozen-binary architecture holds everything still: the model never drifts, updates never churn, and no vendor-side change triggers a revalidation cycle. The classifier validated today is the classifier that runs in five years — byte-for-byte identical, with the same locked threshold and the same audit trail.
Flynn's long-term support commitment matches that architectural property. Security maintenance, compliance documentation, and direct support extend under the terms specified at license — for the life of the deployment.
We support what we ship, for as long as you run it.
A short description of the asset, the signal, and the deployment context is enough to start the conversation. We'll route from there.