Manish Gautam
Co-founder, Asama AI
Co-founder of Asama, the AI infrastructure engineer for teams that run their own servers. A mechanical engineer and statistics and physics enthusiast turned infrastructure reliability analyst, he works on Asama's detection theory and wrote Determinism, Probability, and the Limits of Observability.
13 posts
-
Asama vs NVIDIA Minerva: a component-by-component comparison for GPU and server fleets
NVIDIA Minerva 1.0.1 scored against Asama, an AI infrastructure engineer, on 13 components from NVIDIA's docs: where Minerva fits and where an alternative does.
-
How Asama Investigates: parallel hypothesis trajectories for AI root cause analysis
How Asama, an AI infrastructure engineer, investigates: one agent per hypothesis, all running in parallel, verified into an evidenced root cause.
-
Why Asama Is Different: an AI infrastructure engineer built on infrastructure state
What it takes to detect, investigate and remediate infrastructure issues on a large fleet, why stale data breaks it, and why Asama runs on infrastructure state.
-
Comparison matrix v2.0: how to compare any tool with Asama
How to score any infrastructure tool against Asama on Infrastructure State, detection and remediation: the L0 to L4 ladders, the rules and the demo questions.
-
Normal Is a Moving Target: four conditions for a valid anomaly score
Every anomaly score compares a reading with a baseline. Four conditions decide whether it holds: signal identity, stationarity, peer validity and observer bias.
-
Determinism, Probability, and the Limits of Observability: what the residual says about a fault
Every fault model is some version of y = mx + c + ε. What the residual's shape says about a fault, where chaos caps prediction, and why ε never reaches zero.
-
The maintenance queue is a CapEx problem: what idle servers cost while they wait (Problem Scope 5/5)
Servers in the maintenance queue keep depreciating while they wait. Worked arithmetic for a 1,000-server fleet, and the share of the queue a digital fix clears.
-
Your automation has an expiry date: how playbooks go stale as the fleet changes (Problem Scope 4/5)
Why automation written for last year's hardware misapplies fixes on today's fleet, and how to plan each fix from the node's actual infrastructure state.
-
The tribal knowledge tax: what walks out when your senior engineers leave (Problem Scope 3/5)
Why a pinned BIOS setting or held-back firmware version often lives in one engineer's head, and what that costs in investigation time and deferred maintenance.
-
Configuration drift is the silent killer: the settings nobody tracks (Problem Scope 2/5)
Configuration drift hides in the BIOS, firmware and kernel settings no one told config management to check. Why no alert fires, and how to see it on every node.
-
Uptime is not reliability: the gray failures green dashboards miss (Problem Scope 1/5)
A server can pass every health check and still run below spec. Why uptime misses gray failure, and the three properties that make infrastructure reliable.
-
Unpopular opinion: build the foundation first, not what customers ask for
Each vendor's tools stop at its own hardware, and most fleets mix vendors. Why we built one model of every server's infrastructure state before any feature.
-
How we named Asama: Sanskrit for "without an equal"
Asama (असम) is Sanskrit for "that which does not have an equal": why we chose it over Orca and Raven for the AI infrastructure engineer we build.