Research data sits in many places: in institutes, clinics and sequencing centres, in different systems and under different access rules.
For joint projects, partners should be able to find and use this data. Even so, not every institution wants to, or may, transfer its data to a central platform.
What Ferrum changes
Partners find, through the standard interfaces, which datasets exist, without seeing the data itself.
You decide each request. Ferrum does not decide it.
Accesses and downloads are kept in a chained log. A later change can be seen there.
The files stay on the storage you set. Ferrum does not copy them to a Synaptic Four service.
Where the data sits: on the storage you set, by default on your own computer.
What goes outside: Ferrum asks a time server for the time, as a check. No research data is sent with that. You can replace the time server.
The operator sets any further counterpart systems.
If Synaptic Four were no longer there: the source, the installation guide and the operations handbook are public.
An example
A research institute wants to offer selected datasets for a joint project with another institution. The scenario is an example, not a reference project.
The institute runs Ferrum.
The files sit on the storage the institute sets. Ferrum does not copy them to a service of Synaptic Four.
The partner finds the dataset.
Through the standard interfaces, the partner can ask which datasets and variants are present, without seeing the data itself.
He makes a request.
It is for access to one particular dataset.
The institute decides.
Technically, the external decision service that the institute runs checks this. The grant comes from your institute, not from Ferrum.
Ferrum delivers the file.
Ferrum allows access to a file when the sign-in carries a release for that exact dataset. Access and downloads are kept in a chained log. A later change can be seen in it.
This is how the sequence is built. It has not been run through from start to finish.
When Ferrum fits
Ferrum fits when …
Ferrum does not fit when …
Ferrum fits when several institutions want to exchange research data through international standard interfaces on their own infrastructure.
You are looking for a certified secure processing environment or a ready-made approval service.
You want to start small, on one computer.
You already need operation around the clock.
What you need
For a single computer there is the smaller form, without its own database server.
For an institution that runs servers there is the full form, with a database, object storage and a sign-in service. The detailed comparison is in the technical profile.
A person who takes on operation: servers, backups, users.
A sign-in system and an approval service, when partners are to request access.
To start: test data or sample data.
Synaptic Four measured the path from the guide to the first query once: about 25 minutes, including building the images.
The installation guide and the operations handbook are public in the source.
Setup and training belong to the pilot.
Ferrum itself is free (Apache 2.0). Only services are paid for:
€480
Start, half a day remotely
€1,800
Assessment before use
€10,000
Pilot, 90 days at one site
If the first milestone is missing after 30 days, the pilot ends, and you pay €3,000.
How the assessment and the pilot are credited
Up to €1,800 is credited to the pilot if the agreement follows within 60 days; you then pay €8,200.
The pilot is credited in full against the first year of Ferrum Professional; you then pay €5,000.
Together €15,000, if the assessment is credited in full.
€15,000
Ferrum Professional, per year
€7,500
Research and non-profits, per year
A named contact and response times under the contract.
Updates on dates you agree.
Documents for the Cyber Resilience Act for each version you run. They name the bill of materials, notes on vulnerabilities, and support for your own documentation.
Advance notice of security flaws before they become public, where responsible disclosure allows it.
Priority for fixes that affect your operation.
Not included are round-the-clock operation, certification and legal advice.