Show HN: I made a super-simple image CDN (magecdn.com)
Hi HN,
MageCDN is a simple and affordable image hosting service I have been working on for the past few weeks. The idea came out of my own frustration with hosting and optimizing images for my blog.
While platforms like Imgur make it really simple to upload images, they don't allow you to embed them. Services like Cloudinary, Imagekit exist, but I found them too complex for my needs. Plus, they get really expensive past their free tier.
So, I started MageCDN with three simple goals:
- pricing should be affordable and scale linearly.
- basic image operations (resize, crop, optimize) should be doable within the app.
- uploading and getting a link you can use should be fast and hassle-free.
Would love to hear what you think!
40 comments
[ 3.9 ms ] story [ 97.7 ms ] threadAnd best of luck in your endeavor!
We do have it clarified what kind of content is prohibited under terms of use and how that can result in account being suspended.
As another poster highlighted, hosting other people's content is tricky. Its certainly not a business I would rather be in. I bet the management of this SaaS service is going to quickly take over your day job.
If you are just hosting your own content you can do it pretty cheaply using the AWS Serverless Image Handler stack:
https://aws.amazon.com/solutions/implementations/serverless-...
Mine isn’t image-based, but I rolled my own CDN using S3 as a backend, Lambda/DynamoDB for some metadata stuff, and Cloudfront as the CDN (so yeah, I didn’t roll my own CDN, I just implemented all the backend upload/admin stuff).
The great part is that it’s stupid cheap for a hobbyist, and Cloudfront has a generous free tier. I can also always swap that part out if it becomes too expensive.
If magecdn doesn't support setting a cap then their "no surprise charges" is misleading. But if they do support caps then it should be mentioned in the FAQ imho, it's a selling point.
>All root servers have a dedicated 1 GBit uplink by default and with it unlimited traffic. Inclusive monthly traffic for servers with 10G uplink is 20TB. There is no bandwidth limitation. We will charge € 1/TB for overusage
On the other hand, if you incurred that kind of egress on Cloudfront, you'd have no option but to pay. The bigger platforms rarely budge in these kind of situations.
I would also add that large-scale DDoS attacks (something like 80+TB!!) are unusual, especially when the target is just a small website.
[1]: https://bunny.net/network/ddos-protection/
--
1: https://bunny.net/optimizer/transform-api/
On another note bunny has really grown. From DNS to fonts
2. It costs $9/mo/website, in addition to the bandwidth. We don't charge by websites at all.
3. It does solve the problem of optimization, and serving, but not really of storage. You'd still have to upload the files somewhere. BunnyCDN does have a storage option. But it isn't geared toward images (for eg, you can't paste screenshots).
More importantly, with BunnyCDN you'd have to configure pull zone, storage zone, enable optimizer before you can start serving images. MageCDN is plug-and-play!
Good luck with the business!
Are image only CDN's a sustainable market? Maybe they are, and I'm just ignorant on why websites would choose such a thing over a general CDN.
Surely if someone has enough traffic or load to require a CDN then they would want it for their whole site and not just for image resources?
Image and general CDNs are not exclusive: pictures resized on-the-fly and hosted on image CDN, while html/js/css hosted on general CDN.
while True: requests.get("... .png")
is amusing.
I feel like a better option would be creating an open source project of the application managing the images. With it doing something unique to its competitors and giving a way that someone could use it to manage their companies images.
[0] https://git.asonix.dog/asonix/pict-rs/
...is this true? what's stopping you from getting the direct link and plugging it into your <img> tag or wherever your images from this would go?
> Also, don't use Imgur to host image libraries you link to from elsewhere, content for your website, advertising, avatars, or anything else that turns us into your content delivery network
Imgur did shut down direct links to images being shared. Now they direct to the webpage:
http://i.imgur.com/FPyso27.png
So in the future, we might expect Imgur to only allow its own website as a valid referer.
[1]: https://imgur.com/tos
While I hope you all the best, I am wondering about the target audience?
If I have so many images, I want to use a CDN instead of the native storage solution offered by my blog/shop/forum, wouldn't I also want to use an API and have far more images than 10 GB?