Design networks visually. Generate deploy-ready Terraform (our Oberum Network Builder story)

Hey Indie Hackers — I’m Daniel, co-founder at Oberum Technologies. I’m here to build in public, learn from other builders, and share what we’re figuring out as we go.

Why we started Oberum Network Builder:

We kept seeing the same workflow pain in cloud networking: architecture lives in diagrams, implementation lives in Terraform/OpenTofu, and the risky issues show up late. CIDR overlap/containment problems, routing and reachability gaps (IGW/NAT, route tables), and policy concerns (IAM and DR) are often discovered during review, during plan/apply, or after something breaks. The feedback loop is expensive, slow, and hard to standardize.

What we’re building:

Oberum Network Builder - design networks visually. generate deploy-ready Terraform.

It’s a visual drag-and-drop network architecture platform that turns validated intent into repo-ready Terraform/OpenTofu for cloud network design.

Core ideas/features we’re focused on:

- Visual IaC / Network IaC: AWS VPC design and Azure VNet design on a canvas

- Typed connections + guided fields so invalid topologies are harder to create

- Semantic validation for Terraform networking before deployment incluiding: CIDR planning, Routing validation, IAM validation + DR validation

- Terraform and OpenTofu generator: preview/edit output and export repo-ready projects

- Reuse at scale: architecture templates, template library, module catalog

- Team workflow: role-based collaboration, version history, approval workflows, audit trails, run logging

- Git integrations and Terraform Cloud integration (plan/apply execution with run logging)

- Operations: drift detection + rollback references for Terraform networking

- Self-hosted deployment for regulated environments

- AWS/Azure import to bring existing Terraform HCL into a visual network design

- AI copilot that helps design architecture and writes code alongside you

Where we are + what I’m looking for:

We’re actively building and looking for a few design partners who do Terraform/OpenTofu for networking (platform teams, cloud/network engineers, consultants).

Two questions for the community:

1) If you’ve shipped network IaC, what are the top 3 “gotchas” you wish your tooling caught earlier (CIDR, routing, reachability, IAM, DR, something else)?

2) What “must-have” validations or guardrails would make a visual network IaC workflow a no-brainer for your team?

If you’re open to a quick chat, I’d love to learn from your workflow and share back what we learn as we iterate.

Product page: https://oberumnetworkbuilder.com/