Launch HN: Refine (YC S23) – Open-source platform for enterprise web apps
Here are some questions, suggestions, and thoughts roughly categorized as I went through and understood a bit more about refine (the open source) and what I can glean from enterprise.<p>Landing Page &#x2F; Initial impressions<p>* You mention &quot;enterprise&quot; a lot on the landing page, along with being open-source, but then you also call your commercial version &quot;enterprise&quot;. It is a tad confusing delineating what is what. Having built and sold developer facing tools, *I* have enough context to understand that you mean is &quot;this isn&#x27;t a toy, you can actually use it in for-real production apps with for-real big company requirements even in open source&quot;, but I don&#x27;t think you are doing yourself favors by calling your commercial tier enterprise, as it really confuses the message.<p>* The above is made a bit worse by the fact that you don&#x27;t have any mention of a commercial product on your landing page, so when I got to pricing (usually my second page) and see enterprise, now I am not sure if the landing page is just for commercial project and open-source is just a toy.<p>* As far as I can tell, you don&#x27;t have any marketing pages for the enterprise offering beyond the pricing page? I want to know how it differs. I want to click on the list of additional integrations. I want some docs. Anything you can give me besides contacting sales is going to help. I am not saying it is a paper launch &#x2F; painted door, but it seems like one, and a thin one at that. You may have a really great product, but your GTM seems like it is lacking, and GTM for  products built on open-source is super important, but generally underdeveloped by dev led teams.<p>* Your landing page doesn&#x27;t really tell me who the target audience is, unless I have context of another product. I totally get a play that uses the momentum of another company, but I do think you lean on it a bit too hard here. I need a tagline like &quot;Refine is an opinionated project builder for React developers designed to 10x your ability to stop fighting frameworks and start getting work done&quot; or something to tell me who this is for without relying entirely on knowing retool. Similar, the enterprise product has really compelling features, but without more context on pricing, use-cases, etc, I don&#x27;t know if it is for me.<p>* Your CTA and getting started is reasonable, but, as others mention here, it is giving the user a ton of choices that they may not have a clear idea of pros and cons. I suggest changing from a horizontal card arrangement to a vertical card where you have more space to provide some guidance.<p>* Animations and graphics for marketing pages is very subjective, but imo, the animation of the different domains of front-end apps (backend, react, auth, etc) along with the rotating list of &quot;enterprise-ready&quot; features is really busy and don&#x27;t tell me much. I kept thinking that the firing concern would link with the enterprise ready feature, but it seems they were unrelated which just made it noisy.<p>Architecture &#x2F; deployment model &#x2F; commercial differentiation<p>* Are you doing the hosting directly for enterprise version and including the direct database access? If that is hosted in your cloud... that seems really tricky security wise. If you are hosting in the customer account that seems really tricky in terms of a wide range of clouds etc. I would be curious to know how this has gone so far.<p>* With enterprise and the direct database offerings, it seems like you have two choices of generating APIs that connect to DBs or are doing a more &quot;direct&quot; API that can execute SQL. Both have challenges. is there anything unique there on offer?<p>* The differentiation of features between open source and commercial seems reasonable... but I am concerned that because you don&#x27;t have *any* ability to use any server side integration, it becomes such a different beast that you don&#x27;t have an opportunity to get people to learn it. I would think that moving a &quot;taste&quot; of the server-side capabilities into open-source might be really helpful<p>Small Nits &#x2F; Fixes<p>* The generated project has a lot of places with hardcoded configuration that I know I would need to change for my app... but no docs&#x2F;comments&#x2F;hints to tell me to do that? For example, using Auth0, I have a hardcoded (real) auth0 key and secret. I found it by chance. I personally wouldn&#x27;t do that in a production app, as I want to centralize all config in one place. That seems like something I wouldn&#x27;t be happy with<p>* Your docs are expansive... but could use some refinement. They are hard to navigate, especially the tutorial section, which doesn&#x27;t appear to have any representation in the left nav? They also aren&#x27;t navigable they way I expect docs to be (for example, <a href="https:&#x2F;&#x2F;refine.dev&#x2F;docs&#x2F;tutorial&#x2F;getting-started&#x2F;chakra-ui">https:&#x2F;&#x2F;refine.dev&#x2F;docs&#x2F;tutorial&#x2F;getting-started&#x2F;chakra-ui</a> is not a page). I also was able to break the back button in the tutorial section.<p>Hopefully this is helpful, that was a lot of negative stuff, but I do want to close with overall feedback that this is a *really* hard problem and it is clear that there is a lot of potential value here.<p>If you want to get deeper into any of these questions, the email is in my profile, always happy to chat with companies building cool things :)