FL-Net
The federated network software behind Federated Learning Net: lets multiple data holders keep control over local data while participating in shared discovery, analysis, and governed workflows.
The documentation is easier to navigate when the terminology is explicit. These are the building blocks used throughout the site.
The federated network software behind Federated Learning Net: lets multiple data holders keep control over local data while participating in shared discovery, analysis, and governed workflows.
The deployed instance of FL-Net: a ready-to-use platform for finding data, running tools, and collaborating without building infrastructure from scratch.
Self-hosted nodes operated by data holders which make up the Federated Learning Net. They enforce access rules, run no-code data onboarding, and participate in federated analysis.
Orient yourself with the pages above, or go straight to the path that matches your role.
Understand what FL-Net and Federated Learning Net are and how the pieces fit together.
Open sectionSee why teams choose FL-Net over other federated learning frameworks.
Open sectionChoose the right path based on your role and deployment model.
Open sectionUnderstand how the platform, clients, and runtime boundaries fit together.
Open sectionSet up a self-hosted client, either on your own infrastructure or in a cloud environment.
Open sectionDescribe your schema, ingest data through connectors, and decide what the network is allowed to do with it.
Open sectionSearch the network, create analysis projects, run tools, and interpret results in a governed environment.
Open sectionDevelop reproducible ETL, federated learning, and inference Tools for others to run.
Open sectionRun your own platform and coordinate the clients that connect to it.
Open sectionHelp build the underlying software: the Client, Platform, and Schema system itself.
Open sectionFL-Net is designed so discovery, governance, execution, and interpretation follow a consistent sequence instead of turning into manual coordination.
Data holders model their local schema and expose only the information needed for discovery and governance.
Data Scientists search the network, evaluate available tools, and assemble a project that matches their question.
Execution happens through reproducible tools and explicit permissions rather than ad hoc data movement.
Results, logs, and artifacts stay traceable, so teams can refine parameters and compare outcomes.