Bootstrapping codebases is always a cumbersome and time-consuming task.
→ Setting up a scalable and cost-optimized infra as code is hard and time-consuming (especially if it's your first rodeo)
If you don't spend the time upfront, you're gonna have a super hard time to evolve and maintain it across environments (e.g. staging and production)
→ Integrating and automating technologies is a time sink
Alarms, budgets, CI/CD, testing frameworks, linter, formatter, ... The time setting up each one of those piles up very quickly!
How does it work?
Select technologies (programming languages and cloud services) through an intuitive interface and get a barebones codebase (an empty src folder) with your complete stack and a fully automated development cycle.
Here's a prototype: https://buffet.stackforge.tech/
Looking for candid feedback and advice!
Thank you for your time =)
Just thought I'd point this out: When using high-level frameworks like Gatsby or Next.js, most of this is already handled for you. All you have to do is hit "deploy" on a platform like Vercel or Netlify and it's all handled for you.
Hi @nicholaschiang thanks for your input! They most definitely do, but:
I'd say our ideal customer would be a) tech startups that want to save 2-3 weeks of their developers' time when bootstrapping a project or b) incumbent companies that don't the know-how or time to implement it themselves.
Do you think that makes sense or is it a bit far-fetched?
Hmm, yeah. I can see how that would be useful. Things like Qovery do, however, give you direct access to your AWS resources (i.e. it just manages your account for you). And I'm sure something similar exists for Azure and GCP as well.
That's great, I didn't know about Qovery. Thanks a lot for your inputs, nicholas
Yeah, I just heard about it too. It's being made by a fellow IH who posted about it (on this site) a while back.
Cool idea, end to end build/deploy system including source code can be really challenging to get up and working unless you already are familiar with the stacks/process.
This would be interesting to me for trying to learn new tech stacks, and to easily compare/contrast.
Hi @acardenas, thanks a lot for the feedback!