Deliverables
Typical outputs for this service.
- private license discussion
- integration help
- priority fixes
- documentation support
- release-readiness review
Service
Commercial licensing and support
Commercial licensing discussions and paid support for integration, documentation, priority fixes and release-readiness review.
Scope
Deliverables
Scope is defined as reviewable engineering output.
Inputs required
Useful information for an initial review.
- Intended use case
- License scope
- Support expectations
Limitations
Boundaries that prevent unsupported claims.
- Closed-source, proprietary or customer-delivered bitstream use requires a separate commercial agreement.
Process
Engagement flow
The same review flow applies to public IP support, private prototypes and custom RTL work.
- Intake: workload, target, constraints and NDA requirement.
- Feasibility: architecture options, risks and evidence gaps.
- Implementation: RTL, wrappers, tests and docs where scope is approved.
- Review: simulation, build or measurement evidence before public claims.
Trust
Evidence and licensing references
Current public proof is intentionally limited to what can be inspected.
Public proof style
af-pdm-rx demonstrates the preferred public pattern: portable RTL, tests, docs, board wrappers and explicit evidence gaps.
Licensing boundary
Commercial and proprietary use is handled by direct agreement where applicable.
Next step
Request Licensing and support
Send the workload, target board or FPGA family, timing target, throughput goal, power constraints, interface assumptions and NDA requirement.