I make a SQL-only website builder (SQLPage) that could be qualified as low code. I think all the points mentioned are valid, but some of them are easy to work a

I make a SQL-only website builder (SQLPage) that could be qualified as low code. I think all the points mentioned are valid, but some of them are easy to work around: > They wanted truly custom functionality that the low-code solution could not handle. It's important that the low-code solution has an escape hatch, or a way to to interact with external "high-code" APIs. In sqlpage, we have sqlpage.exec > They implemented a bunch of custom functionality in a product-specific or even proprietary language and now their pool of potential developer talent is tiny. I agree that low-code makes sense only if the low code is in a standard, popular language. In SQLPage, it's all just SQL. > Upgrades to the low-code platform would break their custom implementation. This is a true problem. The low-code solution really has to be careful with updates. > The underlying database structure was an absolute mess, especially after a bunch of incremental modifications This! Most low-code tools take your data hostage. You shouldn't use them. In SQLPage, we add a layer on top of a database that you still fully control.