Hey Huzzler, I’m Daniel, co-founder at Oberum Technologies.

We built Oberum Network Builder because cloud networking still follows a slow loop. We found that architecture gets drawn in diagrams, then re-implemented by hand in Terraform/OpenTofu, mistakes pop up late as CIDR overlap, routing/reachability gaps, policy issues. We wanted a workflow where the design is the source of truth and the output is easily deployable.

Oberum Network Builder is a visual drag-and-drop network architecture platform that turns validated intent into repo-ready Terraform/OpenTofu.

What it does:

• Visual VPC/VNet topology design with typed connections and guided fields
• CIDR planning: overlap/containment checks before apply
• Routing validation: IGW/NAT logic, route tables, subnet reachability
• Semantic checks for common network architecture errors early in the cycle
• Preview/edit output, then export repo-ready Terraform/OpenTofu projects
• Reusable architecture templates: template library + module catalog
• Team workflow: role-based collaboration, version history, approvals, audit trails
• Git integrations and Terraform Cloud integration (plan/apply + run logging)
• Drift detection and rollback references for ongoing operations
• Self-hosted deployment option and AWS/Azure import for existing Terraform

Our Current focus:

Our current focus is tightening the team and collaboration experience so designing, reviewing, and shipping network IaC feels effortless across roles. We want to improve our shared workspaces, role-based access, version history, approvals, and audit-ready change tracking from design through export and runs. We’re also working towards expanding drift detection and rollback references so teams can quickly see what changed in Terraform/OpenTofu networking, understand the impact, and recover safely. Something else we're taking a look at is making templates and modules more reusable across teams and client environments. We want to create standardized architecture patterns that our users can clone, adapt, and deploy repeatedly without rework.

For those experienced in designing and building network architecture, i'd love to hear your experience on the following:

• When you design networks, what do you document first: subnets, routes, or security boundaries?
• Which validations are must-haves for you (CIDR, routing, reachability, IAM/DR, other)?
• Drift: how often do you see it in networking stacks, and what typically causes it?
• For reusable network patterns, do you rely more on modules, templates, or internal golden repos?

We're really excited to hear your thoughts and chat with anybody currently working on or interested in cloud networking.