38
65 Comments

What tools and frameworks do you use to create your SaaS?

I was wondering what tools and frameworks you use to make your MVP and/or your SaaS

  1. 16

    Lot's of people are commenting with their development stack, but I thought I would list some tools/services:

    1. 1

      Now this is something to appreciate

    2. 1

      Thanks for the added reasons.

  2. 6

    For me, PHP (Laravel) + InertiaJS + VueJS + TailwindCSS = 🎉

    1. 2

      my favourite, planning for my next saas using the same stack

      1. 1

        Brilliant. If I could pick 1 thing that has had the biggest impact on my career as software developer in the past 6 years, it would be Laravel for sure.

        1. 1

          This comment was deleted 3 years ago.

          1. 1

            I use Laravel Forge for server management and then host on either Linode or Digital Ocean. Lately, I've been preferring DO because of their better interface and server monitoring/analytics.

    2. 2

      what is the significance of InertiaJS?

      1. 2

        For some of my apps I don't need to have a full SPA with backend API, but would still like to have some of the advantages of that approach. Mainly navigation and data table rendering without full page refreshes. Inertia lets you render your site client side, but use server side routing.

    3. 1

      @hschutte I'm looking to build a SaaS app using Laravel but don't have any idea how to build one. I've built Laravel web apps in the past but can't seem to find any good tutorial for building a SaaS app using Laravel. Can you help a bit?

      1. 1

        I came across SaaS Adventure course by Devdojo.com. I can't really comment because I haven't gone through it myself. But I am sure the course uses Wave SaaS boilerplate they developed, which is based on Voyager (also by them), which is based on Laravel.

      2. 1

        Sure. Are you struggling with the payment integration, or what aspect of the SaaS app is giving you trouble?

        1. 1

          Thanks for the reply. I can't understand how to get started and lay the foundation of building a SaaS app.. this includes structuring the architecture, database and multi-tenancy stuff.

    4. 1

      Why the mix of PHP and JS and not, say, Laravel Spark?

      Side question: This is my first exposure to Laravel and I would much rather deal with PHP than JS. Are there awesome Laravel tutorials out there?

      1. 1

        As far as I know Laravel Spark still has some VueJS components included, so that would still mix PHP with JS.

        Laracasts probably has the best tutorials and Jeffrey's voice is very calming 😜

        1. 1

          TIL. Thank you for the info and the link!

  3. 5

    Elixir + Phoenix + LiveView + TailwindCSS.

    If it's bigger, I'll also use Vue and maybe even GraphQL.

    If it's really simple, then I'd probably use something completely different just so as to keep on learning. I'm a pretty strong believer in learning a new language every year or two and continually learning new frameworks, APIs, protocols, etc.

  4. 4

    Using react, nodejs and express. For session management using SuperTokens (https://supertokens.io/) instead of express sessions. Though they are relatively new, they look very promising. Definitely more secure anyways.

  5. 4

    AWS serverless stack (ideally, only pay per use AWS services), golang for the backend and reactjs + tailwind (it's f-ing amazing 🎁)

  6. 4

    Looks like I'm the lone .NET warrior here!

    [EDIT] I'm not alone ;-)

    1. 2

      You’re not alone, in there for you, even though... oh wait sorry got carried away

    2. 2

      Add +1 for .Net ( WPF, WCF, ASP.NET MVC etc. )

    3. 2

      +1 for .NET. I normally have a REST API written in dotnetcore. Front-end in ReactJS/GatsbyJS.

  7. 4

    Next.js (React) + Bulma + Firebase Auth + Firestore DB + ZEIT Now

  8. 4

    I'm a big fan of Ruby on Rails, Bootstrap 4, and a sprinkle of jQuery.

  9. 2

    I will avoid the vendors to chose, there are 10-50 choices to make and none are the best blind choice, mentioning a product blindly is a disservice to you so I'll instead be more helpful and focus on the technology for SaaS.

    Assuming the infrastructure is a cloud service provider (CSP) that looks after IAM, DNS, compute, and network.

    • SAML: for federated authentication (to every identity provider)
    • Relational database: for the small amout of persistent data you will need to store
    • Object storage; Chose a AWS S3 compatible service like GCP, Wasabi, SwiftStack, Dreamhost, or AWS itself
    • Document storage: for fast search across large datasets like logs and analytics needed to improve your services. Luscene is the technology behind solutions like ELK (Elasticsearch) and Solr, I personally like to chose something that supports a GraphAPI like RavenDB and try to avoid ancient style document DBs like MongoDB because of the complexity and limited 'valid' use cases.
    • Containers! very important for a SaaS to put workloads into granular, idempotent, and immutable constructs like kubernetes pods or docker for the ability to scale beyond the limitations of network-based routing and load balancing. This is the rare case more options is not always more complex, unless you actually start exploring those options, when you need them they are a choice you have.
    • Programming language: chose one with more flexibility so your core contributers can use the same language for many different uses. For example Python can be used for systems and ops, API and website, Data Science and Machine Learnging, then there is Go which is great for backends and getting better for frontends with the help of webasembly, is used heavily in the container world, and a Rego derivative is used for Security (OPA, Conftest) and other security tools (Snyk, CVE, Cloudflare PKI, Gophish, Gosec, and even a new TLS implementation).

    BE WARNED, do not chose a programming language that is using floating-point arithmetic if you intend to be doing any currency or number analysis that must be accurate! Chose an arbitrary-precision arithmetic language of you will suffer bugs. Devs do not learn the fundamentals needed for precision any more, and many devs that do performance conscious coding or machine learning prefer floating point but that means you lose numerical accuracy and that could cost you a lot of real money or reputation if you're relying on accurate number computations.

    If unsure, try doing 0.1 + 0.2 and if you don't get 0.3 you are using a language that defaults to floating point arithmetic - the warning is that these languages usually have hacky ways to get 0.3 (arbitrary-precise arithmetic) using uncommon primitives or 3rd party libraries but devs will always default to the native language when adding, minus, divide, multiply unless forced to use uncommon or 3rd party methods that often cause extra effort and a performance hit. So don't let these bug exist in the first place, chose the right tool for the job, chose a language with arbitrary-precise arithmetic to do your currency or accurate work, and chose a floating-point language to do the machine learning and analysis that ends up on dashboards and graphs and not end up on a statement or important report (and were wrong due to rounding errors...)

    Learn from these insights and you will thank me one day.

    Good luck

  10. 2

    old school..php, yii, jquery

  11. 2

    MERN stack basically. Just finishing backend in Express.js + mongoDB, no external services used - self hosted mongoDB, JWT authentication etc. , on DigitalOcean. Really good experience so far 👌

  12. 2

    ReactJS + AWS Amplify (Cognito, GraphQL, Lambda)

  13. 2

    If SEO is important, then Next.JS, Express and Postgres, if SEO isn't important, then Gatsby JS for landing page, and the app is built with React, Express, and Postgres.

    1. 3

      How is Next any better for SEO than Gatsby?

      1. 2

        yeah, Gatsby is great for SEO. I have my personal site with blog on Gatsby 👌

      2. 1

        I prefer Next.JS for SEO for the application, since most apps require a backend or an API.

        Gatsby on the other hand, is for static websites, and not for a full stack application.

        1. 1

          Yes but having a backend or an API makes absolutely zero difference for SEO 🙂

        2. 1

          Gatsby can do more actually. It's a React app serving static files, but since it's a React app, it can do anything React can.

    2. 1

      Are there any drawbacks to using Next.js over create-react-app? I'm wondering if using Next.js makes sense in something like a SaaS app where SEO is not important?

      1. 1

        If SEO is not important, then there's no point in using Next.JS. The whole point of Next.JS is to provide server side rendering, which drastically improves SEO.

        1. 1

          Yes, that's the standard argument for using Next.js. But what I wanted to know is what disadvantages does using Next.js have over create-react-app in apps that don't need SEO? At present I use create-react-app for all my front-ends, but it has it's disadvantages, like the lack of inbuilt routing for instance (which Next.js offers). So I'm just wondering if it makes sense to just use Next.js for all apps going forward whether SEO is required or not.

          1. 1

            You can achieve inbuilt routing easily with react via react-router-dom.

            I think it just boils down to whether or not you need server side rendering, and if the benefits of server side rendering is what you need for your application. If not, then there really is no need to use Next.JS

            1. 1

              Thanks. React-router-dom is what I use presently for routing.

              What would you say are the drawbacks of using Next.js over a simple react app in your experience?

              1. 1

                I don't think there are any drawbacks.

                If I don't need server side rendering, I just won't use Next.JS.

                Next.JS wasn't built to be a replacement or a solution to create-react-app. It's just a boilerplate for server side rendering, which you can do manually with a backend & create-react-app & redux.

    3. 1

      GatsbyJS is great or SEO

  14. 2

    vue.js+ node+ php+ mysql

  15. 1

    I‘m so surprised that Django seems to be out of fashion.

  16. 1

    For me, for the SplitCSS.com project, I used:

    • Laravel
    • Tailwind CSS
    • NodeJS
    • Headless Chrome
    • UnCSS
  17. 1

    Flask(Python) / ReactJS / Postgres
    I also use my own open-source boilerplate https://www.saasforge.dev that allows me to focus on functionality instead of inventing the wheel every time.

  18. 1

    Trying to keep it boring (and outsourced) --

    • django web backends
    • golang worker backends
    • vanilla javascript (but mostly django rendered html)
    • AWS RDS (mysql)
    • AWS SQS message queue for distributing work
    • AWS ALB + ACM auto-updating certificates in the load balancer
    • AWS ASGs scale out backends based on load
    • AWS Cloudwatch for logs and some metrics (for now, ELK hosted by elastic.co is tempting)
  19. 1
    • Ruby/Rails
    • Turbolinks + Stimulus + Stimulus Reflex
    • Tailwind CSS
    • PostgreSQL
    • SendGrid
    • Heroku
  20. 1
    • Ruby on Rails
    • React and some StimulusJS
    • Bootstrap (considering moving some things to TailwindCSS)
  21. 1

    Mostly React (with Next.js) + Firebase + Firestore + Zeit or Netlify

    Made a boilerplate from my current setup I use in my current projects: https://www.reactmilkshake.com/

  22. 1

    I built https://noorahq.com using React, Typescript, Node.js, GraphQL and MongoDB. For the marketing pages I'm using Gatsby.

  23. 1

    React and Firebase (for auth, db and hosting in one place), with some Firebase functions in JS for external api calls - good for an MVP but wouldn't want to be tied into Firebase for a more established site

  24. 1

    Angular + Amplify + GraphQL + Cognito + Lambda = my complete stack

    I look a lot for "serverless" stacks, even if I'm a sysadmin :'D. This way I can focus on business and dev without worrying about managing my infrastructure.

  25. 1

    Elixir + Raxx + Svelte.js + TailwindCSS

    A bit eclectic but honestly working very well for me.
    Elixir is great, We launched on PH today and I'm not at all worried about traffic spikes

  26. 1

    Frontend: Vue(vuetify)/Nuxt,
    Backend: nest.js, MongoDB or MySQL, Nginx.
    If SEO is important, then nuxt with vuetify.

  27. 1

    Laravel + React + Bootstrap. For SEO and crawlers, we use prerender.io.

  28. 1

    Figma for prototyping.
    Frontend: Vue/Nuxt, PUG, SASS.
    Backend: Koa.js, Passport.js, MongoDB, Nginx

  29. 1

    Vue (w/ Vuex, Vue Router), LESS, Flask, MySQL, Redis, AWS, Sendgrid, Google Analytics, Amplitude

    ...and Stripe! Surprised to see most people skipping the payment part of SaaS :)

  30. 1

    backend = node js + express + mongodb
    frontend = mithril js + SCSS

  31. 1

    reactjs + node + express + mysql + jwt
    Maybe just Apache for serving simple static content

  32. 1

    React + Redux + bootsptrap + nodejs (expressjs) + postgres

  33. 1

    Personally I like laravel and vue.js. PHP is quite good for quick prototyping if you have some experience with it.

  34. 0

    This comment was deleted 4 years ago.

  35. 1

    This comment was deleted 4 years ago.

Trending on Indie Hackers
I talked to 8 SaaS founders, these are the most common SaaS tools they use 20 comments What are your cold outreach conversion rates? Top 3 Metrics And Benchmarks To Track 19 comments How I Sourced 60% of Customers From Linkedin, Organically 12 comments Hero Section Copywriting Framework that Converts 3x 12 comments Promptzone - first-of-its-kind social media platform dedicated to all things AI. 8 comments How to create a rating system with Tailwind CSS and Alpinejs 7 comments