I will review your llm gateway for cost, auth and quota risks

Z
zerokdevops
Z
zerokdevops
Sanghyeok Y

About this gig

Running LLM traffic through your own gateway, or about to? I review the design and tell you, in writing, what will hurt you in production.


I have designed and operated an in-house LLM gateway in production, and wrote a 32,000-word playbook on the topic.


What I look at:

- Auth: static provider keys, short-lived tokens, per-user attribution

- Quotas and budgets: per-team limits, alert ladders, what happens at 100%

- Cost: usage metering, missing usage blocks, cached tokens, reconciliation with the provider bill

- Streaming: idle timeouts, mid-stream disconnects, retries

- Tools / MCP access: who can call what, and how it is audited


What you get:

- A written report with findings ranked by risk

- For each finding: why it matters and the smallest fix

- Premium: a staged launch checklist mapped to your system


What I need from you:

- A diagram or short description of the request path

- Relevant config or code (secrets removed)

- Your providers, rough traffic and monthly budget


Written delivery only. Please message me before ordering if you are unsure which package fits.

Get to know Sanghyeok Y

Sanghyeok Y

DevOps engineer for LLM gateways and Kubernetes

  • FromSouth Korea
  • Member sinceOct 2026
  • Languages

    Korean, English
DevOps engineer with 9+ years in infrastructure, Kubernetes, GitOps and, lately, AI infrastructure. I have designed and run an in-house LLM gateway in production: auth with short-lived tokens, per-team quotas and budgets, cost metering and reconciliation, and MCP tool access. I wrote The AI Gateway Playbook, a 32,000-word guide on the same topic. I work in writing: you send your design, config or repo, and I send back a clear, prioritized review. Korean native, English for written work.