14 comments found.
login credentials don’t work for the demo @: https://demo.31saas.saidhasyim.com/
Hey thanks for reporting. There was a change to the URL, and I’ve just fixed this. Thanks a lot.
Don’t forget to update your Live Preview, that link is dead.
Thanks for letting me know. The updated URL has been submitted, but it is still pending Envato’s approval. Meanwhile, this is the updated link: https://demo.31saas.saidhasyim.com/
Hi, the demo is not working anymore, is it stil supported? Thanks
hello. My apologies, i updated the demo url and it was pending CodeCanyon’s approval. The new link is https://demo.31saas.saidhasyim.com/
Thanks 
This is a work of art, and it’s a masterpiece, unfortunately I mostly work with PHP otherwise this was ending up in my cart. perhaps in the near future.
Great work
Thank you for the kind words. I’m glad you appreciate the work.
I expect an admin management panel should be integrated to manage, user, plans, subscriptions, payment gateway, blogs and more.
Thank you for your feedback! 31SaaS is designed as a boilerplate to help developers quickly create products without having to rebuild generic functionalities like authentication, database connection, and Stripe payment integration.
While I do not include an admin management panel out of the box, once you have all the necessary API connections and integrations set up with 31SaaS, building an admin panel becomes straightforward.
This is very interesting but before I buy. Why is there a CookieFall Back in Local storage? is there a way to disable that?
Hello wiesty, I couldn’t find this message in the demo page. Could you let me know where you find it?
If you are referring to some warning messages when launching the Stripe page, it occurs in Stripe page that is beyond our source code control. Happy to look into it if you let me know.
When I am logging in on the demo page, normally you save the SessionToken/JWT Token as a secure cookie. But somehow it is also saved in the local storage with the key “cookieFallback”.
What auth system did you use? NextAuth.js or auth.js
Hello Wiesty,
Thanks for letting me know. I appreciate that.
The authentication is using Appwrite. When accessing Appwrite API from any third-party domain, some browsers block Appwrite’s secure cookies. As a workaround, Appwrite stores user sessions in the browser’s localStorage. However, that can be solved by setting up custom domain for the Appwrite endpoint at DNS. I have included the steps in the documentation.
No change to the source code.
I have also applied that in the demo app. If you retry, it shouldn’t store the cookieFallback anymore upon login.
Great Work!
Great Work!
Thank you.
which database?
Do you have a prisma?
Even better, it uses Appwrite, which serves as both authentication and database. Compared to Prisma, Appwrite’s free tier is very generous. You start to pay when your project has scaled up a lot.
I will look into adding Prisma in future updates if there are many buyers demanding for it.
Having said that, you can swap the boilerplate’s database with any database of your choice. The database has already been integrated with TanStack queries to optimize queries. You can replace it with another database and apply the same configuration.
I would like to build 10 product. Do I need to buy 10 times? Thanks
Hello, that’s right. Envato’s 1 license can only be used to create a single end product.
10 end products would require 10 licenses.
Give 1 a try first before purchasing 10 
How does this work? I don’t understand the full concept, and how to use it. Is it possible to schedule a demo walkthrough? Or is there a video tutorial I can watch? It looks like something interesting.
Hello,
Basically 31SaaS provides developers with a complete source codes that serve as a starting point with a lot of the basic features (plus more) and design elements needed for a modern and stylish SaaS website. Instead of starting from zero, developers can use this template to save time and effort, focusing more on adding unique features and customizations that make their SaaS stand out rather than rebuilding the necessary functionality from the ground up, for example: authentication, billing, API calls, database configuration. Plus, you get more than just those basic functions such as webhook, JWT token generation, protected routes, dark mode, mobile responsiveness, etc.
When you purchase 31SaaS, you get the complete source codes which compile into the exact demo SaaS that you see at https://demo.31saas.com/.
I have recorded an explainer video here: https://youtu.be/LX9XGCVQ4eE. Let me know if you need more information. Happy to clarify.
Great Work!
Thanks
I bought it but there is an error when installing it. Can you write your e-mail address?
Hey updayz, thanks for your purchase. Don’t worry, send me the error your encounter at support@saidhasyim.com, and I will take a look at it.
Great Work?
yes, give it a try.
That’s a nice item. I’d love to see more updates: 2FA or even better: Passkeys, user accounts that can set a billing address, invoicing, user management
Thanks for your comment, Kaje.
- I will consider adding 2FA in future updates.
- Billing address is set during checkout at Stripe. The address is kept in Stripe rather than in our database. If you wish, you can easily extend the codes to store user’s personal data + any other details There are already some fields provided as an example.
- Likewise, invoice information is already integrated with Stripe. It will be easy to customize the boilerplate to suit your specific needs and store the invoices data too.
- User management is currently managed in database. Do you mean, a separate admin functionality to manage users? If so, you can build the admin panel using the boilerplate.
