koigrid vs Cloudflare R2
S3 storage with bandwidth included and no Cloudflare lock-in.
R2 has zero egress fees too — but it ties you to the Cloudflare ecosystem, and it isn’t a managed, agent-native cloud with human support.
| Feature | koigrid | Cloudflare R2 |
|---|---|---|
| Egress | Included | Free |
| Lock-in | None (open MinIO, portable) | Cloudflare ecosystem |
| Pricing | Per GB-month, egress included | Per GB-month |
| Agent-native + human support | Yes | No |
What koigrid improves
No lock-in
Open S3 (MinIO), portable to any provider.
A whole cloud around it
Apps, databases and caches on the same platform as your buckets.
Agent-native + support
Manage via LLM, with human support.
Frequently asked questions
Is koigrid cheaper than Cloudflare R2?
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 Cloudflare R2 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.