Maturity: Early use.
Own statement
Date: 14 November 2026
No review by a third party. HelixTest checks are not GA4GH certification. A published revision and the current branch are not the same revision.
Maturity: Early use.
Own statement
Date: 14 November 2026
No review by a third party. HelixTest checks are not GA4GH certification. A published revision and the current branch are not the same revision.
When Ferrum runs, the files sit on the storage the operator configures. The default is a directory on the operator's own machine. The source code does not copy those files to a service run by Synaptic Four.
Present in the code
Date: 7 November 2026
Present in the code, no end-to-end test. The operator can choose another store, a sync target, or other peers. This does not show that files never leave the premises.
Source Source code Source code Source code Source code Source code Source code
Ferrum can be operated on your own infrastructure.
Tested
Date: 13 October 2026
Not an air gap: the setup includes Postgres, SeaweedFS and Keycloak. Not a clinical deployment.
A partner can ask for access to a dataset. For a file bound to a dataset, Ferrum allows access when the sign-in carries a release for that dataset or when the caller is an administrator. Ferrum does not decide the request.
Present in the code
Date: 7 November 2026
Present in the code, no end-to-end test. The request exists only when an external decision service is configured. The data holder's decision is not in this program. Unbound files and an administrator account are outside this check.
In the source code of the full gateway, one gateway exposes seven GA4GH interfaces: DRS, WES, TES, TRS, htsget, Beacon v2 and Crypt4GH. Code that exists is not an end-to-end test. The edge variant does not include three of the seven: WES, TES and TRS. Passports are not one of the seven. The full build includes a Passports route from this program. The edge variant does not include it. With external sign-in, the process logs that Passport checks use ga4gh-infra.
Present in the code
Date: 15 November 2026
Code that exists is not an end-to-end test. The edge variant does not include WES, TES, TRS or Passports. The full build includes the Passports route from this program. With external sign-in, the log names ga4gh-infra. Not certified. Details are on the evidence page.
For a file bound to a dataset, Ferrum allows access when the sign-in carries a release for that dataset or when the caller is an administrator. Access and downloads are recorded. A failed log entry does not stop the request.
Present in the code
Date: 7 November 2026
Present in the code, no end-to-end test. The log does not cover every data movement. A failed entry does not stop the request. The data holder's decision is not in this program.
Source code Source code Source code Source code Source code Source code
The edge variant and the full gateway are two builds of the same program (ferrum-gateway) in one source tree. The build decides which interfaces are included.
Present in the code
Date: 20 October 2026
What is not shown is that an operator can move from one size to another without rebuilding. Edge includes DRS, Beacon, htsget and Crypt4GH on SQLite. WES, TES, TRS and Passports belong to the full build.
The edge variant listens by default only on the local address 127.0.0.1. Any other address has to be set explicitly (FERRUM_BIND).
Present in the code
Date: 20 October 2026
Not re-tested in this review; state 0.3.10 not checked individually.
Ferrum keeps a hash-chained log of the events it records.
Tested
Date: 14 October 2026
The log covers recorded events only, not every data movement. It does not prove that data stayed on premises.
The health check compares the system clock with a time server, by default pool.ntp.org. The server can be replaced.
Present in the code
Date: 20 October 2026
Switching the probe off is not provided for. The probe sends no research data.
htsget in Ferrum currently returns whole files. Regions (reference name, start, end) are rejected for every kind of data (HTTP 400).
Present in the code
Date: 20 October 2026
A trial showed that the library htsget-search 0.14.0 produces region tickets for BAM and VCF. It is not built in yet. The edge size against the 52,428,800-byte gate is not in the evidence file.
The human Beacon offers part of the standard's routes (status, info, map and variant queries). The framework root paths, answers for individuals and samples, and the three access tiers are missing.
Present in the code
Date: 21 October 2026
Coordinate queries accept only human assemblies and chromosomes. Membership of a Beacon Network was not verified.
Edge runs on Linux x86_64, macOS and Windows through WSL2. For the Raspberry Pi 5 there is a program and an installer. It has not been tested in the field. For a lab laptop the guide names 8 to 16 GB of RAM and 50 GB of free disk. Installation is an install script and one start command, with no Docker and no database server. A network is needed only for the installation.
Present in the code
Date: 13 November 2026
Design targets, no published load test. Windows natively is not supported.
A Helm chart for Kubernetes is included. It has not been installed yet.
Present in the code
Date: 20 October 2026
This is not installed on a cluster. A template ready to run is not shown. Files being present is not a running deployment.
The source tree includes an installation guide and an operator handbook. They describe how to set Ferrum up without Synaptic Four. They do not state support terms.
Present in the code
Date: 7 November 2026
Present in the source tree, not installed in this review. No support promise, and no promise that Synaptic Four runs the system.
In two tested setups (edge program on an isolated machine, pinned demo images on an internal network) no outbound connections were observed. Not evidence for every configuration. The time probe (NTP) is intended and could not be sent in the isolated setup.
Tested
Date: 20 October 2026
This does not hold for every configuration. The time probe is intended and could not be sent in the isolated setup. Taking in data was not checked, because a sign-in was required. The composed demo setup and the demo start did not run. Only those time windows were observed.
In the program itself, authentication is switched on by default.
Present in the code
Date: 20 October 2026
In the Compose setup shipped for the demo, authentication is off by default (environment variable). Anyone using it beyond a demo switches it on.
If the configuration file is invalid, Ferrum does not start instead of continuing with defaults.
Present in the code
Date: 20 October 2026
Not re-tested in this review.
Ferrum is written in Rust. Its own code (about 54,000 lines in 244 files) contains four unsafe sites in three files.
Present in the code
Date: 20 October 2026
Encryption uses the C library libsodium through sodiumoxide (in third_party/crypt4gh, not counted here). Rust rules out memory errors in Synaptic Four's own code where no unsafe is involved, and says nothing else about security.
Ferrum's own checks (formatting, lint, 282 tests, licence check) passed on 13 October 2026 at commit with Rust 1.91.1.
Tested
Date: 13 October 2026
An older state than v0.3.10. Not an independent run. Tests show only what they cover.
HelixTest is Synaptic Four's own testing tool for GA4GH interfaces. HelixTest has a check mode for Ferrum. A recorded run against a published Ferrum image is still outstanding. Profiles for other vendors' servers are in progress.
Present in the code
Date: 12 October 2026
A documented check against a published Ferrum release is still outstanding. This is not a certification. There is not yet a set of implementations by others.
Building four of the five programs that were checked gave identical checksums in two clean runs on the same platform.
Tested
Date: 11 October 2026
Not checked across platforms and not in continuous integration. The HelixTest release binaries did not match.
Ferrum is under the Apache licence 2.0. You may use it, change it and pass it on freely, including commercially.
Present in the code
Date: 14 November 2026
Not legal advice. The text of the licence file is what counts.
A separate Beacon for pathogens is decided, not built. The human-focused Beacon rejects the SARS-CoV-2 reference name NC_045512.2 with HTTP 400.
Tested
Date: 24 October 2026
This name was checked, not every pathogen reference. An organism name can still be queried on the human Beacon. The separate Beacon is not built. This is not a GA4GH certificate.