5
3 Comments

How do you build cloud infrastructure if you’re not a DevOps expert?

I’m working on a tool called ArchFormation, and I’d love some honest feedback from people who actually build and deploy things.

The problem I’m trying to solve:
Many developers and small teams need production-ready cloud infrastructure, but don’t have deep DevOps experience. They either copy Terraform from blogs or spend a lot of time figuring out AWS services, IAM, networking, etc.

The idea:
An AI Infrastructure Assistant that suggests cloud architectures using pre-optimized Terraform modules. You can visually adjust every service on a canvas, review everything, and export Terraform code or deploy with an AI assistant, while staying in control.

I’m not trying to replace Terraform or DevOps, just make common architectures easier and safer to assemble.

Landing page (for context, not a signup push):
https://archformation.com/ai-infrastructure-assistant

Questions I’d genuinely love feedback on:

Is this a real pain for you or your team?

Would you trust an AI assistant if you can fully review and edit the infrastructure?

What would make this helpful vs “I’ll just do it myself with AWS + Terraform”?

Happy to hear critical feedback — I’m validating whether this is worth building.

on December 14, 2025
  1. 1

    I think the “fully review and edit the infrastructure” part is critical.

    A lot of hesitation around AI-assisted infrastructure isn’t just generation quality — it’s operational trust over time.

    People increasingly want:

    • reviewability,
    • predictable runtime behavior,
    • traceability,
    • and confidence that the system won’t silently drift operationally after deployment.

    Especially once AI moves from suggestion into infrastructure orchestration or long-running operational assistance.

    Interesting direction.

  2. 1

    This is a real pain. I’ve seen small teams lose weeks on IAM/networking decisions that only surface as problems later. Out of curiosity, what part has been most painful so far for you personally — IAM, networking, or keeping things production-safe?

  3. 1

    Thanks for this! The way you break down infrastructure decisions without deep DevOps experience feels super practical.

    When I’ve built SaaS products, I’ve also found choosing which parts of infra to own vs outsource early on makes a huge difference in focus and cost.

    Did you find any specific patterns or rules for deciding when it was worth learning something new yourself vs using a managed service?