I'm so sorry you ran into that, and thank you for reporting it. This is exactly the kind of feedback I need at this early stage.

You're right, my backend logs show that most requests are succeeding, which means there must be an error happening somewhere between the front-end and the server that I'm not catching properly yet.

Based on this, implementing a more robust error logging system is now my top priority. I'll get on it right away so I can find and fix these issues for everyone. Thanks again for giving it a try.

Thanks! Not yet. To get this launched quickly and validate the idea, I'm currently using a cloud API to handle the inference.

However, my plan is to eventually deploy the model on my own server. I'll be sure to document the entire process—from setup to optimization—and share it as a detailed guide on the site for anyone interested!

I had a project for a big brand a couple years ago where we experimented with genai and inpainting and it was a huge hassle to get it working right, required a big comfy pipeline with masking, then inpanting, then doing relighting to make it all look natural, etc.

It's crazy how fast genai moves, now you can do all that with just flux and the end result looks extremely high quality

That's a great question. Right now, the inference costs are coming out of my own pocket. My main goal was to let people experience the model's potential without any barriers.

To keep the project sustainable in the long run, I'm exploring some options, like potentially offering a paid tier for heavy users or more advanced features. For now, I'm focused on improving the core experience and will do my best to keep costs low so it remains accessible to as many people as possible.

Glad you liked the first result. And ugh, sorry you hit that error on the second go. You're right, that "unexpected error" message is pretty useless. Better error handling is at the top of my to-do list now.