What is a FLNet Client?
A client is the self-hosted node a data holder operates in the FLNet network.
It is the place where local data is prepared, governed, and made available for discovery or analysis according to the rules you define. In other words: the client is how an institution joins the network without giving up operational control of its own data.
What a client is responsible for
A client typically handles four things:
- Hosting local metadata and data access logic
- Running connectors to import and normalize data
- Publishing enough information for network discovery
- Enforcing what external users and workflows are allowed to do
The client is not just a passive storage endpoint. It is the governance boundary between your local environment and the rest of the network.
What you can do with a client
With a client deployment, you can:
- describe your local schema using a shared data standard
- import datasets through connectors
- keep your site visible to the network for discovery
- participate in federated analysis when it is allowed
- manage users and permissions locally
When you need a client
You should deploy a client if:
- your organization owns data that should stay under local control
- you want to participate in FLNet as a data holder
- you need to define institution-specific access rules
- you want your data to remain discoverable over time
If you only need to use already available data and tools, start with Platform usage instead.
Operational expectations
Running a client usually means:
- keeping the system reachable on a stable host
- maintaining authentication and certificates
- defining user roles locally
- reviewing how connectors and access settings are configured
For federated discovery to work reliably, the client should ideally be available continuously.