Lifecycle
unknown
AccelFury
af — the AccelFury IP development toolchain
Manifest-first development tooling for FPGA IP workflows.
Purpose and current status
The historical public website describes af as a manifest-first Rust CLI for FPGA development workflows.
Source access
unknown
Distribution access
unknown
Version and scope
Current version, lifecycle and supported workflow matrix have not been independently confirmed.
Access check
not_publicly_resolved; 2026-09-26
Content review
2026-09-26
Reported workflows
These integrations are described in the historical public website. A current approved workflow matrix and exact tool versions are needed before evaluation.
| Workflow / integration | Role | Source state |
|---|---|---|
| Manifest-based project description | Inputs describe the component and target assumptions. | reported |
| Verilator simulation | Simulation integration; supported configurations require confirmation. | reported |
| Yosys checks | RTL checking integration; this does not establish timing closure. | reported |
| FuseSoC packaging | Integration packaging; this does not establish board qualification. | reported |
Inputs and outputs
Plan evaluation around a component manifest, RTL, selected target and tool versions. Confirm the actual input schema and available report or package formats with the supplied version.
Checks, simulation, build and packaging are distinct workflows. A successful command does not establish board functionality or application acceptance.
Limitations
Review boundaries before committing to a workflow.
- Current lifecycle, source access, distribution and workflow support require confirmation.
- The historical public website describes a Rust CLI. No installation command or downloadable evaluation package is confirmed here.
- A workflow integration is not a guarantee for every FPGA vendor, board or tool version.
Licensing and evaluation
License terms for the current distribution have not been confirmed. Discuss the intended use before evaluation.
Documentation
The website explains the evaluation path and evidence policy. Current CLI documentation must accompany any agreed distribution.