You mention you had 100K users - I'm assuming those are paying users. Could they not keep using the product (especially if they've already onboarded)? Or are there significant ongoing costs beyond hosting?
You have a product bringing in $12 million per year (EDIT: I misread the profit remark originally, apologies to Kiro), and you can’t be bothered to do basic security updates?
> it's just a matter of time before it gets hacked but no big deal. If shit really hits the fan I will just shut it down.
You’re basically waiting to get hacked and your response plan is to just shut it down? And turn off $12 million in annual revenue because you didn’t feel like applying security updates?
Are you sure you mean $1 million per month in revenue? Because this doesn’t make any sense at all.
If this is true and accurate, you can at least see why this wouldn't apply to virtually anyone else running a high-profit software app, right? Especially not something like Friday.app which includes customer data.
Otherwise you're right. I simply can't be bothered and I don't even have access set up to the server on my current machine.
Me- Look a multi-gazillionaire!
Kiro - The profit is miniscule!
Me- They has spoken!
1M is thousand 1MM is million
https://gettingpeopleright.com/resources/what-does-m-and-mm-...
taking a guess that your app is an API wrapper of some kind? the $ you move is basically through your account from customer to service provider on each call and you charge some low flat rate per month for access?
That really depends on the product and how you built it. With platforms like Google App Engine or Heroku, there's no infrastructure to take care of and the only thing you have to patch/update is your own code. Customer support can be an issue, but some products are naturally self-service. Or cheap enough that there's no expectation of quality support.
I do think you need to plan for this sort of thing if you want to be able to walk away (even for a short vacation). If your natural inclination is to start with k8s, you're going to need ongoing devops work in perpetuity.
Definitely not. A company of that size with 100K paying users (so like $10M+ ARR) would be considered wildly successful. In their case it was probably a tiny tiny fraction of that.
Wyze did this recently with their subscription, which they let you pay as little as $0 for. They forced anyone who didn't subscribe onto a lower tier, which only stored still images instead of videos in the cloud.
I believe for that reason, for some founders it is, "you either die a hero or...."
If you use something for free, dont be surprised if it isnt there tomorrow.
Not needing to tend to a project you no longer find interesting (or view as a failure) is very liberating.