[{"data":1,"prerenderedAt":27},["ShallowReactive",2],{"tag-list-en-platform-engineering":3},[4,17],{"title":5,"description":6,"tags":7,"path":14,"date":15,"img":16},"Giving Your Teams a Real AI Budget with LiteLLM","A hands-on guide to putting a gateway between your people and the model vendors, so that every call is attributed to a named person and a team, every team has a ceiling that resets on a schedule, a daily bound contains the runaway agent, and the finance team finally gets a per team breakdown. Covers deployment with Docker and Postgres, teams and keys, stacked budget windows, rate limits, model tiering, request tags for chargeback, PII guardrails, and the day two work nobody warns you about.",[8,9,10,11,12,13],"LiteLLM","FinOps","LLM-Gateway","Budgets","Observability","Platform-Engineering","\u002Fai\u002Fai-budget-with-litellm","2026-08-30","https:\u002F\u002Fres.cloudinary.com\u002Fdpdwhd6ka\u002Fimage\u002Fupload\u002Ff_auto,q_auto\u002Fv1\u002FBlog\u002Fimages\u002Fhbcudyxllyjvbkjxvs7g",{"title":18,"description":19,"tags":20,"path":25,"date":26,"img":16},"A Reference Architecture for a Sovereign Government Cloud","The two previous articles showed where Togolese law and Kubernetes fail to meet, then why multi-cloud does not answer a jurisdictional question. This one proposes what to build: a reference architecture for a sovereign government cloud in the WAEMU context. Requirements derived from the legal texts, layer-by-layer design choices with their justifications, an operating model, stated limits, and an honest comparison with the alternatives. An architecture document, not a tutorial.",[21,22,23,24,13],"Sovereignty","Kubernetes","Reference-Architecture","Togo","\u002Fkubernetes\u002Fsovereign-govcloud-reference-architecture","2026-08-15",1788067438086]