zlacker

>>amanch+(OP)
I have built this 3d bin packer. https://3dpack.ing Despite my best attempts didn’t take off:(

>>revers+wg
This looks really interesting! Optimisation problems like this are so much fun to solve and seem like such a natural fit for the SaaS model.

Could you give more of an idea about how much it "took off"? Based on earlier comments of yours, it seems that you have some paying customers. Has it grown very gradually? Do you have much churn?

Also curious how you have been splitting your time between algorithm development for the underlying optimisation problem (probably the most interesting part to me!), AI front-end (a neat value-add on top), marketing and dealing with support? If you have the time and energy, I'm sure a blog post or similar would be interesting to many people.

>>akobol+jo2
I guess i am around 150 MRR level or less perhaps. So it pays the costs and leaves me some money and I can run it forever given the condition satisfied.

I have spent countless months on the algorithm earlier. It improved from trash to something commercially reasonable gradually, it was more like getting stuck for a while then getting small break throughs.

My biggest mistake was changing my domain perhaps. Earlier it was bindrake.com Then I added 3d pack.ing and due to complexity of canonical pages google kicked me out.

Ironically recently I get contacted by a client and they said “you don’t exist on google but we found you from ChatGPT”

>>revers+SH2
Thanks! I know what you mean about "countless months" on an algorithm... Glad you were able to improve it to a useful level.

> it was more like getting stuck for a while then getting small break throughs

Like simulated annealing itself ;-) (Yes, I watched the deep dive clip)

Really cool that you give API examples right on the landing page BTW. Do you know if many customers use the API directly? Also really interesting to me that your algo is quick enough that you can return a solution directly before the HTTPS connection times out (I would have thought it might take half an hour to optimise, meaning you'd probably need to instead return some kind of handle that the user can use to pick up the solution via a different endpoint later).

A couple of minor nits I noticed, hope this is helpful rather than annoying:

- The "Blog" link at the top appears to produce a copy of the original landing page. Maybe just delete that link?

- The "API Response Structure" section is duplicated

- In the deep dive clip, at 5:31, the subtitle contains "three dpaq.ing", while at 5:54, both the voice and the subtitle say "third bin packer" (I suspect you meant "3D bin packer")