Good suggestion, our company page is updated to include the founders
HN user
flybayer
RDS has been default private for probably 6 months or longer.
Would be better if it was IaC but with pre built "blocks" app, cache, etc, which you could easily customize
We are working on a major new product version that does exactly this ;)
Stay tuned, we’re working on the next version of Flightcontrol which is in this direction.
No, but we support cost budget alerts.
When did you try it?
There is no service limit on the free plan. It’s limited to a single user instead.
ECS is great and simpler than k8s. Flightcontrol[1] is an easy way to spin up and deploy to ECS clusters. (I'm a cofounder)
You might like https://www.flightcontrol.dev which makes it easy to deploy servers or Lambdas. (I'm cofounder)
Hi, you might like https://www.flightcontrol.dev which fully automates production infra in your AWS. So you get to use your AWS credits, and you can even pay Flightcontrol with your credits, so it'll be 100% free.
Flightcontrol is very popular for Next.js deployments on AWS
*I'm cofounder of Flightcontrol
The problem with typical PaaS is significantly less reliability, higher costs, and limited flexibility than AWS for example.
But of course AWS is a nightmare on it's own.
So you might like Flightcontrol [1] which provides a PaaS user experience on your own AWS, thereby giving you the best of both worlds.
This isn't answering your question, but you might also want to consider https://www.flightcontrol.dev. Here's a comparison with Porter: https://www.flightcontrol.dev/porter-alternatives
Fargate does not have cold starts like Lambda. There is always a container running, it does not scale to zero.
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.
Good to know, I fully support it!
I'm curious if this was after a failed funding attempt. I think we're going to see a lot more VC backed companies prioritizing profitability.
I think startups should use seed rounds to become profitable. It's the only way to secure your future. You can be profitable and grow fast. See Notion and Linear.
We use https://www.flightcontrol.dev to deploy to AWS Fargate with auto deploys, multiple environments etc (I’m cofounder of Flightcontrol)
AWS via https://www.flightcontrol.dev/
https://www.flightcontrol.dev is one that’s built on AWS
thanks for the feedback! All new website and product UI launching in a couple weeks, hopefully it will be more clear :D
But the overall, Flightcontrol works very similar to Heroku except it deploys to your own AWS account
https://www.flightcontrol.dev (I’m a cofounder)
https://www.flightcontrol.dev, easy deployment to AWS (I'm cofounder)
Depends on what parts of PaaS you like or not, but you might like https://www.Flightcontrol.dev which streamlines Fargate deployments. Also static sites, preview environments, etc. (I’m Flightcontrol cofounder/CEO)
You might like https://www.flightcontrol.dev, although you'd still want to set up GitHub actions for running the tests before deploy
https://Flightcontrol.dev is a relatively new one that provides a PaaS-like experience on your own AWS account
*I'm cofounder & CEO
Flightcontrol | Developer Advocate | REMOTE (overlap 10a-12p EST) | Full-time
Flightcontrol provides the deployment experience of a Platform-as-a-Service but without the limitations, since it uses your own AWS account.
We're a 5 person YC startup cofounded by the creator of Blitz.js. We’re intentionally building the most life-giving and fulfilling company possible.
Looking for our first devrel. Your high level goal is to grow “top of funnel” traffic through awareness and education, with written content as the foundation.
Full description: https://jobs.flightcontrol.dev/developer-advocate
Blitz actually came first, so trpc is an alternative implementation of RPC.
Blitz auth was developed at the same time as next auth, and takes a more imperative approach which allows you to build more custom auth flows.
Unless I'm missing something, Blitz RPC add's zero TS overhead. So the limitation will be the total amount of TS code you have which is not related to Blitz.
In simple terms: If you want to use GraphQL, use Redwood. If you want type safe client-server communication without GraphQL, then use Next.js + Blitz