@menimor I think in some ways Imgix might be better, and in same cases Imagizer will be, for example, I just ran a resizing test on the same image (from imgix asset library), and Imagizer appears to be 3x faster for uncached resizing transformations, here is the test data:
https://gist.github.com/anonymou...
Pricing wise, Imgix charges for bandwidth and accessed master files, which means even if you have very low bandwidth usage you will still be charged master files (if they are accessed even once).
Imagizer follows pay as you go model, e.g. you are only charged for API access, $1 for 1,000 - this makes it very simple to budget the costs.
Depending on how large or small your resulting files are, Imgix or Imagizer would win on price. E.g. Imagizer wins on higher resolution files, but Imgix may win on smaller resolution files since they account for bandwidth in GB transferred. I think Imagizer has a more flexible model, and just simpler to understand.
Imagizer has image recognition capabilities, for example, we can recognize dog breeds:
imgdog.nventify.com/a/img921/6544/i399Su.jpg?labels=true
{"Name":"Dog","Confidence":92},
{"Name":"German Shepherd","Confidence":92}
Imagizer knows with 92% confidence that its sees a German Shepherd >:)
@jack_levin this is an amazing answer. Thank you for taking the time to write this. We currently use imagix, but on a very small scale. We have a ticket in the backlog to look into alternatives, will def add imagizer to the list.
Makerpad
Twittume
Imagizer Engine
Imagizer Engine
Imagizer Engine
Imagizer Engine
Imagizer Engine
Imagizer Engine