Re:Launch HN: Creo (YC W24) – Build Internal Tools with Reac...
by solias99 on Tuesday April 02, 2024 @03:19PM
(#39909777)
All you do is write a single page in the tools folder and deploy.
We embed those tools in our parent web app, which has authentication, team permissions etc. So you will never interface with the code that does that.
You just have to focus on your business logic.
In terms of the AI copilot, the main value prop is knowing about our components, and using them to stitch together something fast. (Instead of the AI writing the component from scratch.)
Then when you say you provide Auth etc, does this mean we have to fully commit to use your stack for auth etc, or can we put this in an app that has existing auth with, say, Auth.js or similar?