No-code tools and platforms serve different purposes: one builds applications, the other hosts them long-term. Some vendors excel at tooling but struggle with hosting, while others do the reverse. The best approach pairs strong infrastructure providers with superior tool vendors instead of accepting vendor lock-in.
Chapters
Is that no-code tool a tool or is it a platform? Is it something that you are going to use or to create the things that you need, or is it something you're going to rely on as a host for your software going forward? This is a really important distinction because it tells you what metrics you're looking for out of the institution that you're talking to. There are companies that provide wonderful tooling and that really are only okay at hosting because it's not their center of gravity. There are others that are really good at hosting and that are not really good at tooling. The brilliance of no-code is the ability to assemble these things, to use the infrastructure player where they're really good and the tooler where they're really good. You're going to find a lot of the tool vendors want to keep you using their hosting because they believe that's going to be how they keep you as a longer-term customer. This is misguided. What they should be doing is providing the absolute best tooling experience so you continue to build and extend using them while they host in the world-class environment that serves