Sumeet Ghosh
Co-founder, Asama AI
Co-founder and CEO of Asama, the AI infrastructure engineer for teams that run their own servers. He was Head of Infrastructure at Flipkart.
10 posts
-
Asama vs LogicMonitor + Edwin AI: a component-by-component comparison for on-prem server fleets
LogicMonitor Signature with Edwin AI, scored head to head with Asama on 13 components of Infrastructure State, Detection and Remediation, every anchor shown.
-
Why L3 Stalls: AI root cause analysis stops where your monitoring data does
AI root cause analysis answers the first of five whys and stalls at L3. The chain breaks at breadth, depth, normalisation, topology and history, not reasoning.
-
Asama vs Zabbix + Claude: a component-by-component comparison for on-prem server fleets
Zabbix 7.0 LTS wired to Claude over MCP, scored head to head with Asama on 13 components of Infrastructure State, Detection and Remediation, every anchor shown.
-
Asama vs Zabbix: a component-by-component comparison for on-prem server fleets
Zabbix 7.0 LTS and Asama scored head to head on 13 components of Infrastructure State, Detection and Remediation, every anchor shown so you can re-score.
-
The Four Levels of Detection Maturity: L1 to L4, from threshold alerts to root cause
A detection maturity model, L1 to L4: how much of symptom detection, correlation and root cause your platform does, and how much is left to your engineers.
-
Trust Is the Real Interface: what makes an AI root cause analysis checkable
An AI root cause analysis earns trust when you can check it: findings tied to evidence, confidence stated with its gaps, and overrides that change the answer.
-
The Automation Boundary: when agentic remediation should run on its own, and when it should ask
When should agentic remediation run without a person? Suggest, orchestrate and autonomous modes, and three tests: reversibility, determinism, blast radius.
-
What happens when the loop stops: why remediation is the mission (3/3)
Faster detection does not end the firefighting loop. One BIOS incident, told two ways, shows why the fix needs agentic remediation: planned, approved, verified.
-
Where the loop always starts: the hardware signals your monitoring misses (2/3)
PCIe replays, BIOS drift and disks that SMART calls healthy: the hardware signals behind silent degradation, and what 35,000 servers at Flipkart taught us.
-
Your team is trapped in a loop: why infra teams keep firefighting (1/3)
Hardware telemetry split across tools, runbooks that age with every firmware change, servers stuck in maintenance: the loop that keeps infra teams firefighting.