Ask HN: Series A/B startups, what's your infra setup?

I'm currently at an early stage startup around the series B mark, and we're currently using a PaaS, like Heroku or Fly.io, to host our infrastructure. However, while these solutions have served us to a certain extent, we're hitting limitations in terms of features, integrations, hardware options, and overall system reliability. For some context: we run a NestJS monolith application, use RabbitMQ for background tasks, Redis for rate limiting, and have an AI microservice for ML models. Our databases are managed Postgres and Google Firestore, plus we use GCP Cloud Functions for some legacy systems.

We're considering moving to native cloud solutions on AWS or GCP but are concerned about the feasibility of the setup for our volume. Although Kubernetes is an option, the idea of managing a cluster seems daunting. So, we're exploring intermediate services like Fargate, Cloud Run, or Porter, which provide more advanced features while still being somewhat managed. Any recommendations?

I heard FB config is decent

The startup I work for is getting off a similar PaaS and evaluating Porter too; we really like the idea of the white glove service they have and flexibility across multiple clouds but was worried about general overhead in someone on the team needing to manage it, whereas the PaaS was so hands off (even if it was a black box). Curious what you and your team end up deciding on!

Another option you might like is Flightcontrol[0]. It's similar to Porter, but newer and aims to make all the best AWS services as easy as PaaS. And unlike Porter, it doesn't charge more for horizontal and vertical scaling.

Today, the server deployments use Fargate, and are truly hands off just like PaaS. Soon we're launching ECS+EC2 support which will let you customize the EC2 instance type, use GPUs, and leverage reserved instances. ECS doesn't offer some advanced k8s features, but it's 80% or more of the benefit in an easier to use, cheaper package.

We commonly see Series A & B companies migrating off PaaS to Flightcontrol + AWS because they can keep the same workflows while gaining more reliability, control, and flexibility.

I'm cofounder, CEO. Let me know if you have any questions.

[0] https://www.flightcontrol.dev/

I've run / worked on two 7-8 figure early stage products on a handful of Heroku dynos, a medium sized Postgres, and RabbitMQ + workers for background stuff. Also cron jobs, ElasticSearch, and a few other things. You can get pretty far with basic infra if you don't have demanding computational needs. I really feel like making devops complicated and using complex setups on AWS/GCP is unnecessary for many startups.

I'm currently running a few small projects on Render and migrating one from Heroku to Render to save a few bucks.