koigrid vs CloudWatch Synthetics
Uptime & synthetic monitoring — the simple, flat-rate 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 a flat rate.
| Feature | koigrid | CloudWatch Synthetics |
|---|---|---|
| Pricing | Flat rate | 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.
Flat rate, no lock-in
Predictable price and portable — not tied to AWS.
Frequently asked questions
Is koigrid cheaper than CloudWatch Synthetics?
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 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.