I didn't have enough time to dive into all the information or test out the editor. However, one bit of feedback that I have is just wondering what sets ERD Lab apart from other existing solutions? What motivated you to make your own DB design tool? If a prospective customer was either weighing the pros/cons between several DB design tools or already using another tool, what would compel them to decide on using ERD Lab?

Maybe consider including a table highlighting the differences in features/pricing from other similar tools on the homepage (after the list of features) or a separate page entirely highlighting this information? For example, Render.com has a page specifically highlighting how their product is a better PaaS solution compared to Heroku [0]. This is just a thought.

Personally, I'm not familiar enough with DB design editors to know what I should be looking for in such a tool. Moreover, about ~1 year ago, I was looking for a solution that solved this exact problem, so I am genuinely curious about this.

Finally, just wanted to mention that while I don't need this at the moment, I did bookmark it to consider using in the future.

Otherwise, great job, and I wish you the best!

[0] - https://render.com/render-vs-heroku-comparison