> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nofire.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Connect NOFire to your repositories — choose the option that fits your network

NOFire uses your GitHub repositories to connect code changes with infrastructure behavior. The right setup depends on where your GitHub instance lives and how you want NOFire to access your code.

|                           | [GitHub App](/git/github-app)                     | [Edge Proxy](/git/github-edge-proxy)         |
| ------------------------- | ------------------------------------------------- | -------------------------------------------- |
| How NOFire accesses code  | GitHub API, on demand                             | Local clone in your cluster                  |
| GitHub reachability       | Internet-accessible or self-hosted via Edge Proxy | Must be reachable from your cluster          |
| Auth mechanism            | GitHub App (OAuth or App credentials)             | GitHub App or Personal Access Token          |
| Code outside your cluster | Snippets only                                     | Snippets only                                |
| Infrastructure needed     | None (cloud) or Edge (self-hosted)                | Edge in your cluster                         |
| Best for                  | Fast onboarding                                   | Private networks, compliance, data residency |

## Next Steps

* For cloud or self-hosted GitHub: [GitHub App](/git/github-app)
* For in-cluster cloning: [Edge Proxy](/git/github-edge-proxy)

Any questions? Contact us at [support@nofire.ai](mailto:support@nofire.ai).