Live data from Hacker News

The architecture behind a one-person tech startup

anthonynsimon.com

331–334 of 334 posts

Re: The architecture behind a one-person tech startup

#331
I run a one-person SaaS company supporting three products. One is an iOS and Android all-local storage app so that costs me nothing to run. I have two projects running on Django sharing the same RDS DB. I can support two apps with just a single EC2 each. One runs docker containers. The other I did not dockerize yet. For me, the total costs are about $40/month. I have looked at Netlify and other “easy options” but they double or more my costs due to their costly basic tiers.

Re: The architecture behind a one-person tech startup

#332
post #36

For my typing SaaS, I found firebase hosting/realtime DB a ginormous time saver. And since it hasn't taken off (and probably won't ever), it just costs me a pennies a month since I'm under their free limits, plus the domain.

But you should be careful if it actually does takeoff. Firebase is freaking amazing, but the pricing can get crazy expensive.

That is a problem I'd love to have.

Re: The architecture behind a one-person tech startup

#333
post #61

I have done with before, ran and one man b2b saas platform with 30clients from around the world. Infrastructure was the easiest part. We where processing roughly 100million messages a day, about 5 nodes. Monitoring was good, application performance tracking was good. Business ran for close to 7 years, making about 1.3mill a year on an average year.

Care to elaborate on the use of past tense? I.e.: are you no longer in business, sold it or no longer running it solo?

Yes, I no longer have the business. It got harder and harder to compete with larger players as the market begin to attract more players. I sold of the business to a larger company (just contracts and not tech).

Re: The architecture behind a one-person tech startup

#334
post #230
post #61

I have done with before, ran and one man b2b saas platform with 30clients from around the world. Infrastructure was the easiest part. We where processing roughly 100million messages a day, about 5 nodes. Monitoring was good, application performance tracking was good. Business ran for close to 7 years, making about 1.3mill a year on an average year.

What was the hard part?

Hard part was support. Due to my clients being from around the world, sometimes they need help with items and expect a certain level of service, such and responses to support questions with in 24 hours or sometimes sooner. This required me to 90% of the time forward the inquiry to the a upstream vendor and that took time to collateral the right data to vendor (from the client's inquiry).

I did end up hiring a support personal for help to give me some breathing room on the weekends.

Post reply on HN