Skip to main content

What FLNet is good for

FLNet is useful when teams need more than a single upload-and-run application. It is designed for cases where data stays distributed, governance matters, and analysis must remain reproducible.

Solution 1: Join an existing federated network​

If a FLNet deployment already exists, you can join it as a data holder and make your datasets discoverable without handing over raw data by default.

Typical outcomes:

  • others can discover that your site has relevant data
  • metadata can be searched centrally
  • access rules still remain under your control
  • approved federated workflows can run without flattening everything into one shared database

Best fit for:

  • hospitals
  • research institutes
  • consortia with multiple independent partners

Solution 2: Use the platform for governed analysis​

If you are a researcher or analyst, FLNet gives you a structured way to:

  • find data relevant to a question
  • assemble a project around that question
  • run tools or workflows with explicit parameters
  • review outputs, metrics, and generated artifacts

This is especially useful when you need a repeatable workflow instead of one-off scripts or manual coordination.

Solution 3: Operate your own deployment​

If your organization needs stronger operational control, you can deploy your own FLNet-based environment.

Reasons to do this include:

  • internal governance requirements
  • custom authentication and networking
  • local control over runtime resources
  • institution-specific tool catalogs or integrations

Solution 4: Publish tools for others to use​

FLNet is not only a place to consume analysis. It is also a way to package analysis logic so other users can run it consistently.

You can build tools for:

  • data harmonization and transformation
  • centralized analysis on uploaded data
  • federated analysis across multiple data holders
  • model training, evaluation, and reporting

That reduces the amount of custom frontend and backend work needed to make a scientific method usable by others.

Why teams choose this model​

Compared with a conventional central data platform, FLNet and FLNet aim to offer a better balance between:

  • discoverability
  • local control
  • reproducibility
  • operational governance

Compared with purely manual collaboration, they reduce the amount of bespoke coordination needed to make multi-party analysis actually run.

Where to go next​