I'd like to give a big shout-out to Imgix, they've built a truly useful service. Their landing page copy features lines like "You can't build this in a weekend" and "This isn't ImageMagick running on EC2" - and from what I've seen using them, they live up to it. Kudos on a great product, Imgix team (and congrats on the recent funding)!<p>P.S. We tried using Cloudinary at first, but Imgix turned out to be much easier to manage. A killer feature for us was allowing us to source images from an S3 bucket (a feature Cloudinary only exposes to Enterprise customers).
I was skeptical about imgix, but I recently plugged it into a CMS for a startup I was helping out as a simple image editor + transcoding service. It did pretty much all the work: all I did was add a few buttons to alter the bri/con/vib parameters, and hook the crop up to simple jQuery cropper plugin.<p>We're also using it as a way to upload jpeg2000 files from iOS devices to save on bandwidth, which will then appear properly on Android and desktop.<p>I'd say it saved me a fair bit of infrastructure work.<p>EDIT: They had an outage the other day where new images weren't being cached that was fixed within a few hours (that sucked), but were awesome enough to provide a root cause for me.
Looks very similar to Cloudinary (<a href="http://cloudinary.com" rel="nofollow">http://cloudinary.com</a>) which I use for my startup. The pricing at lower end of images looks better for Imgix but doesn't scale as well. Still, I think cloud-hosted image processing is a great service and I'm glad there is competition in it. It let us skip huge amounts of dev work related to constructing image pipelines and organizing assets: we pay $40 (plus more for some addons) and get a massive image layer. Imgix, Cloudinary, and others let you focus on the unique parts of your own software at a really good price.
having an image server with apis solves 80% of the problem.<p>having a client counterpart lib to ease you in solves the other 80% <a href="https://github.com/choonkeat/attache_rails" rel="nofollow">https://github.com/choonkeat/attache_rails</a><p>being able to host it yourself solves the last 20% <a href="https://github.com/choonkeat/attache" rel="nofollow">https://github.com/choonkeat/attache</a>
as per the notes, I am forwarding this error message on:<p>404 Not Found
The server can not find the requested page:<p>www.texturequalitypro.com/assets/files/content_files/TextureQualityPro_Large_Sample.jpg?w=250&border=5&txt=this+is+a+test&vib=20 (port 443)
Please forward this error screen to www.texturequalitypro.com's WebMaster.<p>Apache/2.2.29 (Unix) mod_ssl/2.2.29 OpenSSL/1.0.1e-fips mod_bwlimited/1.4 Server at www.texturequalitypro.com Port 443