Comparison

koigrid vs AWS CloudWatch

Events, metrics and alarms built in — the flat-rate 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.

FeaturekoigridAWS CloudWatch
Event timeline per tenantBuilt-inLogs Insights (extra)
Resource health metricsSampled automaticallyPer-metric, you wire it
Threshold alarms → emailBuilt-inAlarms + SNS (extra)
SetupAutomatic with every resourcePer-resource, per-metric
Query by API / AI agentNativeAPI (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?

koigrid is flat-rate with bandwidth included — no per-GB egress or per-request fees. For a comparable setup you usually pay a lot less (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.

Is my data hosted in the EU?

Yes. koigrid is EU-hosted (on Hetzner) with data sovereignty by default.

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.