Skip to main content

Welcome

FLNet is the product experience built on top of FL-Net, a federated network model for discovery, governed collaboration, and reproducible scientific workflows.

In practical terms, that means:

  • Data holders can keep data local in their own client deployments.
  • Researchers and analysts can discover relevant cohorts and run approved analyses.
  • Developers can package transformations, models, and workflows as reusable tools.

FL-Net and PoSyMed: what is the difference?​

The documentation uses both names on purpose:

  • FL-Net refers to the underlying federated architecture and operating model.
  • PoSyMed refers to the user-facing product or deployment you use in practice.

If you are using the hosted platform, you mostly interact with FLNet. If you are deploying your own node, integrating tools, or reasoning about trust boundaries, you are also dealing with FL-Net directly.

What this documentation covers​

This site is organized around the three main ways people use the system:

1. Joining the network as a data holder​

Use these docs if you need to:

  • deploy a client
  • describe your data via a shared standard
  • import local datasets
  • decide what external analysis is allowed

Start here: Client deployment and usage

2. Using the platform for discovery and analysis​

Use these docs if you need to:

  • search the network for relevant data
  • create analysis projects
  • run tools and review outputs
  • understand the user interface and workflow model

Start here: Platform usage

3. Building or extending tools​

Use these docs if you need to:

  • package your scientific method as a reproducible app
  • define inputs, outputs, and parameters
  • integrate your tool into the platform runtime

Start here: Tool development

What to expect from the platform​

FLNet is designed for environments where governance matters as much as usability. The platform aims to make complex analysis possible without requiring users to manually coordinate files, ad hoc scripts, and email approvals for every step.

You should expect:

  • explicit separation between metadata discovery and raw data access
  • traceable execution through tools and workflows
  • permission boundaries that can be enforced by data holders
  • a path from simple interactive use to self-hosted deployments