Introducing OmniTwin: Reimagining Infrastructure Control Planes from First Principles

Software development has spent the last two decades building an immutable safety net. Modern developers do not push application code directly to production servers without passing through automated testing pipelines, isolated container environments, and strict syntax validation checks. If a single line of code is broken, the continuous integration and continuous deployment (CI/CD) pipeline rejects it automatically before it can impact a single user.

Yet, the critical network infrastructure that powers these very applications remains stuck with reactive scripting, static ledgers, and blind trust. Much of enterprise network operations (NetOps) still works this way. Engineers copy configuration blocks from text templates, paste them manually into command-line interfaces (CLIs), or trigger heavy, sequential infrastructure automation scripts that lack deep, live topology awareness. One mistyped subnet mask, a rogue routing leak, or an undetected overlapping prefix can silently take down an entire enterprise fabric.

We founded OmniTwin to fix this. Network engineering should have the same determinism, safety, and continuous validation that software engineering has. We are building Agentic NetOps: a Network Digital Twin engine that validates changes before they reach a device.

The Failure of Modern Network Automation

The networking sector has historically been fractured across three flawed technological archetypes:

  • Static Registries & IPAM Suites: Passive ledgers of intent operating on slow, synchronous, legacy frameworks. They act as an inventory system without a real-time data tier, automated provisioning, or built-in math acceleration. They are rigid, tied to expensive licensing, and have no hook for AI reasoning or programmatic scaling.
  • Brittle Orchestrators & Legacy SDN: Enterprise monoliths that make engineering teams build rigid, sequential visual workflows by hand. They treat multi-vendor networks as a black box and abstract safety through operational bottlenecks, like forcing a senior infrastructure engineer to log in at 3:00 AM to manually click an "Approve" button.
  • Reactive Monitoring Tools: Traditional infrastructure tools excel at pushing configurations, but they are fundamentally blind to the downstream systemic reality of those changes. When you deploy a script via legacy tools, you are essentially launching an instruction into a void. The tool verifies that the command was sent successfully, but it cannot tell you whether the command will cause a routing loop three hops away.

Monitoring tools only tell you that something broke after the damage is already done. The industry has accepted this reactive posture as the standard cost of doing business, but it is an architectural flaw. OmniTwin is built to validate a change before it ships instead.

How OmniTwin Changes the Engineering Loop

OmniTwin does not only store your configurations; it validates changes against a computational twin of your infrastructure before they run. The twin ties your operational intent to what the network is actually doing.

The architecture processes each change through three stages before anything approaches a physical switch:

1. Mathematical Validation

Rust-Based Bitwise Logic: Using a deterministic math engine written in Rust, OmniTwin checks each proposed address allocation, multi-tenant boundary, and prefix split with bitwise operations. These checks show whether a change creates an address overlap or crosses a tenant boundary.

2. Safe Isolation via Graph Sandboxing

Go-Based Control Plane: When a configuration shift is requested, the Go-based control plane forks the affected network subgraph into an isolated, in-memory transactional sandbox. Proposed modifications run only in this sandboxed clone first, isolated from production APIs.

3. Pre-Execution Path Tracing

Path-Traversal Simulation: Within the sandbox, the platform runs path-traversal algorithms to simulate actual data packets moving across the proposed network fabric. The platform queries the sandbox: "Can packets from the unsecure Guest Wi-Fi zone reach the database zone under this new configuration?" If the simulation records a policy or logical violation, the change is blocked. If it passes, the change is cleared to proceed. Simulation tests the model of your network, so it is only as accurate as the data in the graph; it lowers risk and does not remove it.

Architecture and Stack

We are a small engineering team, and we designed this architecture to move infrastructure management from reacting to outages to checking changes first. OmniTwin runs as a single runtime pod. A Rust core handles the bitwise logic and an asynchronous Go control plane handles multi-tenant routing.

We bind relational intent directly to topology reality with a three-part data stack:

Technology ComponentOperational Role inside OmniTwin
PostgreSQL 17 & pgvectorHandles relational intent. Semantic natural language search over it is in development.
Graph DatabaseMaps physical and logical topology reality, giving the control plane a spatial model of the network fabric.
Drift DetectionCompares runtime state against the validated digital twin to flag drift and telemetry anomalies. In development.

Instead of forcing systems engineers and data center managers to govern rogue scripts with slow human approval workflows, OmniTwin checks each change with a network simulation before it runs.

Where We Are

We are in active development, refining the systems that allow critical infrastructure to be simulated, validated, and managed automatically. We are not interested in creating another surface-level dashboard that simply reflects existing, broken static data; we are building an engine that checks network intent against network state.

We are opening an early access waitlist for network engineers, data center managers, infrastructure engineers, and systems engineers who want to move beyond fragile scripts. If you want a control plane that validates changes before deployment, join the early access tier.