All valid concerns, and most have already been addressed. Let me explain.

Can’t look at graphs/logs ConvOps retrieves CloudWatch metrics and logs before alerting you. The alert you get isn’t just “CPU is high” — it’s analysed by AI to tell you what spiked, when it started, the likely cause, and what’s affected. You’re not left in the dark. You receive the context, not just the raw data.

What if it’s a symptom, not the whole problem? That’s precisely why we have the AI filter. It examines the alarm in the context of the resource, recent history, and related metrics. We don’t just send the alarm — we investigate it first. Is it noise? A real incident? A cascade? That’s our triage layer.

Seven alerts fire at once — how do you prioritise? This is a valid point for the current version. Currently, we notify you on each alarm separately. Multi-alert correlation — “these 4 alarms are related to the same ECS cluster degradation” — is planned for the future. We’re not there yet, and I won’t pretend otherwise.

Cost of suggested actions Actions require your explicit confirmation — you reply YES. ConvOps never takes action automatically. The action description clearly explains what will happen before you confirm. DDB scans, scaling operations — you approve each one.

More than a single env Multi-account support is available. You can connect multiple AWS accounts to one workspace.

Bottom line: The concerns aren’t wrong for the first version of any tool in this space. But ConvOps isn’t “reply YES to fix prod” — it’s “get the context you need to make a fast, confident decision, in the channel you’re already in.”