FabricGate
Discover, pull and verify FPGA designs for your board — one command, any runtime.
FabricGate is a package registry for FPGA designs (bitstreams plus the metadata a runtime needs to load them). This repository contains the client side: the fabricgate CLI, the Python SDK, the shared data models, and the public API contracts. The hosted registry lives at https://registry.fabricgate.dev.
Status: alpha (0.1.0). The registry is being seeded with community PYNQ overlays. Interfaces marked stable in
docs/specs/are kept backward compatible; everything else may still change before 1.0.
Install
pip install fabricgate
Python 3.11 or newer. fgate is installed as a short alias of fabricgate.
Three steps to a running design
# 1. Find a design for your board
fabricgate search --platform pynq-z2/pynq adder
# 2. Pull it (bitstream + hwh + manifest, digests verified on download)
fabricgate pull example/adder-demo:1.0.0 --platform pynq-z2/pynq
# 3. Load it with the runtime you already use
python -c "from pynq import Overlay; ol = Overlay('adder-demo/adder.bit')"
example/adder-demo is a placeholder name; run fabricgate search to see what is actually published. The --platform value is <board>/<runtime>; run fabricgate pull --help for the resolution rules, including the generic-<device> fallback.
What the CLI can do
| Command | Purpose |
|---|---|
search, info, diff, stats, watch |
discover designs and track updates |
pull, verify, list |
download with digest verification, re-verify, inspect the local cache (list --remote [--namespace <ns>] lists designs on the registry) |
build, push, yank, deprecate |
publish your own designs (build generates the Platform Manifest and Design Index from a build directory) |
login, token, quota, webhook, license-check |
account, automation and policy helpers |
fabricgate --json gives machine-readable output for every command.
Supported boards and runtimes
The bundled Board DB (src/fabricgate/data/board-db/official.yaml) currently knows these boards:
| Board | Device | Runtime |
|---|---|---|
pynq-z1, pynq-z2 |
xc7z020 | pynq |
zcu104 |
xczu7ev | pynq, linux-fpgamgr |
zcu106 |
xczu7ev | pynq |
zcu102 |
xczu9eg | pynq |
ultra96-v2 |
xczu3eg | pynq |
pynq-zu |
xczu5eg | pynq |
kv260, kr260 |
xck26 | pynq |
zcu111, rfsoc2x2 |
xczu28dr | pynq |
rfsoc4x2, zcu208 |
xczu48dr | pynq |
zcu216 |
xczu49dr | pynq |
pico-ice |
iCE40UP5K | nanopynq (Phase 3, forward reference) |
generic-xc7z020, generic-xczu7ev |
— | device-level fallback for boards not yet listed |
Adding a board is a data change; see CONTRIBUTING.md.
SDK
from fabricgate.sdk import api
result = api.pull("example/adder-demo:1.0.0", platform="pynq-z2/pynq")
print(result.artifacts)
The SDK wraps the same client the CLI uses. See docs/specs/client-behavior.md for the resolution and caching rules.
Public contracts
docs/contracts/ is the source of truth for the registry's public API:
openapi.yaml/openapi.json— Registry HTTP APIschemas/design-index.schema.json,schemas/platform-manifest.schema.json,schemas/board-db.schema.json— wire formatsCHANGELOG.md— contract changes and migration notes
Specifications for the CLI, client behaviour and data formats are in docs/specs/.
Self-hosting and the registry implementation
The registry server is operated as a hosted service and its implementation is not published at this stage (see docs/specs/ for the distribution policy summary in client-behavior.md). Everything a client needs to interoperate — API, schemas, error formats — is in this repository, so alternative implementations are possible.
Contributing, security, license
- CONTRIBUTING.md — development setup, tests, pull requests
- SECURITY.md — how to report a vulnerability
- LICENSE — MIT
Verifying what you install
Every release is published from this repository via PyPI Trusted Publishing and carries a GitHub build-provenance attestation:
pip download --no-deps fabricgate==0.1.0
gh attestation verify fabricgate-0.1.0-py3-none-any.whl --repo harurun78/fabricgate
Release files for fabricgate 0.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| fabricgate-0.1.3.tar.gz | 331.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fabricgate-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 428.2 kB
Release files / fabricgate-0.1.3.tar.gz
| Download URL | fabricgate-0.1.3.tar.gz |
|---|---|
| Size | 331.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
457185ee80cd8ea2ab46d8004378a0f7e25fdeba765bd402d8c73fb6f2b8ce83
|
|
BLAKE2b-256 checksum How to use checksums |
cc6b55812e888aa27e86229262931d719ed0eb34b92f4c0a0ee9043663486d41
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 24, 2026.
Transparency logRelease files / fabricgate-0.1.3-py3-none-any.whl
| Download URL | fabricgate-0.1.3-py3-none-any.whl |
|---|---|
| Size | 96.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
70762952e56787425eff8f56d42713ea3a641fd95dfd98665cf2a8488ef5ddd7
|
|
BLAKE2b-256 checksum How to use checksums |
49e96b21d0ad3e3c55e29f39bfc28063b3848c25b281f715d2f3983e82781fa5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 24, 2026.
Transparency log