Live data from Hacker News

Show HN: Multi Tenant SaaS Boilerplate

volca.io

1–7 of 7 posts

Re: Show HN: Multi Tenant SaaS Boilerplate

#3
If I could give one recommendation here: fully document the paid features. You have zero docs that I could find on how you do authentication, authorization, subscriptions, or multi-tenancy. These are going to be the main reasons for people to purchase your boilerplate, yet there's no code examples to be found. I don't want to read how to build yet another todo app. I want to read about how to use your paid features. The todo app doesn't touch on any of your paid features.

As a buyer, I don't want to know what the definition of authentication is. I know what it is. I want to see how easy your implementation is to use vs the myriad of authz/authn packages on npm so that I can determine if your boilerplate will save me time.

Also, volca-core needs a LICENSE. :)

Re: Show HN: Multi Tenant SaaS Boilerplate

#4
Those pricing page bullets should be improved to show the benefits / features. For a tech audience commodity product (lots of competition, audience in the know and knows what they want) just do the features I would say.

Talk about tax when we get to the checkout or as a small text under the price.

Re: Show HN: Multi Tenant SaaS Boilerplate

#5
post #3

If I could give one recommendation here: fully document the paid features. You have zero docs that I could find on how you do authentication, authorization, subscriptions, or multi-tenancy. These are going to be the main reasons for people to purchase your boilerplate, yet there's no code examples to be found. I don't want to read how to build yet another todo app. I want to read about how to use your paid features.…

Thanks for the feedback! Super valuable. We will add documentation about how the features work with some code examples.

Re: Show HN: Multi Tenant SaaS Boilerplate

#6

Those pricing page bullets should be improved to show the benefits / features. For a tech audience commodity product (lots of competition, audience in the know and knows what they want) just do the features I would say. Talk about tax when we get to the checkout or as a small text under the price.

Thanks for the feedback! So maybe something like a table clearly explaining the features included in each package?