Everything you need
to get moving.

Guides, references, and deep-dives on DDI concepts and OmniTwin's agent-native architecture. Start with a quick start or go straight to the API.

Know your agents.

Each agent has a defined job, trigger, and scope in the design. No agent is wired into the running service today, and every card below carries its status. The one capability here that ships is the what-if preflight check, which is ordinary code and not an agent.

Scout Agent

Planned

Automated network discovery & sensing

Device discovery is not built yet. The design is for Scout to scan your subnets, detect active hosts, and infer device types, so the twin can be populated without manual entry, on a schedule or on demand after a provisioning event.

When to use

Intended for day-one onboarding and post-change verification, once it exists.

Architecture →

The Polyglot

Partly available

Vendor data translation & migration

Bulk import of a DCIM bundle works today through the operator CLI. The Polyglot agent, which would automate import and translate exports from other DDI tools such as Infoblox, BlueCat, and phpIPAM, is in development.

When to use

Bootstrapping a twin from an existing export. Today, use the operator CLI for DCIM bundles.

CLI reference →

Truth Seeker

In development

Auto drift detection

Drift detection is being built and is not wired into the running service. The design is for Truth Seeker to compare the state recorded in your twin against what Scout observes on the live network, and flag divergence. It depends on Scout, which is planned.

When to use

Intended for environments where unauthorized or undocumented changes are a compliance or operational risk, once it is available.

Architecture →

The Safety Net

Available

What-if preflight check (not an agent)

A what-if preflight check ships today as ordinary code on a tenant route. It is the one capability in this catalogue that works now, and it is not an agent. Wiring it into an agent that gates changes automatically is in development.

When to use

Before a planned change to DNS zones, DHCP scopes, or IP allocations, to see the effect before you commit it.

API reference →

The Architect

Planned

Auto-planning for network changes

The design is for The Architect to take stated intent, such as "I need a /24 for the new data center pod, routable from the management VLAN", and propose an allocation plan: subnets, VLAN IDs, DNS zones, DHCP scope boundaries, within your existing topology and policy constraints.

When to use

Intended for new site buildouts and greenfield addressing work, once it exists.

Architecture →

The Hands / The Closer

In development

Full closed-loop automation

Not wired into the running service. The design is for The Hands to stage a planned change and The Closer to apply it across DNS, DHCP, and IPAM, with an audit trail and a way to roll back.

When to use

Intended for environments where human-in-the-loop execution is the bottleneck, once it is available.

Architecture →

The Signal

Planned

DNS / DHCP telemetry & anomaly detection

The design is for The Signal to watch DNS query volume spikes, DHCP pool exhaustion rates, and rogue DHCP server behaviour. IPAM shows you static subnets. The Signal would watch the dynamic DDI traffic moving through them.

When to use

Intended for where dynamic traffic patterns, not static records, are what actually breaks.

Architecture →

Rack Master

Planned

DCIM physical layout planning

The design is for Rack Master to take a physical hardware manifest and propose patch panel wiring, rack unit placement, and power phase balancing in the visual canvas.

When to use

On demand when provisioning new rack space, in place of manual drag-and-drop DCIM planning.

Architecture →

The Audit

Planned

Compliance & zero-trust governance

The design is for The Audit to scan the topology graph for orphan IP records, unallocated active ports, expired TLS certificates on DNS endpoints, and dual-homed devices violating isolation boundaries.

When to use

Intended as a scheduled audit or a pre-compliance check, once it exists. It would not make you compliant with any framework by itself.

Architecture →

Open-standards DDI and the twin concept.

What is open-standards DDI?

DDI stands for DNS, DHCP, and IP Address Management - the three control-plane services that underpin every IP network. Open-standards DDI means those services are built on published RFCs and open protocols rather than proprietary vendor formats. Your data is portable. Your tooling is interoperable. No lock-in.

OmniTwin's schema tracks every IP prefix, address, DNS zone, record, DHCP scope, and lease against the open standard definitions, so the data model is not tied to one vendor's format.

Why open standards matter operationally

Proprietary IPAM formats create migration friction and API inconsistency. When your DNS server speaks one schema and your IPAM speaks another, reconciliation is a human job - which means drift is a human problem. Open standards collapse that gap: one schema, one source of truth, one set of automation primitives.

The twin concept

A network twin is a structured representation of your network's state - every address, every record, every lease - maintained in software. The twin is not a backup or a report. It is designed to be the operational surface that agents act on. Reconciling it against the real network is in development.

The agents described above are in development. The design has them operate on the twin directly rather than on a separate system that syncs back: drift is marked in the twin, changes are planned against the twin, and applied changes are committed to the twin and to the network in the same operation. The twin is the runtime, not the record.

Questions? Get in touch.

Can't find what you're looking for, or have a question about a specific agent or integration? The team reads every message.

Contact the team →

We read every message.