IPAM, but the addresses know what they are for.

Every IP record in OmniTwin carries its purpose, its owner and its history alongside the address itself. The design binds each write to an identity. When an agent touches a subnet, it is meant to act as a named principal with a delegated identity, shown as agent:reconciler (acting as: maya@acme.com) in the illustration. Agents are in development, so that example is illustrative.

The aim is an IPAM with an audit trail, reversibility on allocations, and agents that propose conflict resolutions instead of opening a ticket. VLAN objects follow the same identity model. Subnets are meant to know their purpose, their owner, and the last actor that touched them.

An address earns its meaning in stages. This is how one record picks up its context, and where that context stops today.

What an address carries

Five stages. Four are wired. Impact tracing through the graph is planned.

  1. Wired

    An address is taken from a prefix inside a tenant's address space, under a lock so two requests cannot take the same one.

  2. Wired

    The record holds its purpose, its owner and the site it belongs to, not just the number.

  3. Wired

    The database binds it to a tenant, so another tenant cannot see it.

  4. Wired

    When a DHCP lease touches the address, the record updates and the dependent DNS name is marked as needing work.

  5. Planned

    Tracing what depends on an address through the graph, for impact questions, is planned. Topology queries over imported data are not available yet.

  • Identity-bound writes on every allocation
  • Audit log designed in, not bolted on
  • Agent-proposed conflict resolution (in development)
  • VLAN, subnet, and IP all in one object graph

The ⌘K command bar: two modes, one input (in development).

Type a CIDR block or hardware keyword - 10.0.0.0/24, gi0/1 - and the bar is designed to stay deterministic: instant typeahead, no AI involved. Start with an operational verb - Find all unused /24s in prod-east, Allocate a /28 for the new k8s cluster - and the bar is designed to become an agent prompt with streaming results. Agent mode is in development.

One input field. Two behaviors. The design tells the engineer which mode they are in before they press enter.

Server streaming response (illustrative) json
[
  { "type": "agent_status",    "body": "searching the twin..." }
  { "type": "data_chunk",      "body": { "matches": 3 } }
  { "type": "agent_tool_call", "body": { "fn": "allocate_subnet" } }
  { "type": "final_result",    "body": { "committed": true } }
]

Ctrl + ~ opens the agent telemetry drawer (in development).

DCIM with drift detection as a first-class signal.

Drift detection is in development. Everything in this section describes the design, not what runs today.

OmniTwin's Canvas renders your physical and virtual infrastructure as a live object graph. Every rack, device, port and interface is a node in the graph, connected to the things around it. When the real world diverges from the twin, a cable gets moved, a device is reconfigured, a lease expires, the Canvas is designed to mark it.

The goal is for drift to be a signal rather than a next-morning report. The planned one-click reconcile would queue an agent action, let you review the delta, and commit the fix with identity attribution.

The agent would surface drift, propose the action, and wait for the human to commit it. Identity is bound to the action - not to the chat window.

  • Canvas: live object graph of physical and virtual infra
  • Drift detection as a signal, not a batch job (in development)
  • One-click reconcile with delta preview (planned)
  • Every fix attributed to agent and delegated human (planned)

The Universal Importer.

The goal is to get an export from the DDI tool you run today into a working twin. What ships today is a DCIM bundle importer, run as an operator CLI (see the CLI reference). Readers for native Infoblox NIOS, BlueCat, phpIPAM, and CSV exports are not available today.

The design is for the Importer to validate, normalize, and map every record, surface conflicts with a suggested resolution, and wait for your approval before writing. An automated, agent-driven import is in development.

  • DCIM bundle import via the operator CLI (available)
  • Native Infoblox NIOS, BlueCat, phpIPAM, CSV readers (not available yet)
  • Conflicts surfaced for approval before writing (design goal)
  • Agent-driven import (in development)

Five surfaces over the same twin.

The three problems above are all worked through one live model of your estate, and these are the surfaces you reach it by. Each one says plainly whether it ships today.

Find the hosts nobody wrote down.

A sweep reads the estate directly rather than trusting the record of it, then reports the three numbers that matter: what answered, what the IPAM already knew about, and the gap between them.

In development
  • Addresses swept 65,534
  • No record anywhere 47
discover design preview
$ omnitwin discover --subnet 10.42.0.0/16 --probe icmp,snmp,arp
✓ sweeping 65,534 addresses  [████████████████] 100%

  responding            1,284
  already in IPAM       1,237
  undocumented             47

$ omnitwin discover adopt --undocumented --dry-run
✓ 47 hosts would be written to the twin
✓ 0 collisions with existing records

$ _
10.42.0.0/16 1,284 responding

Not just different. Different by design.

Legacy DDI
OmniTwin
Architecture
Monolithic frameworks. Static registry, no real-time reactive tier.
Go control plane and Rust math engine, connected over gRPC.
Data ingestion
The discovery engine is open source and difficult to set up and manage.
Discovery is not built yet. Bulk DCIM bundle import ships today through the operator CLI.
Drift detection
Reactive dashboard. A human must click to accept, deny, or fix every discrepancy.
Drift detection is in development. The design shows drift as a line on the canvas with a one-click reconcile that logs identity, intent, and result.
SSO / SAML
Premium IAM features are gated behind expensive tiers.
SAML 2.0 with group mapping is included from Pro, not reserved for an enterprise contract.
Visualization
Add-on graphical UI rendering a relational dataset. Slow at enterprise scale.
Graph database as the topology layer, designed to render large active node sets.
AI capability
Natural-language query layer wrapping a third-party LLM.
Agents are in development. The design has them live inside the twin with persistent state and identity-bound action.
Air-gap deployment
Self-managed solutions like SolarWinds are complex to set up and manage.
Single-binary Iron Vault profile. No external dependencies. (Roadmap)
Buyer
CIO with a procurement team. Six-figure annual contract floors.
Engineer with a credit card for the entry tiers. Pro and Scale go through Contact Sales.

Get early access.

We're onboarding the first teams now. Join the list and we'll reach out when your slot opens.

No spam. No sales calls. By submitting you agree to our Terms and Privacy Policy.