koigrid vs AWS CloudWatch
Events, metrics and alarms built in — the built-in alternative to AWS CloudWatch.
On AWS, logs, metrics, dashboards and alarms are a separate service billed per metric, per alarm, per GB and per API call — and you wire each resource to it. koigrid ships observability with every resource: an event feed, health metrics sampled from your databases and caches, and email alarms.
| Feature | koigrid | AWS CloudWatch |
|---|---|---|
| Event timeline per tenant | Built-in | Logs Insights (extra) |
| Resource health metrics | Sampled automatically | Per-metric, you wire it |
| Threshold alarms → email | Built-in | Alarms + SNS (extra) |
| Setup | Automatic with every resource | Per-resource, per-metric |
| Query by API / AI agent | Native | API (complex) |
What koigrid improves
Zero setup
Observability comes with every resource.
Alarms included
No separate SNS to wire up.
Agent-native
Query events and metrics from your LLM.
Frequently asked questions
Is koigrid cheaper than AWS CloudWatch?
It depends on the workload. koigrid charges for the RAM and disk you reserve, by the hour, shared vCPU included, from a public price list — with bandwidth included and no per-request fees. Egress-heavy setups usually come out well ahead; see the estimate above.
Can I migrate from AWS CloudWatch without lock-in?
Yes. koigrid runs on portable primitives — standard PostgreSQL, S3-compatible storage and containers — so you can move in (or out) whenever you want.
Where is my data hosted?
In data centers in the EU, on servers we run ourselves. The privacy policy says exactly where.
Can I run everything from an API or an AI agent?
Yes — koigrid is API-first and agent-native: every action has an API and a scoped token, with llms.txt and OpenAPI so an LLM can operate it end to end.