I see that your backend relies on libvips to do the resizing. I have no experience with it, but I could make libvips-tools' vipsthumbnail program work correctly:
I'd like to echo the sentiment that offering 100% uptime and 3x, 5x, 10x refunds is a dangerous decision and actually will not increase paid signups. I've been doing operations/DevOps for over a decade (in fact I just launched a consulting startup (https://elasticbyte.net) that helps companies manage their cloud infrastructure). 100% uptime is a red flag, ops professionals never guarantee 100%.
You instead should offer standard 99.9% (44 mins a month) or 99.99% (4 min 30 sec) with standard SLA language.
CloudFlare doesn't allow this kind of use of their service. Once you start pushing enough bandwidth they will ask you to go away. And since you offer free unlimited CDN bandwidth, when that happens and you move to a different CDN provider your bill could increase 50 times over a day.
It's not bandwidth that is restricted by our terms of service it's...
SECTION 10: LIMITATION ON NON-HTML CACHING
You acknowledge that Cloudflare’s Service is offered as a platform to cache and serve web pages and websites and is not offered for other purposes, such as remote storage. Accordingly, you understand and agree to use the Service solely for the purpose of hosting and serving web pages as viewed through a web browser or other application and the Hypertext Markup Language (HTML) protocol or other equivalent technology. Cloudflare’s Service is also a shared web caching service, which means a number of customers’ websites are cached from the same server. To ensure that Cloudflare’s Service is reliable and available for the greatest number of users, a customer’s usage cannot adversely affect the performance of other customers’ sites. Additionally, the purpose of Cloudflare’s Service is to proxy web content, not store data. Using an account primarily as an online storage space, including the storage or caching of a disproportionate percentage of pictures, movies, audio files, or other non-HTML content, is prohibited. You further agree that if, at Cloudflare’s sole discretion, you are deemed to have violated this section, or if Cloudflare, in its sole discretion, deems it necessary due to excessive burden or potential adverse impact on Cloudflare’s systems, potential adverse impact on other users, server processing power, server memory, abuse controls, or other reasons, Cloudflare may suspend or terminate your account without notice to or liability to you.
Agree on this. In the beginning, we wanted to use CloudFlare for https://uploadcare.com (we're not a direct competitor, but provide image transformations as a part of our services). But it's against their policies, they confirmed it. The only option is to use a proper CDN.
That is really good to know about Cloudflare. CDN cost an important thing for anyone to take into consideration when they price their free/paid tiers and something that not everyone does.
I always try to price fee tiers so that one paid customer pays for about 100 or more free users and aim for at least 5% conversion of free to paid. It's not a hard-fast rule but a good starting point. If I can't hit that (even after crippling the free tier) I just drop the free tier altogether and make it a free trial instead.
I made this mainly because I wanted a service to use for my own projects - but the existing solutions were either prohibitively expensive or didn't have uptime guarantees.
The backend for the processing service is nodejs and sharp[1], processed images are cached on CloudFlare. The processing servers are a custom instance type in an autoscaling group on Google Cloud.
Cloudflare does not permit storing just images in any of their plans. Their terms state that serving disproportionate amount of image or video via their service will be violation of their terms. You should check it before using it for longh term or providing cheaper cache options to users.
Often when competitors are expensive it's for a reason. Occasionally you'll have stumbled onto an old industry where tech can disrupt things and lower costs, but for cloud-based image serving, everyone is essentially using the same tools and CDNs. You should have a really good reason why you will be able to deliver at a lower cost or with lower margins, otherwise it's likely you will have to end up with the same 'prohibitively expensive' rates, or will go out of business.
Well, from first glance, you're lowest plan is more expensive than imgix's $10/mo minimum. I see now that you have a free plan and I get that you're following the SaaS pricing plan status quo, but if you claim to be a lower-cost competitor, you should make the free plan more prominent.
I have a lot of media-heavy side projects. I use Cloudinary for 1 and imgix for the rest.
It's really hard to compare you price-wise to imgix because you are charging based differently.
One thing I like about imgix is that I can give them access to an S3 bucket and perform transformations on master images that aren't public-read.
Fun feature you should add: the ability to crop around faces. I.e say you have a long and tall image and you need it to be square, you could pick the center, top, or bottom to zoom in on, which do you choose? It would be nice to set a flag and say "find the subject(s) of this photo and crop around the subject(s)".
Yeah, that is a good idea. The Google Vision API actually makes it pretty easy to do. It is pretty amazing that this kind of thing is now possible. You can chain together a bunch of transformations into one like [find face] + [crop photo]. Here's one example of that implemented https://www.filestack.com/docs/image-transformations/facial-...
Now I'm kicking myself because I did something very similar for one of my clients based on AWS and shared it publicly (https://github.com/pbudzon/aws-image-gateway)! Not sure how it compares cost-wise, though. It's a combination of CloudFront, API Gateway, Lambda and S3. I'm quite sure CloudFront doesn't have limitations on what you can cache, like Cloudflare seems to have.
Like others who commented, I don't get the idea of image-resize-as-a-service, so I remember I laughed at my client when they asked me for this. For some reason I believe it's better for the world if we don't make people think it's ok to throw around gigantic images around the cables when it's completely unnecessary...
Not your fault. Developers tend to sometimes underestimate the power of releasing a command line utility as a web based/API tool that can help non techies do simple stuff. Image resizing is a recurring candidate but there are others like conversion tools (to pdf), checkers/monitors (ssl for example) etc. Yes, you could do these on your server with a simple cmd line but tons of folks are willing to pay to be able to use a browser/API to do the same.
If the image url is in front there isn't exactly a sure fire way to tell where that url ends and where the options should begin. Of course there are work arounds, but the way it is now it seems that it would cover every case.
Transloadit is great. I'm using it right now with an open-source video project (https://github.com/xiaofei-mo/mysteriousobjectsatnoon). The encoding process is just ffmpeg under the hood, but not having to write all of the glue code to get it running with AWS has saved me a ton of time.
Thanks! And yes, it doesn't pay any attention to the original filename, image format is detected by the data stream. Here's that image resized to 600px wide:
I have to admit that I don't quite understand "image scaling as a service". Scaling is almost certainly a case where shipping the image over a network is significantly more costly than just doing the scaling locally?
Here the only binary program you need installed to scale the image is curl. If you want to do it yourself, you need a whole bunch of image processing libraries installed. Because of that, you'll probably end up separating your image processing logic onto its own host on your internal network, anyway. Then you're back to where you started, making an http call to an external service. Unless latency is a critical factor, an image scaling API is attractive because you do not need to waste development time setting up (and scaling) your own image processing environment.
As someone who has never hosted an image service like this, what actions do you have to take to stop "bad" people from using your service? For example, uploading inappropriate / illegal / violent images.
I developed a website for the university I attend that anyone can upload photographs of older exams for each course. In order to solve the image content problem the system checks every uploaded image with a 3rd party image recognition API[1] before saving it. Works pretty good so far!
It can't be open like that "just use our URL" because it will bring many free-riders and shutdown your server.
But it also can't be a closed system with private keys and all that, because the hassle is too enormous -- the user will need a server to get the key for each image and so on.
I have the impression that all services of this kind suffer from the above dual-problem.
My problem is usually making the cropping "smart". I need a content-aware cropping so that the resulting image looks good.
It doesn't seem to come up too often as a known and requested feature in most of these services, I am wondering how come, this seems like a "must have" for me
[+] [-] leni536|9 years ago|reply
http://i.imgur.com/X9vKa2s.png
https://i.scaley.io/png-256x128/i.imgur.com/X9vKa2s.png
This means that you don't use a linear color space for blending colors.
Sorry about the language, the image is not made by me [1].
[1] https://web.archive.org/web/20120904060524/http://www.4p8.co...
edit:
I see that your backend relies on libvips to do the resizing. I have no experience with it, but I could make libvips-tools' vipsthumbnail program work correctly:
Note the "--linear" option, without it produces the same wrong image.[+] [-] hoahluke|9 years ago|reply
I didn't include it in the website, admittedly because I didn't fully understand it, and I wanted to keep the service as simple as possible.
Would it make sense for this to be the default?
[1] https://i.scaley.io/png-gamma-256x128/i.imgur.com/X9vKa2s.pn...
[+] [-] tedmiston|9 years ago|reply
Is it about the choice of interpolation algorithm? nearest neighborhood vs linear vs cubic, etc
I've written image processing code in the past, though color accuracy wasn't important to it, and I'm curious to understand this better.
I also currently use ImageOptim and would be curious to know if it handles this.
[+] [-] throwaway2016a|9 years ago|reply
[+] [-] devy|9 years ago|reply
At the same time shaved off 46% of the size (from 4.02 KB to 2.16 KB)
[+] [-] dvt|9 years ago|reply
[+] [-] nodesocket|9 years ago|reply
You instead should offer standard 99.9% (44 mins a month) or 99.99% (4 min 30 sec) with standard SLA language.
[+] [-] wingerlang|9 years ago|reply
[+] [-] jimaek|9 years ago|reply
[+] [-] jgrahamc|9 years ago|reply
SECTION 10: LIMITATION ON NON-HTML CACHING
You acknowledge that Cloudflare’s Service is offered as a platform to cache and serve web pages and websites and is not offered for other purposes, such as remote storage. Accordingly, you understand and agree to use the Service solely for the purpose of hosting and serving web pages as viewed through a web browser or other application and the Hypertext Markup Language (HTML) protocol or other equivalent technology. Cloudflare’s Service is also a shared web caching service, which means a number of customers’ websites are cached from the same server. To ensure that Cloudflare’s Service is reliable and available for the greatest number of users, a customer’s usage cannot adversely affect the performance of other customers’ sites. Additionally, the purpose of Cloudflare’s Service is to proxy web content, not store data. Using an account primarily as an online storage space, including the storage or caching of a disproportionate percentage of pictures, movies, audio files, or other non-HTML content, is prohibited. You further agree that if, at Cloudflare’s sole discretion, you are deemed to have violated this section, or if Cloudflare, in its sole discretion, deems it necessary due to excessive burden or potential adverse impact on Cloudflare’s systems, potential adverse impact on other users, server processing power, server memory, abuse controls, or other reasons, Cloudflare may suspend or terminate your account without notice to or liability to you.
[+] [-] igordebatur|9 years ago|reply
A disclosure: I'm the co-founder of Uploadcare.
[+] [-] throwaway2016a|9 years ago|reply
I always try to price fee tiers so that one paid customer pays for about 100 or more free users and aim for at least 5% conversion of free to paid. It's not a hard-fast rule but a good starting point. If I can't hit that (even after crippling the free tier) I just drop the free tier altogether and make it a free trial instead.
[+] [-] hoahluke|9 years ago|reply
[+] [-] tonmoy|9 years ago|reply
A simple url DOS attack from my puny browser may cripple your entire server.
[+] [-] hoahluke|9 years ago|reply
The backend for the processing service is nodejs and sharp[1], processed images are cached on CloudFlare. The processing servers are a custom instance type in an autoscaling group on Google Cloud.
Any feedback is greatly appreciated!
[1] https://github.com/lovell/sharp
[+] [-] adityapatadia|9 years ago|reply
[+] [-] sfeng|9 years ago|reply
[+] [-] callmeed|9 years ago|reply
I have a lot of media-heavy side projects. I use Cloudinary for 1 and imgix for the rest.
It's really hard to compare you price-wise to imgix because you are charging based differently.
One thing I like about imgix is that I can give them access to an S3 bucket and perform transformations on master images that aren't public-read.
[+] [-] VeejayRampay|9 years ago|reply
[+] [-] jastanton|9 years ago|reply
[+] [-] stachenfeld|9 years ago|reply
[+] [-] inka|9 years ago|reply
Like others who commented, I don't get the idea of image-resize-as-a-service, so I remember I laughed at my client when they asked me for this. For some reason I believe it's better for the world if we don't make people think it's ok to throw around gigantic images around the cables when it's completely unnecessary...
[+] [-] codegeek|9 years ago|reply
[+] [-] traviswingo|9 years ago|reply
[+] [-] rayboy1995|9 years ago|reply
[+] [-] hashkb|9 years ago|reply
[+] [-] 0XAFFE|9 years ago|reply
Please don't show a blank page when no javascript is available.
Maybe a message that you should enable javascript or better some basic information what your service does.
[+] [-] pag|9 years ago|reply
[+] [-] markplindsay|9 years ago|reply
[+] [-] dk8996|9 years ago|reply
https://scontent.fbed1-2.fna.fbcdn.net/v/t31.0-8/11206479_82...
[+] [-] hoahluke|9 years ago|reply
https://i.scaley.io/600-max-https/scontent.fbed1-2.fna.fbcdn...
[+] [-] mpweiher|9 years ago|reply
[+] [-] chatmasta|9 years ago|reply
[+] [-] mgottein|9 years ago|reply
[+] [-] stdio_h|9 years ago|reply
[1]https://clarifai.com/
[+] [-] niklasrde|9 years ago|reply
[+] [-] SnaKeZ|9 years ago|reply
[+] [-] samblr|9 years ago|reply
[+] [-] dbbk|9 years ago|reply
[+] [-] fiatjaf|9 years ago|reply
But it also can't be a closed system with private keys and all that, because the hassle is too enormous -- the user will need a server to get the key for each image and so on.
I have the impression that all services of this kind suffer from the above dual-problem.
[+] [-] artursapek|9 years ago|reply
[+] [-] mderazon|9 years ago|reply