Who runs OpenNodes, and what it keeps

Contact

• Questions, bugs, ideas: GitHub issues.
• Operators — claiming or removing a listing, probe keys: operators@opennodes.io.
• Privacy requests: privacy@opennodes.io.
• Security reports: security@opennodes.io — please don't open a public issue. See the security policy and security.txt.

Where it runs

• opennodes.io — static pages served by Cloudflare.
• registry.opennodes.io — the reference registry on a Hetzner Cloud server in Nuremberg, Germany (PostgreSQL, daily backups).
• demo-node.opennodes.io — the project's own small reference node (a 1B model on the same server). Other listed nodes are run by their operators, not by OpenNodes.

What the registry stores

• Node data: Node Cards and their revisions, probe results, measured performance, and state history — all public by design.
• Imported catalog data from public sources (OpenRouter, Hugging Face, models.dev, the Ollama library), marked unverified. Operators can claim a listing or ask for it to be removed.
• Probe keys that operators choose to provide for card-only listings: stored on the server, sent only to that operator's own endpoints for checks, never shown through any page or API.
• Operational logs: the web server records IP addresses and requested URLs for operation and abuse prevention, kept short-term.

What it does not see

• Your prompts and answers. The chat, the playground, the CLI, the gateway and the Ollama router send them straight from your device to the node you chose. The registry is out of the data path.
• Your API keys. Keys you type in the web app stay in your browser's local storage; the gateway and router keep them on your machine.
• Accounts or tracking. There are no accounts, no advertising, and no third-party analytics.

One exception: the catalog's "Ask the advisor" box sends the task text you type to the registry to compute a recommendation; it is not stored. The MCP server and the router extract features locally and send only those.

What the badges mean

Tiers and measurements report what the registry's automated probes observed — identity, context, throughput, availability — at the time of measurement. They are evidence, not guarantees: nodes are operated by third parties under their own terms, and OpenNodes is not a party to your use of them.