> For the complete documentation index, see [llms.txt](https://docs.nfh.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nfh.global/build/creating-a-network.md).

# Creating a network

The operator track for standing up an open network on NFH fabric — environment, participant onboarding, policies, and building consumer and provider nodes.

This is the hands-on track for a **Network Facilitator Organisation (NFO)** standing up an open network on NFH fabric, and for **Network Participants (NPs)** joining one. It walks from a blank environment through onboarding, policy, and building the nodes that transact.

{% hint style="info" %}
These guides use the **Beckn Protocol** (the wire spec keeps its name) over NFH fabric services — [REGISTR](/product-documentation/products/registr.md) / [DeDi](https://docs.nfh.global/dedi) for identity, [Catalog Publishing and Discovery](/build/creating-a-network/catalog-publishing-and-discovery.md) + [DISCOVR](/product-documentation/products/discovr.md) for catalogs and discovery, and [ONIX](/product-documentation/products/onix.md) for the protocol adapter.
{% endhint %}

## The path

{% stepper %}
{% step %}

### Set up the network environment

The infrastructure and services an NFO stands up first. → [Setting up the network environment](/build/creating-a-network/environment.md)
{% endstep %}

{% step %}

### Onboard network participants

Register identities, keys, and callback URLs in DeDi. → [Onboarding network participants](/build/creating-a-network/onboarding-participants.md)
{% endstep %}

{% step %}

### Publish and discover catalogs

Self-host and self-sign a catalog, and see how a Discovery Service crawls and verifies it. → [Catalog Publishing and Discovery](/build/creating-a-network/catalog-publishing-and-discovery.md)
{% endstep %}

{% step %}

### Configure network policies

Express the network's rules. → [Configuring network policies](/build/creating-a-network/network-policies.md) — the [network manifest](/build/creating-a-network/network-policies/network-manifest.md), [Rego policy artifacts](/build/creating-a-network/network-policies/rego-policies.md), and [signing a file](/build/creating-a-network/network-policies/signing-files.md).
{% endstep %}

{% step %}

### Build the nodes that transact

Stand up the consumer (buyer-side) and provider (seller-side) applications using [ONIX](/product-documentation/products/onix.md) as the protocol adapter, then run the [Getting started with NFH fabric](/build/getting-started-with-fabric.md) walkthrough end-to-end.
{% endstep %}
{% endstepper %}

{% hint style="success" %}
**Just want to try NFH fabric first?** See [Getting started with NFH fabric](/build/getting-started-with-fabric.md) for a guided, runnable walkthrough before standing up a full network.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nfh.global/build/creating-a-network.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.