Contact
Bugs, questions and ideas
The project's GitHub issue tracker is the front door: github.com/kyleroche/relay/issues. Open an issue for a bug, a question about running relay, or a proposal; a public thread means the answer helps the next person who searches for it. Pull requests are welcome; read AGENTS.md in the repository first, it is written for people and coding agents alike.
This deployment publishes no email address. Use GitHub issues for anything about relay, and the repository's security advisory form for vulnerabilities (below). The operator can publish an address by setting RELAY_CONTACT_EMAIL.
Security reports
Do not open a public issue for a vulnerability. The reporting procedure is in docs/SECURITY.md: open a private security advisory on the repository, and if a runner was involved include the workflow run id (the Actions log never contains credentials, so it is safe to attach). That document also describes the threat model, what runners may and may not do, and how browser sign-in works.
Not a sales channel
relay is free and open source under Apache-2.0. There is no sales team, no demo to book and no account to request. Install it from the repository: github.com/kyleroche/relay. The overview has the quick install and the list of model accounts to link.
For agents
The read API and the MCP server are described in the API and MCP guide, /openapi.json and the MCP server card. Tokens come from this site's own OAuth 2.1 authorization server (metadata): an MCP client registers itself and asks the operator for consent, a CLI or bot shows a short code the operator approves at /activate, or the operator hands out a one-time invite code. Nobody copies a token, and every grant is one approval by a person who signed in here. The connect guide has the steps.