A twin that acts.
Three things OmniTwin does on day one. Not a feature list - the three problems we built it to solve.
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.
- 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.
- Wired
The record holds its purpose, its owner and the site it belongs to, not just the number.
- Wired
The database binds it to a tenant, so another tenant cannot see it.
- Wired
When a DHCP lease touches the address, the record updates and the dependent DNS name is marked as needing work.
- 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.
[
{ "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
$ 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
$ _ An address is arithmetic, not an opinion.
The math core walks the pool in order and returns the first block that fits. No spreadsheet, no reviewer, no second answer on a second run. This pane prints what the arithmetic returns for the pool below, computed at build.
Math core ships today- Blocks examined 11
- Usable hosts returned 62
$ omnitwin alloc next --pool 10.42.0.0/16 --size /26
policy first-free · deterministic · no agent in the path
held 704 addresses across 4 reservations
examined 11 candidate blocks in order
✓ 10.42.2.128/26 free · 62 usable hosts
$ omnitwin alloc reserve 10.42.2.128/26 --for k8s-pods
✓ reserved · written to intent · audit logged
$ _ Name the gap between intent and reality.
Two stores answer the same question: the one that holds what you meant, and the one that holds what the network is doing. Drift is every record where those two disagree, listed rather than summarised.
In development- Records compared 41,908
- Diverged from intent 12
$ omnitwin drift detect --scope production
✓ comparing intent to reality [] 100%
! 12 of 41,908 records diverged
A app-7.prod-east 10.42.9.14 reality 10.42.9.40
A cache-2.prod-east 10.42.9.21 reality absent
PTR 10.42.7.0/24 present reality absent
… 9 more
$ omnitwin drift reconcile --plan drift-8f2a
! 12 changes staged · awaiting one approval
$ _ Fail the push, not the network.
A proposed change runs against a branch of the twin in memory before production sees it. Overlapping CIDRs, exhausted scopes and broken delegation are caught by hard rules, so the push fails instead of the estate.
Ships today- Checks run 4
- Conflicts blocked 1
$ omnitwin apply plan.tf --simulate
cloning twin branch sim/8f2a · in memory · nothing shipped
✓ vlan 340 delegation resolves
✓ dhcp scope headroom 38%
✓ zone prod-east.internal signs clean
✗ 10.128.0.0/20 overlaps sn_01HX7
blocked before production · 1 conflict
discarding branch sim/8f2a
exit 1
$ _ Signed at the edge, before it is trusted.
Every lease arrives with a signature from the server that issued it and is checked before it reaches the twin. The tenant it belongs to is enforced on the same path, not after the fact.
Signed ingestion ships today- Signature scheme ed25519
- Unsigned accepted 0
$ omnitwin audit tail --tenant acme --limit 4
14:02:11 lease.ingest dhcp-02 sig ✓ ed25519
14:02:11 lease.commit 10.42.7.31 ttl 3600
14:03:04 subnet.reserve 10.42.2.128/26 agent:maya
14:03:04 policy.check tenant-isolation pass
✓ 4 records · 4 signatures verified · 0 unsigned accepted
✓ every write attributable to a key, not a username
$ _ Not just different. Different by design.
Get early access.
We're onboarding the first teams now. Join the list and we'll reach out when your slot opens.