UseGravity.App VS Nodewood

Is this a monorepo setup? It looks like one from the graphics. I also think when it comes to these SaaS starter kits its helpful to have visuals of the out of the box look and feel. I would also recommend creating a docs page. For example I've used this a few times https://usegravity.app/ and the thing that sold me on it is the Docs, it gives the feeling that its very robust. - Source: Hacker News / 7 days ago

Does anyone have experience using the Gravity SaaS boilerplate (https://usegravity.app/) ? Our team is currently evaluating it for an internal expansion project, and we want to assess its entire code base before making the actual purchase. Source: 12 months ago

Your landing page, messaging, plans and pricing looks like a mix-match of content lifted from other SaaS boilerplates on the market including mine (https://usegravity.app). Source: about 1 year ago

If this helps, there's a similar service called https://usegravity.app . It's a full-blown starter Node/React starter kit. It starts at $800, or $900, with integrated billing. It seems like a high price and a successful product (earning over $25k per month). I found out about it when the founder did a Podcast https://indiebites.com/72. He also has a community around it, which I think is the main USP. Source: over 1 year ago

It's pretty easy to implement into any boilerplate. I've helped a few customers add it to their apps built with my usegravity.app boilerplate. Source: over 1 year ago

Hey, thanks for the mention! I'm the creator of Nodewood, and I'm happy to answer any questions anyone has on it, or really anything else in the space I can help with. Source: about 1 year ago

This is largely why I built Nodewood [1]. Every time I wanted to start a new project, almost always a SaaS idea, I'd skip over the "boring stuff" like building user management, subscription management, teams, admin, all that, to get to the meat of the business logic, to make sure I had a valid idea. But I still needed all that stuff eventually, so I'd have to lose time later building it all in! So I decided to... - Source: Hacker News / over 1 year ago

This is actually part of why I created Nodewood [1], because every new Node project required pulling all that together, and every new SaaS idea I had had the same basic requirements (user management, subscription management, teams support, etc). Then I figured, if I found this useful, surely others would too, so I packaged it up and have had a few happy customers since then, who have helped me refine it, which... - Source: Hacker News / almost 2 years ago

Well, I've spoken about this before, and on here no less, but only really in response to posts like this. I don't do any advertising or speak about mine except in interviews, since it's usually indicative of the kind of requirements they're looking for. I created a SaaS bootstrap for Javascript called Nodewood [1]. It actually started as just a template for me, because there's a lot of setup for each new JS web... - Source: Hacker News / almost 2 years ago

Disclaimer: I'm the author of the following boilerplate. Nodewood (https://nodewood.com/) is a Javascript SaaS boilerplate built to take advantage of using Javascript on the server and in the UI. Models, Validators, and other business logic can be re-used in both builds, so you don't have to write, rewrite, and maintain that logic in both places, or in different languages. It has built-in subscription management... - Source: Hacker News / about 2 years ago