feat: add byok-relay to Development Tools#153
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request adds the byok-relay project to the README, describing it as a self-hosted relay for user-supplied AI API keys. The review feedback recommends removing an extra blank line for consistency, changing the term 'register' to 'configure' for clarity, and ensuring the Chinese version of the README is also updated.
|
|
||
| - [byok-relay](https://github.com/avikalpg/byok-relay) |
There was a problem hiding this comment.
There is an extra blank line introduced before the new entry. Removing it will maintain consistency with the spacing used for other items in this section.
| - [byok-relay](https://github.com/avikalpg/byok-relay) | |
| - [byok-relay](https://github.com/avikalpg/byok-relay) |
|
|
||
| - [byok-relay](https://github.com/avikalpg/byok-relay) | ||
|
|
||
| A self-hosted (or managed) relay that lets frontend apps use user-supplied AI API keys — no CORS issues, no exposed keys, no inference bill for the developer. Users register their own Anthropic, OpenAI, Google, Groq, OpenRouter, or Mistral key once; the relay stores it encrypted (AES-256-GCM) and proxies all subsequent requests server-side with SSE streaming support. |
There was a problem hiding this comment.
This repository is bilingual. Please add the corresponding entry to README.cn.md to keep both versions in sync. A suggested translation is provided below. Additionally, 'configure' is more appropriate than 'register' for API keys in this context.
Chinese Translation:
-
一个自托管（或托管）的中继，允许前端应用使用用户提供的 AI API 密钥 —— 无 CORS 问题，无密钥泄露，开发者无需承担推理费用。用户只需配置一次其 Anthropic、OpenAI、Google、Groq、OpenRouter 或 Mistral 密钥；中继将其加密存储 (AES-256-GCM)，并支持 SSE 流式传输，在服务端代理所有后续请求。
| A self-hosted (or managed) relay that lets frontend apps use user-supplied AI API keys — no CORS issues, no exposed keys, no inference bill for the developer. Users register their own Anthropic, OpenAI, Google, Groq, OpenRouter, or Mistral key once; the relay stores it encrypted (AES-256-GCM) and proxies all subsequent requests server-side with SSE streaming support. | |
| A self-hosted (or managed) relay that lets frontend apps use user-supplied AI API keys — no CORS issues, no exposed keys, no inference bill for the developer. Users configure their own Anthropic, OpenAI, Google, Groq, OpenRouter, or Mistral key once; the relay stores it encrypted (AES-256-GCM) and proxies all subsequent requests server-side with SSE streaming support. |
…igure, add README.cn.md entry
1 participant
byok-relay — BYOK relay for frontend apps
byok-relay is a self-hosted (or managed) relay that lets frontend apps use user-supplied AI API keys — exactly the pattern this list curates.
Fits this list's criteria:
Why it's different from a simple proxy: Users own their key — it never leaves the relay in plaintext, and the frontend only ever holds a short-lived relay token (not the real API key). This solves the trust problem of BYOK for browser-only apps.