Skip to content
View vjsairam's full-sized avatar

Block or report vjsairam

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
vjsairam/README.md

Sai Ram

AI infrastructure and platform architect

I help engineering teams measure what each AI workload costs per successful task and compare the options against their quality and latency targets: a managed model API, their own GPUs, or a mix.

Work with me: a five-day AI workload cost assessment on one workload, ending in a written recommendation.

Measured work

Managed model API vs self-hosted vLLM on EKS vs a policy-routed hybrid, on the same frozen task sets. Results from the August 2026 runs (costs are inference-service cost per correct task, not full platform TCO):

  • Classification: the private 7B model was more accurate (94.3% vs 77.8% correct) and about 40 times cheaper per correct answer ($0.0000505 vs $0.00214). The managed run used a 64-token answer cap, and GPU cost covers only the benchmark request span.
  • Structured extraction: the managed premium model won on quality (99.9% vs 40.7%), so the quality requirement decides, not the token price.
  • Hybrid routing priced the blend in between: 88.9% correct at $0.00071 per correct task across mixed quality tiers.
  • Failure drills: a deleted vLLM pod recovered in 2m45s, and 150 of 150 requests hit by injected provider faults failed over with no client-visible errors.
  • Autoscaling with KEDA on two pre-provisioned GPU nodes: scale decision about 10s after load arrived; the second replica was ready after a 7m40s pod-plus-model cold start. Node provisioning was not measured.

Terraform upgrade analysis exposed as an MCP server, written in Go.

Open source

  • KEDA: merged removals of deprecated scaler settings for the 2.22 release (GCP Pub/Sub, Huawei Cloudeye), with the matching docs changes.

What I work on

  • Inference architecture: managed, private or hybrid, decided on cost per correct result
  • GPU and Kubernetes model serving: vLLM, KServe, autoscaling
  • Reliability and failure testing for AI services
  • AI FinOps: GPU utilisation, capacity planning, unit economics
  • Platform engineering: AWS, Terraform, observability, security

15+ years in infrastructure and platform engineering, including regulated environments. CKA and CKS certified.

Contact: sai@vjsairam.com · vjsairam.com

Pinned Loading

  1. ai-inference-cost-optimization ai-inference-cost-optimization Public

    Reproducible comparison of managed, self-hosted and hybrid LLM inference costs, quality, latency and reliability.

    Python

  2. inferaudit inferaudit Public

    Read-only review of how AI models are served on Kubernetes: startup timelines, reliability and access findings, in one HTML report.

    Go