Tag: cloud run

Why a $1.05 Cloud Run L4 hour can be cheaper or more expensive than hosted inference depending on utilization, throughput, fallback rate, and accepted business outcomes.

Reader outcome: Built a reproducible cost model for comparing Cloud Run GPU capacity with token-priced APIs using active hours, workload shape, fallback, and accepted-result economics.

A production-oriented Cloud Run and vLLM design that keeps GPT-OSS private, separates routing from inference, and makes model loading, readiness, concurrency, and rollback explicit.

Reader outcome: Produced a deployable service contract for private OpenAI-compatible inference with IAM authentication, pinned artifacts, measured concurrency, and a scale-to-zero operating path.

Why adding a private open model beside hosted APIs fails unless routing, fallback, evaluation, and authority are designed as one production contract.

Reader outcome: Defined a hybrid inference contract that routes bounded work to a private model while preserving hosted-model fallbacks, deterministic validation, and human review.

When a SaaS product should graduate from a flexible Python-first backend into Go, gRPC, Cloud Run, and Google Cloud service boundaries.

Reader outcome: Mapped a Go and gRPC adoption path for SaaS teams that need stronger service contracts, concurrency, latency discipline, and Google Cloud operations without premature rewrites.

A practical guide to running MCP servers locally, choosing affordable clients, and deploying private open models with Cloud Run, Ollama, and Open WebUI.

Reader outcome: Separated local agent tool access from private model serving, then defined a safer setup for MCP clients, local servers, and Cloud Run GPU sidecars.

A practical deployment guide for running Ollama behind Open WebUI on Cloud Run GPUs without mixing service specs, model storage modes, sidecar startup order, or auth assumptions.

Reader outcome: Clarified Cloud Run GPU sidecar deployment choices so model storage, service YAML, startup ordering, authentication, and billing constraints are explicit before launch.