Onboarding on the NFH fabric

Join the NFH fabric as a Network Facilitator Organisation (NFO) or a Network Participant (NP) — on the hosted dedi.global solution or by publishing files on your own domain.

Your role

• Network Facilitator Organisation (NFO) — you operate a network. You onboard the network onto the NFH fabric and keep a reference registry of the NPs that belong to it.
• Network Participant (NP) — you join the NFH fabric by publishing your own subscriber details (endpoint and keys). An NFO includes you in its network by adding a reference to them. You can also onboard without being tied to any NFO, and be added to networks later.

Your path — where you publish:

• Path 1 — Hosted: on dedi.global. You create your registries there; nothing to host yourself.
• Path 2 — File-based: on a domain you control, as DeDi files following the DeDi protocol specification.

Pick the guide for your situation:

Role	Path 1 — Hosted (dedi.global)	Path 2 — File-based (own domain)
NFO	Set up your network and add NPs	Onboard your network
NP	Register your subscriber details	Onboard by publishing your records

The paths mix freely across a network: an NFO can run a file-based network and still accept NPs that are on dedi.global, and vice versa.

1. An entity (NFO or NP) cannot use the hosted (dedi.global) path and the file-based path at the same time for any write operations. Each entity writes on exactly one path.
2. Registry names and file locations in these guides are suggested conventions, not requirements. The hard requirements are that record names are unique within a registry, and that the published URLs (in the index file and in reference records) are correct. A record's name can be reused as the key ID in the publisher's ONIX configuration.

See a complete network laid out end to end in the worked example. To change path later, see Switching onboarding paths; to leave, see Unpublishing your registries.