Ask HN: Tech stack for small SaaS side projects as a solo developer?

Frontend: bun, solid.js, tailwind, astro -> cloudflare pages

tbh I had a smoother setup with solid-start but astro is better if you have static pages and everything I do is static pages: either pre generated static content or an app which calls an API. I don't want a server busy rendering HTML and we have free hosting anyway thanks to all the JAMstack marketing money.

Backend: rust, axum, sqlx, sqlite, redid, systemd -> hetzner

Single static binary is great for deploying whenever. Rust means my code won't likely break because of typos or brain farts. You likely don't need a database running in another process until much later on. If I do need it, I pick postgres.

I do have a separate, centralised auth / permissions / license services I use for a bunch of different services. Custom coded. Services get notified and update a local cache in redis with the data If I were starting from scratch I'd just chuck it in the main service (and what I did for years).

With the containers thing any stack can do this.

But I get what you mean. Avoid anything to do with JS. It's the worst of the worst for stability. Avoid Ruby on rails. Avoid python. These ecosystems will evolve out from under you.

Avoid anything from Microsoft. Did you make a website in 2014? tough luck, you are stuck on old .NET world now. Unless you port things over to the new world. Did you use silverlight? whoopsie!

If you really need your SaaS to work forever write it in Go.

  - front-end: either Vue or server rendered html from templates
  - back-end: Kotlin/Java, Go, (if I'm adventurous Phoenix/Elixir or F#)
              framework: something lightweight like Javalin + JDBI (or homegrown)
  - db: MySQL (because I can multi-writer, backup/restore from *my* memory) or a cloud service offering

Front-end: Bootstrap, vanilla JS, for visualizations: D3.js and Babylon.js

Backend: Java Spring Boot, PostgreSQL

Deployement: semi-manual, script rsyncing the Jar onto the dedicated Hetzner Server

Regarding ease of adding new features: I guess that depends mainly on your code base and less on your stack