koigrid vs CloudWatch Synthetics
Uptime & synthetic monitoring — the simple, built-in replacement for CloudWatch Synthetics.
CloudWatch Synthetics runs canary scripts on Lambda — powerful but fiddly, AWS-only, and billed per canary plus Lambda runs. koigrid Checks gives you the same outcome (is my endpoint up, fast, correct?) with simple declarative checks, built-in alerting and no per-run fee.
| Feature | koigrid | CloudWatch Synthetics |
|---|---|---|
| Pricing | Included (no per-use fee) | Per canary + Lambda runs |
| Setup | One API call / dashboard | Canary scripts + IAM + CloudFormation |
| Assertions | Status · latency · body · header | Scripted (Node/Python) |
| Alerts | Built-in (email + webhook) | CloudWatch Alarms + SNS |
| Lock-in | None (portable) | AWS-only |
What koigrid improves
No scripting
Declare a check with assertions — no Puppeteer canary to maintain.
Alerts included
Email + webhook out of the box, no SNS wiring.
No per-canary fee, no lock-in
No per-canary or per-run bill, and portable — not tied to AWS.
Frequently asked questions
Is koigrid cheaper than CloudWatch Synthetics?
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 CloudWatch Synthetics 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.