Three paths. One conversation.
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.
Tier 01 · Pilot program
Priced per engagement.
A 30–90 day engagement for business units proving Flynn in the lab, on the shop floor, or in the field.
- Bounded scope
- 30d - 90d Consulting engagement
- NDA as required
- Direct engineering contact
- Architectural commitments per whitepaper
Tier 02 · OEM licensing
Per-unit royalty · tailored. Most engaged.
For manufacturers embedding Flynn directly into commercial equipment at production scale. Flynn becomes the embedded intelligence inside your product.
- Precompiled binary or source license
- Integration support
- Long-term source stability
- Terms scaled to deployment volume
- Co-engineered signal-conditioning advice
Tier 03 · Enterprise
Deployment-scale · multi-year.
For operators deploying Flynn across fleets, retrofit programs, new builds, or air-gapped environments.
- Source access and certification support
- Integration with existing systems
- Deployment automation
- Compliance reporting packages
- Direct support, multi-year terms
Compare: tier by tier
- License form
- Pilot: Pilot engagement
OEM: Commercial · per-unit
Enterprise: Enterprise · deployment-scale - Source delivery
- Pilot: Precompiled binary
OEM: Precompiled binary (source optional)
Enterprise: Source on request - Integration support
- Pilot: Direct contact
OEM: Yes — co-engineering
Enterprise: Yes — dedicated - Compliance package
- Pilot: No
OEM: On request
Enterprise: Yes — included - Long-term support
- Pilot: 30d - 90d term
OEM: Yes — source-stability
Enterprise: Yes — multi-year contracts - Custom hardening
- Pilot: No
OEM: Case-by-case
Enterprise: Yes — available - Deployment scale
- Pilot: Single asset · bounded
OEM: Per-product volume
Enterprise: Fleet-scale - NDA
- Pilot: As required
OEM: Required
Enterprise: Required - Pricing
- Pilot: Per engagement
OEM: Per-unit royalty
Enterprise: Deployment-scale - Typical onramp
- Pilot: Days to weeks
OEM: Weeks to months
Enterprise: Quarters
Enterprise services: direct services
For organizations deploying Flynn at scale, direct services are available — some today, others as the engagement framework continues to formalize.
Embedded integration consultation — available today
- Source-level integration with existing firmware
- Signal-conditioning advice
- Sampling-rate optimization
- Telemetry adapter selection
Reference deployment kits — available today
- Reference Docker stack
- Telemetry collector + time-series storage
- Visualization dashboards
- Fleet-scale starter scaffolding
Direct technical support — available today
- Engineering-team access through integration
- Support continues into operational maturity
- Licensed-deployment scope
Compliance briefings — available today
- Source-level walkthroughs
- Deterministic-behavior attestation
- Documentation packages for safety, regulatory, procurement
Multi-asset coordination layer — in active development · 2026 pilots
- Spinal-cord layer of the roadmap
- Pilot customer engagements engaging this year
- Composes existing Flynn detectors
Formalized compliance packages — in active development
- Safety-system certification templates
- Regulated-manufacturing audit packages
- Defense-environment qualifications
- Today: case-by-case · productized over the next year
Fleet-management tooling — in active development
- Operational dashboards for distributed deployments
- Configuration management at scale
- Today: reference architecture · productized version follows coordination-layer roadmap
Custom hardening — on request
- Configuration tuning for specific environments
- Regulatory regime alignment
- Hardware-profile tailoring
- Decade-scale support contracts available
Long-term commitment: the version validated today is the version that runs in production
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.
Engage: tell us what you’d put it on
A short description of the asset, the signal, and the deployment context is enough to start the conversation. We’ll route from there.
- For OEMs
- Volume, product family, integration target firmware.
- For enterprises
- Asset class, fleet size, network posture, compliance regime.
- For evaluators
- Dataset on hand, signal type, target hardware.