koigrid vs AWS EventBridge
Scheduled jobs that just run — the flat-rate alternative to AWS EventBridge + Lambda.
A scheduled task on AWS means EventBridge rules, a Lambda or Fargate task, an execution role and CloudWatch logs — plus cold starts, a 15-minute limit and IAM. koigrid runs any container on a cron with limits, logs, retries and gVisor isolation, in one API call.
| Feature | koigrid | AWS EventBridge |
|---|---|---|
| Run any container | Yes | Lambda runtimes / Fargate |
| Time limit | You set it | 15 min (Lambda) |
| Retries with backoff | Built-in | Configurable |
| Logs + exit code | Built-in | CloudWatch (extra) |
| Create by API / AI agent | Native | Complex (IAM, ARNs) |
What koigrid improves
No 15-minute limit
Run jobs as long as you need.
Retries + isolation
Exponential backoff and a gVisor sandbox by default.
Agent-native
Create and trigger jobs from your LLM.
Frequently asked questions
Is koigrid cheaper than AWS EventBridge?
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 EventBridge 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.