About OmniTwin

We made the twin
out of agents.

For thirty years, the network has been documented in software that humans had to operate. We built libraries — beautiful libraries — full of every IP, every rack, every VLAN. And we hired engineers to walk into those libraries, pull books off the shelves, and read them aloud to the network.

Then we built agents that could read for us. So we put MCP wrappers on the libraries.

But agents do not want libraries. Agents want runtimes. They want to wake up next to the data, act on it, and go back to sleep. They want identity, they want state, and they want to do their work in the space between the keystrokes — not in a separate window that opens a chat.

OmniTwin is what happens when you build the system of record and the system of action as the same thing. We did not bolt agents onto a network twin. We made the twin out of agents.

Agents do not want libraries.
Agents want runtimes.

Why we are building this

The founding story goes here. Why this problem, why this team, why now.

The founding story goes here. Why this problem, why this team, why now.

The founding story goes here. Why this problem, why this team, why now.

The team

Founder Name

Founder & CEO

Building the runtime your agents already wanted.

CTO Name

CTO

From NetOps to agent-native infrastructure.

What we are not

A DNS server. A CMDB. An AIOps platform. "AI-powered NetBox." We are a different architectural bet.

  • Not a DNS server
  • Not a CMDB
  • Not an AIOps platform
  • Not "AI-powered NetBox"

Get early access.

We are building in the open with a small group of network engineers. Join the list.

No spam. By signing up you agree to our Terms and Privacy Policy.