I'm a solo dev working on both my own apps and a product as part of a small team. I'm interested to hear how others are running their apps?<p>- Self hosted on a VPS?
- Managed infrastructure like AWS, Fly, Render, Digital Ocean App Platform, GCP?
- Full-stack platform like Vercel, Firebase, Supabase?
Buy some used servers on eBay, at least 3 will do for redundancy, then get 2 internet connections. Set up another server to act as your opnsense firewall/router and bond the two internet connections together. Make sure to buy a pair of UPSs for power back up. Install kubernetes and rook ceph with about 12 hard drives (redundancy) then find a friend who can host another server for offside backups. Dont forget the tape drive system for your second media. Start deploying gittea so you can host your code. Use argocd so you can have a build system. Deploy dapr so you can host all of your microservices in a standard way. Deploy otel and alertmanager so you can hook it into the only cloud service you need: OpsGenie (don't forget to winge the whole time you use it)<p>That way you can write an article about how much cheaper self hosting is compared to the cloud and get your next round of investment.<p>On a serious note. The next startup I do I'm going to just use supabase.
Fully managed so I can spend my time on actually building features. In my case, AWS is my go to cloud, and even with a couple of thousand users, Lambda for compute, DynamoDB for database and SNS+SQS for eventing is costing me less than 5€ per month. Yes, there are risks with serverless if you get DDOSed or whatever, but it’s a risk I’m fine with, and can mitigate with gateways in front if necessary. And Lambdas are not locking me in to AWS since I’m running “full” ASP.Net apps in them, so hosting them on actual compute platforms is an easy switch.
Rancher k8s + Helm charts for HA services (Redis Sentinel + Patroni Postgres). Nightly snapshot backups + streaming Postgres WAL segments to S3.<p>I’ve never understood the k8s hate. We have been running this for a few years and it is rock solid. We can bring the entire cluster up on any provider anywhere in the world in about an hour. The DR is great.
Self-hosted on a VPS is the first option for me, it's cheap and you have total control on everything. It's valid in my case because I know my way through infrastructure and configuration, so a panel isn't too much gain.<p>You sometimes can even get those for free - <a href="https://free-for.dev/#/?id=major-cloud-providers" rel="nofollow">https://free-for.dev/#/?id=major-cloud-providers</a><p>For example, I have some (really) free instances on Oracle Cloud that I host pages, experiments, and so many things.
S3 buckets for the SPA's, AWS Lambda, API Gateway and EC2 for a MySQL instance. Some SQS to help with orchestration of the operational stuff. Have about 5k MAU and total cost barely breaks 40$ a month.<p>Chose this because it's the stack I'm super familiar with.
Hetzner + docker swarm can take you long way for a fraction of cost of any next alternative<p>And for a fraction of a mental burden and stress of the lightest k8s setup you can imagine
We have our own servers (mostly consumer pc parts) and run lxd to slice them up into vms/containers. Deploy to those using kamal and expose the web server port through cloudflare tunnels. With simple scripts to periodically compress and upload the storage volumes and database dumps to Google drive, most of our less critical apps cost about $0 to keep running. For the higher criticality apps, we also deploy them to Linux vms using kamal, but use a commercial service (linode).
Spoiler: Shameless plug, but might be helpful for people<p>I understand most of the commentators, as well as OP, are probably looking to not spend too much time and money on their hosting infra. While that makes sense in the beginning, there might be a point in your successful journey where you want to hand over your operation duties to someone skilled and focus on building software because your business starts depending on safe and well-maintained infrastructure.<p>If you're looking for something between Heroku and AWS (both in terms of pricing and scalability) but based on K8s, with direct access to skilled platform engineers and personal support, you might want to check out <a href="https://www.ayedo.de/cloud/" rel="nofollow">https://www.ayedo.de/cloud/</a>
For static web apps like my portfolio and blog[1], I use GitHub+Netlify.<p>I try to use AWS Lambdas as serverless backend as much as possible, for API products like [2].<p>If a server is absolutely required like running a Ghost blog/newsletter [3], I use AWS Lightsail mainly because I'm familiar with AWS in general and it offers generous free tier.<p>[1]: <a href="https://ivylee.github.io/" rel="nofollow">https://ivylee.github.io/</a><p>[2]: <a href="https://www.ycverify.com/" rel="nofollow">https://www.ycverify.com/</a><p>[3]: <a href="https://www.signalstalk.com/" rel="nofollow">https://www.signalstalk.com/</a>
Render has been a great heroku replacement. I thought I would miss the “add-ons marketplace” but it’s actually been fine. Costs are reasonable for our startup and they seemed to have fixed their odd Cloudflare downtimes of the past.
Docker on a DigitalOcean VPS. I've never been a fan of managed stuff, but then again I'm mostly coding for fun, not because it's the best use of my time.
This is not for a business, but I am working on a side project that uses node.js + sqlite and the entire stack will run on a single Lightsail instance ($5 per month)
So, I've found that a mix of VPS / Cloud is great for me.<p>I have VPSs with Ionos, they're cheap and for the rest its all over GCP, functions, scheduler, firestore, storage, CDN and Cloud run are convenient tools.<p>Namecheap for domains, feels reliable.<p>Maybe switching to Hetzner for VPS if I need bigger ones, feels reliable and good priced.
My setup is a digital ocean box with docker compose scripts and watchtower for deploys. All I have to do is push a new image and it will deploy in prod. Database is as aged Postgres cause that’s all that is really important. Cloudflare for the smaller services.
Currently using heroku for a backend server for an app I'm working on, in the past I've played with a lot of different options, but most of them are too complicated and expensive if you don't actually have paying users.
Netlify for the front-end, google cloud for extended storage and Akamai for hosting. Akamai is great as they are less customizable than AWS (which is a good thing if you don’t need extra config) and much less expensive.
Extremely happy with supabase here, it has mostly eliminated the need for a backend, letting me just focus on making valuable stuff for my users. I also ended up making my entire app realtime just because it was easier
Cloud offerings are incredible for small teams. Don't even bother trying to do your own thing until you can clearly articulate the savings and factor in the risks and costs.<p>Odds are you'll never need to move.
Hosted a few small but profitable web sites on Hostgator since 2005 - cheap and no need to worry about infrastructure beyond hosting files. Only problems have been wordpress sites getting hacked.
I try to stick to serverless rather than trying to manage any infrastructure<p>1) Google App Engine Standard. Datastore for DB.<p>2) For anything that won’t work with the above, then it’s Google Cloud Run
Render. Happy with it for now as a prototyping / MVP tool. Won’t be able to continue forever due to HIPAA requirements and not sure how it scales anyway.
Combination of labs, colo, and partnerships with other parties.<p>Varying types of platforms and degrees of control. Ansible is the most unanimous thing I can name