Would you use SaaS scaffolding/bootstrap services?
Four years ago I started a new company focused on the ‘plumbing’ that every SaaS product needs. Things like subscription management (Auth0+billing), cloud provisioning per customer, etc.
Somewhat similar to Laravel, but API based, not boilerplate code.
I’ve had it on ice for a while, while keeping the tech current. But been thinking about bringing it back to life.
For SaaS founders, do you think committing to a service like this would be valuable to accelerate dev? Would it be more valuable if it managed the full DevOps process too, being an easy button for getting started?
Every company I’ve been at since has still needed to build these same pieces on a v1 product, but selling into early stage companies can be difficult.
Hi @CandelaSoftware, I have been trying to answer this question myself for quite some time.
I am actually working on a similar project myself. So far I was not able to rule out the code boilerplate option due to the fact that developers tend to want to have control but going for an API based offering might not be a bad idea as it removes the DevOps part from the equation.
Do not hesitate to drop me an email if you want to talk more about this subject
Laravel is "just" an MVC framework. Are you thinking of Laravel Spark, maybe? It's built on top of Laravel and includes boilerplate for a bunch of features.
I actually prefer generators over an external API. I'm very, very careful about relying on an external API for core functionality. Why? Because if you do, then its bugs are your bugs, its downtime is your downtime and if the service or company closes down, then a painful rewrite is necessary. Even with a huge company that won't shut down anytime soon, they could terminate or change your service.
For payment, it's worth it. I don't want the liability of storing people's credit card data and I'll gladly let Stripe do that for me. But for run of the mill "plumbing"? No way. I want ownership of the code.
That’s some great feedback, thanks. Originally I had a few companies who wanted to use it and then ended up going the DIY route. Likely for the concerns you mention.
This is a main reason I backed away from the idea :)
Over the years I’ve often found posts asking for something binds together Auth0+Stripe into a single subscription management API for SaaS, but that seems as far as people want to go with API reliance.
Honestly I’d have the same concerns about lock-in as well, but also know the time that’s lost building this plumbing every time.
Might be you need to have an open source solution that they can migrate too, I guess as developers they would just use that instead :)
Or a self hosted solution with a commercial license?
There is 100% a problem with reset passwords, logins, signups, pricing and later on SSO.
A lot of features from https://spark.laravel.com/ as well would be nice to have instantly.
Right, my thought was still to leverage best of breed services, so the data was still there if they wanted to go DIY eventually.
Basically doing the mundane work for them, but letting them migrate off it eventually if needed.
https://www.midtype.com/
https://www.servicebot.io/
They do that and they seem to be struggling to find PMF.
Thanks, seems like a common concern with that approach (PMF). More of a solution in search of a problem.