Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'm a devops engineer and I would prefer not have to worry about scaling or unexpected costs from the provider.

My dream SAAS or cloud company is one that does payments and revenue to resource scaling. They integrate your payments solution of customers to scalability of your infrastructure.

In other words, the more active customers you have the more capacity you have. They would handle all the payments collection and take a cut of your revenue.

The guarantee is that you can handle any number of customers based on the number of paying customers.



But then it's static while transactions aren't occurring. This only makes sense to me in a system in which the load IS a transaction like a payment gateway, or a strict single tenant architecture. You're not gonna scale when a customer bursts because they didn't know enough in advance to pay you before?


I assumed that the provider of said service would have profoundly scalable systems that can absorb load fast, similar to AWS Lambda and Firecracker VMs.


The ideal model might be customer pays for hosting direct from the cloud provider then buys your app service as an add on install.

Sound crazy? Same principle has worked since the 80s: the personal computer!




Consider applying for YC's Winter 2027 batch! Applications are open till November 2.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: