AURIG — open-source FPGA tooling stack

How the pieces fit

AURIG Core sits at the bottom: a VHDL parser and the canonical project manifest. AURIG Lint and AURIG Doc are built directly on it, reading the same parsed structure to check code and to document it; both need a Core checkout to run.

AURIG Build is independent. It drives an FPGA project from the same manifest schema through synthesis, implementation, and bitstream across four vendors, and it can be used on its own with no other part of the stack installed.

AURIG Sentinel sits on top as the scheduler. It runs pipelines unattended on the workstation that holds the EDA licences, delegating the HDL-aware work outward rather than doing it itself.

The five tools

AURIG Lint — A VHDL lint engine and CLI with configurable rules for naming, library policy, synthesizability, and documentation, reporting as text, JSON, Markdown, or HTML.
AURIG Doc — Generates browsable documentation from VHDL, for a single file or a whole project, as Markdown or self-contained HTML.
AURIG Build — FPGA project automation: one YAML file drives synthesis, implementation, bitstream, and simulation across Vivado, Quartus, Diamond, and Radiant.
AURIG Sentinel — An on-premise pipeline orchestrator for FPGA teams: per-project YAML, scheduled unattended runs, logs and artifacts bundled per run.
AURIG Core — The shared Tcl foundation of the AURIG stack: a VHDL parser that turns source into a queryable dictionary, plus project utilities and the canonical manifest schema.

What you can try without a licence

Linting and documentation need no vendor toolchain and no licence, and simulation-based regression can run on GHDL. Synthesis, implementation, and bitstream generation need the corresponding vendor tools installed.

Status

Early access. Published and usable, with the interfaces still free to change. Each repository is the current source of truth for what its release supports.

Getting started

AURIG Build and AURIG Sentinel install from PyPI. Core, Lint, and Doc are Tcl packages used from a checkout. Each repository carries its own installation and usage documentation.

← Open source