That is probably a good model. First build (prototype) it in Retool to nail down the database, functionality, workflow and business logic and then pass it off to someone to recreate in Vue for a royalty free, aesthetic, performant and scalable product.
If they can retool can find a way to integrate in 3 or 4 basic patterns and have a pricing model that include clients rather than users they might pull it off. The crux of the seems that they only want to only support one type of authentication which will never been successful.. You may as well write your own if you going to have to jump through retools proposed authentication model.
Update here: we just launched Retool Embed, which lets you securely embed Retool apps into your existing portal or web app. You can use your existing auth to give users access to embedded Retool apps, and Retool provides security and auditing for external users out-of-the-box (docs here).
Because we're talking about external-facing Retool apps embedded into your product, the pricing model needs to make sense upfront and at scale. Because business models vary (or some companies don't monetize users at all), we've worked with our early customers to align on what works.
Would welcome any feedback on the Embed product - please don't hesitate to share it at antony@retool.com!
2 Likes
Hi all, we just made some significant changes to our pricing! Instead of charging the same price for any user at your company, we will now charge different rates for standard users (people who build apps in Retool) and a significantly lower amount for end users (people who only view or use Retool apps). See the details on our pricing page.
I'd love to understand if this helps unblock your use cases, or if there's more work to be done. Please shoot me a note at antony@retool.com if so!
2 Likes