FL-Net
The federated network model: multiple data holders keep control over local data while participating in shared discovery, analysis, and governed workflows.
Collaboration for real-world scientific work
FLNet
Self-hosted clientsGoverned discoveryReproducible tools
At a glance
One stack, three roles
Data holdersDeploy clients, map data, and control access.
ResearchersFind cohorts, run analyses, and review governed results.
DevelopersPackage scientific workflows as reusable tools.
Know the pieces
The documentation is easier to navigate when the terminology is explicit. These are the building blocks used throughout the site.
FLNet
The product experience built on top of that model: a user-facing platform for finding data, running tools, and collaborating without rebuilding infrastructure from scratch.
Client Deployments
Self-hosted nodes operated by data holders. They expose metadata, enforce access rules, run connectors, and participate in federated analysis when permitted.
Choose your path
Most users do not need the whole platform at once. Start with the path that matches your responsibility and move outward from there.
Join as a data holder
Deploy a client, describe your schema, ingest data, and decide what the network is allowed to do with it.
Open sectionUse the platform
Search the network, create analysis projects, run tools, and interpret results in a governed environment.
Open sectionBuild and publish tools
Develop reproducible apps for transformation, centralized analysis, or federated workflows.
Open sectionTypical workflow
FL-Net is designed so discovery, governance, execution, and interpretation follow a consistent sequence instead of turning into manual coordination.
01
Describe and publish metadata
Data holders model their local schema and expose only the information needed for discovery and governance.
02
Discover relevant data and tools
Researchers search the network, evaluate available tools, and assemble a project that matches their question.
03
Run governed analysis
Execution happens through reproducible tools and explicit permissions rather than ad hoc data movement.
04
Review outputs and iterate
Results, logs, and artifacts stay traceable, so teams can refine parameters and compare outcomes.
Documentation shortcuts
These are the pages most people need first when they are trying to orient themselves or get real work done quickly.
Get Started
Choose the right path based on your role and deployment model.
Network Architecture
Understand how the platform, clients, and runtime boundaries fit together.
Find Data
Learn how discovery works without exposing raw data by default.
Deploy a Client
Set up a self-hosted participant that can join the federated network.
Create a Federated Project
Move from discovery to a governed multi-party analysis.
User Guide
Navigate the interface, run apps, and interpret results with confidence.