Get started by role
Most confusion at the beginning comes from mixing up three very different jobs:
- operating a client
- using the platform
- building tools
Start with the section that matches what you are actually trying to do.
I want to understand the architecture first
Read Understanding the network architecture if you need to decide:
- whether the hosted platform is enough for your use case
- whether you need your own client deployment
- how FLNet separates discovery, governance, and execution
I am a data holder and want to join the network
Read Client deployment and usage.
That path covers:
- deploying a client
- defining a data standard
- importing local data through connectors
- configuring what federated analysis is allowed to do
This is the right starting point for hospitals, institutes, or consortia that want to participate while keeping operational control over their own data.
I want to search data and run analysis
Read Platform usage.
That path covers:
- finding relevant datasets across the network
- creating a project around a concrete analysis question
- running tools in a governed way
- reviewing outputs and iterating on parameters
This is the right starting point for researchers, analysts, and project leads.
I want to create or integrate tools
Read Tool development.
That path covers:
- the runtime model for tools
- how to define inputs, outputs, and parameters
- how to package a reproducible analysis workflow
- what changes between local development and production execution
This is the right starting point for developers and research engineers.
Suggested reading order
If you want the shortest useful path through the docs:
- Welcome
- Solutions
- Network architecture
- One of:
Common decision rule
If your main question is "How do I make my data available safely?", start with the client docs.
If your main question is "How do I use the available data and tools?", start with the platform docs.
If your main question is "How do I extend the system?", start with the developer docs.