RelayGuard v0.2.0 public preview: scoped keys and lifetime data budgets

[kwakhyun]

RelayGuard v0.2.0 is available as an MIT-licensed public preview. It gives an HTTP integration a scoped, expiring key instead of the provider's Bearer token.

The narrow use case is an internal job or collaborator that needs a few JSON/text endpoints and a bounded amount of returned data. The gateway buffers the entire response, checks request and response-byte budgets in SQLite, and withholds an over-budget response in full. v0.2.0 adds persistent lifetime caps, offline policy checks, storage readiness and a redesigned Korean console.

Try it: release and executable packages · English quickstart. The synthetic CRM demo needs no provider account or customer data. The public image is ghcr.io/kwakhyun/relayguard:0.2.0 for amd64 and arm64.

Validation includes 290 Python tests, 10 console state regressions, 12 live HTTP demo scenarios plus 8 lifetime assertions, installed-wheel checks, and anonymous image pull/run on both architectures. This is not an independent security audit or a performance claim.

The scope is deliberately small: one upstream/account, bounded JSON/text, no streaming, OAuth refresh, object-level authorization or distributed quotas. Allowed data can still leave within its budget, and clients with the original provider token can bypass the gateway. Threat model. An existing gateway may fit your needs better.

Feedback from a non-sensitive read-only integration would help answer:

1. Can you run the demo and express the access policy from the docs alone?
2. Which protocol or deployment constraint prevents adoption?
3. Does a lifetime byte cap solve a problem your current gateway does not?

Use synthetic examples in public replies. Report vulnerabilities through SECURITY.md, without posting real credentials or customer data.

---

한국어: 원본 API 토큰 대신 범위와 데이터 한도가 있는 키를 발급하는 도구로 v0.2.0을 공개합니다. Codex를 활용해 구현하고 회귀 검사와 실제 HTTP 실행을 검증했습니다. 외부 사용 사례와 독립 보안 감사는 아직 없습니다.

한국어 시작 안내와 기존 도구와의 비교를 공개했습니다. 기존 게이트웨이를 이미 운영한다면 별도 도구를 추가할 이점이 작을 수 있습니다. 작은 연동에서 총 조회량을 정하고 키를 폐기하는 흐름이 실제로 도움이 되는지 의견을 받고 싶습니다.

업그레이드 시에는 모든 구버전 워커를 중지하고 DB를 백업하세요. 구버전과 신버전을 같은 DB에 연결하지 마세요. 업그레이드 안내.