Platform heat 1 · Quiet★ 0heat incomplete (no X)

Jevlar

An Apache-2.0 self-hosted Go gateway for System One decision-model APIs: one TOML file, client auth, multi-provider key failover, retries, and Prometheus metrics without a database or UI.

What it is

Boring reliability in front of decision APIs.

What it does: Authenticate callers once, pick a healthy System One provider/key, retry and meter usage.

Why it belongs in the showcase: Distinct self-hosted gateway shape for hosted Jev-style APIs.

Caveats: Ops-heavy; no policy brain.

Evidence

Public Apache-2.0 repo, created 2026-11-03, 0 stars as of 2026-11-04. README documents mise check, configs/minimal.toml, healthz/metrics, SIGHUP reload, and keyhash for inbound tokens.

Caveats

  • Gateway ops (keys, providers, TOML) are entirely on you
  • Does not itself implement product policy — only routes System One calls
  • Young repo; validate against your provider SLAs

Unofficial case page. Stars / list position observed for heat; do not treat heat as a quality SLA. Review the upstream README before you depend on it.