News for hackers. Stuff that matters.
Re:What I learned running a SaaS for a year by vincvinc on Tuesday February 22, 2022 @08:31AM (#30427675)
> half of my time went to actually solving the problem I wanted to solve (knowing if a site is down, and alerting folks when that happens). The other half went to building a SaaS platform around that problem.

You’d think in today’s software landscape there would be tools to simplify or automate the part or building a SaaS business that everyone needs to do.

He mentions Stripe for payments of course, but isn’t there anything broader to get set up more quickly? Like a shopify for SaaS businesses?

Re:What I learned running a SaaS for a year by Veuxdo on Tuesday February 22, 2022 @08:32AM (#30427691)
Stripe pretty much is that. There's only so much abstraction you can do on payment processing.
Re:What I learned running a SaaS for a year by zild3d on Tuesday February 22, 2022 @10:17AM (#30428957)
> the part or building a SaaS business that everyone needs to do.

A few critical ones off the top of my head

- payments (subscriptions, cancellations, invoices, etc)

- authentication (signup, login, invite, forgot password)

- transactional emails (confirmations, etc)

for enterprise:

- permissions, access controls

- audit logs

- gdpr

- reporting, monitoring

- single sign on

other common saas-y needs

- notifications

- error monitoring

- performance monitoring

- admin tools (impersonate, deletions)

- feature flagging

I'm surprised a "SaaS in a box" hasn't really gotten traction. I think part of it is the tech stack dependencies - frontend frameworks, backend languages & frameworks, infra, databases, 3rd party tools

Re:What I learned running a SaaS for a year by joshmanders on Tuesday February 22, 2022 @06:18PM (#30435255)
You gotta understand that a lot of people who go into bootstrapping a SaaS are technical people, mostly developers. We're highly opinionated and naive af on stack stuff. We could find the ideal "SaaS in a box" framework/boilerplate, but one small feature just doesn't sit right, so now we're building it all ourselves.
Re:What I learned running a SaaS for a year by ozim on Tuesday February 22, 2022 @03:31PM (#30433309)
Frameworks like RoR, Laravel, .NET framework provide most of it which are mostly SaaS in a box from technical perspective.

Then you have headless CMS-es on top of which you also can build stuff.

So you can plugin your email provider, payment provider, single sign on. It does not take much code but you still have to understand how to integrate stuff.

Then you have wordpress where people basically install all kind of plugins and you can have all what was listed in CMS, but then you get "wordpress developers" to hire so I don't see much difference.

Re:What I learned running a SaaS for a year by dbbk on Tuesday February 22, 2022 @10:00AM (#30428715)
> Like a shopify for SaaS businesses?

This is Paddle. As a one-person startup, there's no way I could go with Stripe. The tax implications alone are too much.

Re:What I learned running a SaaS for a year by zild3d on Tuesday February 22, 2022 @10:19AM (#30428986)
that's still just payments provider vs "Shopify for SaaS" which handles a lot more
Re:What I learned running a SaaS for a year by PhilipA on Tuesday February 22, 2022 @08:59AM (#30427955)
Depending on the technology stack there are frameworks like SaaS Starter Kit for Phoenix: https://fullstackphoenix.com/saas-starter-kit
Re:What I learned running a SaaS for a year by bytebln on Tuesday February 22, 2022 @08:44AM (#30427816)
Paddle.com is pretty simple. I implemented Paddle in my App in less than 2 hours. Stripe API became too complex for my needs.
Re:What I learned running a SaaS for a year by rozenmd on Tuesday February 22, 2022 @09:23AM (#30428231)
There probably is, but I like to avoid sharing around customer data unnecessarily.