Thanks to all our early adopters and beta testers for making this possible.

Here's a direct link to a short (6m) screencast by @imbriaco walking through the basics. https://www.youtube.com/watch?v=bYb-Z52oCT0

We'll be continuing to work on the cfn bundle and release new screencasts on more complex workflows over the next few weeks. So, let us know if there's anything particularly frustrating about your current CloudFormation workflow.

Really appreciate it WhitneyLand. Thanks again for reaching out in the first place :+1:

Oh gotcha. Yeah that's mainly for testing, but would be slow to use in practice since it's not behind a CDN. We'll probably start throttling that one, only for use on the homepage, but feel free to signup and use your own account for free.

Yep, we're actively building both url whitelists per Firesize account and url signing.

Oh yeah a default would be nice. Good idea.

The image on the homepage isn't behind a CDN, but when you signup we give you a custom subdomain which is behind a CDN. Although the initial loading and resizing still takes a quick second, before we cache it.

Not exactly. The Heroku addon just means you can easily signup and manage Firesize from the Heroku dashboard. Although the code is AGPL'd so you could totally run your own hosted version of Firesize: https://github.com/asm-products/firesize

Oh nope, but that would be pretty sweet. I'll throw that in the queue of things to build next.

We just grab whatever image you include in the url, so as long as the images in your S3 bucket are public, Firesize should be able to resize them just like normal.

I like your pricing model much more--I don't like how Cloudinary charges me for storage, because I don't want them to store the images, just transform them.

What I would need to move over to yours are the following features: * Reorienting the picture based on exif data * Picture gravity via face detection * Way to ensure no one else maliciously uses my account (e.g., domain whitelisting/CORS, only pulling from my S3 bucket, something like that) * Renaming the output file image on the fly

Obviously, I'm only one customer, so don't do anything based on just me! But if it's at all helpful, these are one potential user's needs :)

Yep that's exactly why we built it. To be honest it's not overly complex to build yourself, but taking the time to get it right, setting up the CDN, and maintaining background workers can be pretty expensive when you factor in developer hours.

Oh yeah shoot me an email (firesize@helpful.io). We're working on making it available in other regions as well. Sorry about that.

Ah! Thanks iokanuon. If you add a bounty on Assembly, I'll award you some ownership for pointing this out: https://assembly.com/firesize/bounties