About

About AccelFury

Portable FPGA IP cores, an open Rust toolchain (af) and evidence-first hardware acceleration work. Every public claim is backed by a repo, test or measurement.

Public surface

GitHub footprint

4 public repositories at https://github.com/AccelFury: 1 true IP core, 1 toolchain, 1 template repository, plus the org profile.

IP cores

1 true IP core documented in /data/cores.json.

Toolchain

af — Rust CLI for manifests, simulation, lint and packaging.

Template repo

core-template is a starter repository and example surface, not a catalog core.

Releases

0 GitHub releases. Reviewable evidence lives in the repos.

Repository templates

Templates

Templates are listed separately so the IP catalog stays reserved for reusable cores.

core-template

Production-style FPGA IP repository template with af_mod_add modular-addition example, registries, checks and board metadata.

  • Starter repository and example flow.
  • Board matrix entries are scaffolding until evidence is attached.
  • Generated IP still needs project-specific verification.

Tooling

Open toolchain

The same toolchain powers all AccelFury IP — it is the most active artifact of the organization.

af

Rust CLI for FPGA IP development: manifests, Verilator simulation, Yosys checks, FuseSoC packaging, vendor backend orchestration.

  • Powers the verification-first workflow used by af-pdm-rx and core-template.
  • CLI surface, JSON shapes and manifest schema may still change before v1.0.
  • Primary language: Rust (~91%).

Principles

Operating principles

Claims on this site must be backed by repo-visible docs, tests, release notes or hardware evidence.

  • Portable RTL stays portable and board-neutral where possible.
  • Board support is evidence-gated, not implied by a wrapper name.
  • Benchmarks are workload-specific and remain pending until measured.
  • Research pages stay research pages until production evidence exists.

Boundary

Claim boundaries

The site avoids customer, investor, API and catalog claims that are not public.

  • No named public customers or investors are listed.
  • No public production API is claimed.
  • No published GitHub release artifacts exist yet.
  • Additional public IP cores appear only after documentation and evidence are available.