Original Summary

Whenever I throw together a new API or side project, I always end up wasting a couple of days on the same repetitive stuff: hashing keys, writing Redis rate limiters, setting up usage caps, and making sure random scripts don't hammer the database. I looked into using things like Unkey or Zuplo, but for small self-hosted projects, I really didn't want another external SaaS dependency or recurring bill in my request chain. On the flip side, running something like Keycloak just to manage bearer tokens is complete overkill. So I wrote Keygate: https://github.com/tabloy/keygate It's essentially a lightweight self-hostable service that sits between clients and your backend. It handles key generation, sha256 verification, rate limits, and request quotas so you don't have to clutter your actual app logic with auth plumbing. Works as a direct proxy or just an internal verification service. Still actively tweaking it and figuring out the best caching approach. If you manage your own APIs or microservices, take a look and let me know what you think, or what feels broken.   submitted by   /u/alanismex [link]   [comments]

  • 情报分类：商业与市场研究
  • 分类依据：内容涉及商业、投资或市场动态
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/9/26 12:16:25