koigrid vs Cloudinary / imgix
On-the-fly image optimization by URL — the built-in alternative to Cloudinary, imgix and Vercel Images.
Cloudinary and imgix made URL-based image transforms ubiquitous. koigrid gives you the essentials — resize, WebP/AVIF, quality — from allowlisted sources, with no per-transform fee and right next to your Storage and apps, drivable by an agent token.
| Feature | koigrid | Cloudinary / imgix |
|---|---|---|
| Pricing | Included (no per-use fee) | Per transform / bandwidth |
| Resize + WebP/AVIF | Yes | Yes |
| Allowlisted sources (anti-SSRF) | Yes | Yes |
| Just a URL | Yes | Yes |
| Next to your storage/apps | Yes (same platform) | No |
| Manage by AI agent | Native | API |
What koigrid improves
One platform
Optimize straight from your koigrid Storage and apps.
No per-use fee
Included — no per-transform or per-GB bill.
Agent-native
Configure and read usage from your LLM via the API.
Frequently asked questions
Is koigrid cheaper than Cloudinary / imgix?
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 Cloudinary / imgix 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.