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

> ## Agent Instructions
> The PyPI package is graphifyy, with two y's. The command is graphify.
> /graphify . is typed in an assistant chat, not in a shell.
> Use only commands, flags, and endpoints shown on these pages. Do not invent one.
> Choose the surface before you open a page. Local (Graphify Local) is the graphifyy package on the machine: the skill, the CLI, and the ten-tool MCP. Its pages are the Open Source tab (/open-source/) and the Graphify Local tab on each Integrations page. Graphify is the hosted workspace and https://api.graphify.com/mcp (Streamable HTTP, OAuth, no API key). Its pages are the Graphify tab (/platform/, /concepts/) and the Graphify (hosted) tab on each Integrations page. Prefer Graphify unless the user asks for a local or offline setup. Cookbooks (/cookbooks/) and /mcp/docs-search apply to both. Each page's source frontmatter records this as surface: local, cloud, or both. Buildkite is the CI integration.
> In llms.txt, tell the surface from the page path. Graphify: /platform/ and /concepts/. Local: /open-source/. Most /integrations/ pages cover both, with a Graphify (hosted) tab and a Graphify Local tab. Everything else applies to both.
> graphifyy release notes are published at https://github.com/Graphify-Labs/graphify/releases and https://graphify.com/changelog. The current package version is on PyPI (https://pypi.org/project/graphifyy/).
> The official site is https://graphify.com. These docs are https://docs.graphify.com.
> The local MCP server is the ten tools in the MCP tool reference and reads a graph on the machine. The hosted server is https://api.graphify.com/mcp (Streamable HTTP, OAuth, no API key). The JetBrains, ChatGPT, Codex, and Dots, and Vercel pages use the hosted server, not the ten-tool list. On pages with tabs, the Graphify (hosted) tab uses the hosted server and the Graphify Local tab uses the local skill or the ten-tool server.
> Read https://docs.graphify.com/llms.txt, then open one page's .md link. Use https://docs.graphify.com/llms-full.txt only when one page is not enough.

# Run Graphify locally

> Run Graphify entirely on your machine: a code-only workflow, or semantic extraction with a local model backend such as Ollama.

> [!TIP]
>
> Don't want to install anything? Graphify, the hosted product at app.graphify.com, indexes your GitHub repositories in the browser. We run it for you, so there's nothing to deploy. Start with the [Cloud quickstart](https://docs.graphify.com/platform/quickstart.md).

The open-source engine stores its graph on your filesystem. It does not require a Graphify account.

## Code-only workflow

```bash theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}}
uv tool install graphifyy
graphify extract . --code-only
graphify cluster-only . --no-label
graphify export html
graphify query "entry points"
```

`--code-only` is an `extract` flag. It skips semantic document and media extraction. It is not a flag you need to pass to the assistant skill.

## Include documents with a local model

Install the Ollama extra and run an Ollama model suitable for your content. Select an installed model in `OLLAMA_MODEL`, then:

```bash theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}}
uv tool install "graphifyy[ollama]"
graphify extract ./docs --backend ollama
```

Graphify defaults to the local Ollama endpoint. If you override the endpoint to a remote host, that changes where the content is sent. Large documents may need a smaller `--token-budget` or lower `--max-concurrency`.

## Understand the boundaries

* Local structural parsing does not send code to a model.
* A cloud coding assistant still controls where its own prompts and context go.
* A headless semantic backend receives the documents or media you ask it to process.
* PR commands contact GitHub, and model-assisted CLI triage can call your configured provider.
* Query logging is off by default in the current implementation; [configuration](https://docs.graphify.com/open-source/configuration/graphifyrc.md) describes the opt-in controls.

The generated graph can contain source text, labels, paths, and document concepts. Keep it in a location appropriate for that source material.

## Next steps

> **[Try it in Graphify](https://docs.graphify.com/platform/quickstart.md)**
>
> We build and host the graph for you. Start with a 14-day Pro trial, then keep up to 3 repositories on Free. No card required.

> **[Extract without an IDE](https://docs.graphify.com/open-source/features/headless-extraction.md)**
>
> Build graphs in scripts and CI.

> **[Ask better graph questions](https://docs.graphify.com/open-source/features/querying.md)**
>
> Use query, path, and explain.

[PreviousBuild and explore a small graph](https://docs.graphify.com/open-source/cli-quickstart.md)
[NextExtract without an IDE](https://docs.graphify.com/open-source/features/headless-extraction.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.