Glossary

Available Limited beta

Definitions of the networking terms and OmniTwin terms used across this site, with the build state of each OmniTwin capability stated in the definition.

Back to Developers

OmniTwin is a DDI platform: it manages DNS, DHCP and IP address space together, and keeps a live model of the network. Some of the words below are industry standard. Others, such as intent store, reality store and drift, are how OmniTwin names its own design.

Where a term names something that is not built yet, the definition says so.

  • Available 5 items Works today in the private beta.
  • In development 4 items Being built. Not callable yet.
  • Planned 1 item Designed, not started.

Network fundamentals

Industry terms, defined without reference to any product.

DDI

Also: DNS, DHCP and IPAM
DDI is the combined practice and tooling for DNS, DHCP and IPAM: the services that name hosts, hand out addresses, and record who holds which address. The three are managed together because a change to one, such as adding a subnet, usually needs matching changes in the others. Traditionally that means one vendor suite or several tools kept aligned by hand.

DNS

Also: Domain Name System
DNS is the distributed naming system that maps names to records, most often a hostname to an IP address, so clients can find services without knowing addresses. Authoritative servers hold the records, and resolvers cache them for a time each record sets. See forward and reverse DNS for the two lookup directions.

DHCP

Also: Dynamic Host Configuration Protocol
DHCP is the protocol a server uses to give a device an IP address, along with settings such as its gateway and DNS servers, when the device joins a network. Each grant is temporary and is called a lease. OmniTwin ingests signed lease events from DHCP servers today.

IPAM

Also: IP address management
IPAM is the record of which IP address space exists, how it is divided into prefixes and subnets, and what is assigned to whom. Without one authoritative record, ranges overlap and addresses collide. In OmniTwin this record lives in the intent store.

DCIM

Also: Data center infrastructure management
DCIM is the inventory of physical infrastructure: racks, devices, ports, cables and power. It answers where a device is and what it connects to, which IPAM does not. OmniTwin loads DCIM site data through its operator CLI today. That imported data does not yet reach the reality store, so topology queries do not see it.

CIDR

Also: Classless Inter-Domain Routing
CIDR notation writes a block of IP addresses as a base address and a prefix length, as in 10.0.0.0/24, where 24 is the number of leading bits that are fixed. An IPv4 /24 holds 256 addresses, and each bit removed from the length doubles the size. It replaced the old fixed class A, B and C boundaries, and is how a Prefix is written.

Prefix

A prefix is a block of contiguous IP addresses written in CIDR notation, such as 10.20.0.0/16. A prefix can contain smaller prefixes, which is how address space is divided and tracked. A Subnet is a prefix that is in use as a network.

Subnet

A subnet is a subdivision of an IP network: a range of addresses that share a Prefix and can reach each other directly, without passing through a router. Allocating a subnet means choosing a block from a larger prefix that overlaps nothing already assigned. OmniTwin allocates subnets over gRPC today.

VRF

Also: Virtual routing and forwarding
A VRF is a separate routing table inside one router, which lets the same address range exist in two isolated networks without conflict. Because of this, 10.0.0.0/24 in one VRF and 10.0.0.0/24 in another are different networks. Address records that omit the VRF can look like duplicates when they are not.

DHCP lease

A DHCP lease is the time-limited grant of an IP address to a device by a DHCP server. The lease ties a device hardware address to an IP address until it expires, and the device must renew it to keep the address. Lease events are the signal OmniTwin ingests today, through a signed webhook.

PTR record

Also: Pointer record
A PTR record is a DNS record that maps an IP address back to a hostname. It is stored under a reserved reverse zone, with the address octets written in reverse order. Log tools, mail servers and troubleshooting commands use it to turn an address into a name.

Forward and reverse DNS

Forward DNS resolves a name to an address, using A and AAAA records. Reverse DNS resolves an address to a name, using PTR records. The two are maintained separately, so they can disagree, and a name whose reverse record is missing or stale is a common kind of Drift.

Tenant

A tenant is one customer or organizational unit whose data must stay separate from every other tenant sharing the same system. Every record belongs to exactly one tenant. In OmniTwin the tenant is named by the caller's credential, not by the request body.

Row-level security

Also: RLS
Row-level security is a PostgreSQL feature in which the database filters rows by policy on every query, so a session can only see the rows it is permitted to, even if application code forgets a filter. It does not constrain superusers or roles that can bypass it. OmniTwin enforces Tenant isolation this way, under a database role that cannot bypass it.

Multi-tenancy

Multi-tenancy is one deployment serving many tenants while keeping their data isolated. The alternative is a separate deployment for each tenant. Isolation can be enforced in application code or in the database, and enforcing it in the database with row-level security holds even when the application has a bug.

OmniTwin vocabulary

Terms OmniTwin defines for its own design. Each states what is built.

Network twin

In development
Also: Twin
A network twin is a live model of what the network is, kept current from events rather than from manual entry. OmniTwin builds its twin from the intent store and the reality store. Today the events it learns from are signed DHCP lease events, and device discovery does not exist, so the twin does not yet see the whole network.

Intent store

intent Available
The intent store is the relational database holding what should be true on the network: allocations, policy and ownership. It runs under ACID guarantees, so a change either commits whole or not at all. It is one half of the twin; the other is the reality store.

Reality store

reality Available
The reality store is the graph database holding what is true on the network right now: topology, connections and observed state. A graph suits it because paths such as port to switch to VLAN to scope to DNS record are traversals, not joins. Imported DCIM data does not reach it yet.

Drift

intentreality
Drift is the difference between what the intent store says should be true and what the reality store shows is true. A lease on an address that was never allocated, or a DNS name with no matching assignment, is drift. Finding it automatically is drift detection, which is not finished.

Drift detection

In development
Drift detection is the comparison of the intent store against the reality store, flagging where they diverge. In OmniTwin it is in development and does not run today. Until it does, Drift exists but nothing reports it.

Pre-flight check

Available
Also: What-if check
A pre-flight check tests a proposed change against the twin, in memory, before production sees it. It ships today as ordinary code on a tenant route, not as an agent. It reports the blast radius of the change so it can be reviewed before anyone applies it.

Blast radius

In development
Blast radius is the set of things a change would affect, traced outward from the thing being changed. In OmniTwin the term describes what the reality store is for: following connections such as a subnet to the devices that hold addresses in it. Tracing a change through the graph is in development, and imported DCIM data does not reach the graph yet, so the trace cannot see it.

Closed-loop automation

Planned
Closed-loop automation is a cycle in which the system discovers a problem, plans a fix, simulates it, gets approval, executes it, and confirms the result, without a person driving each step. OmniTwin has not built this. Device discovery does not exist and none of the four planned agents is wired, so every step beyond the pre-flight check is still a person's job.

Agent-native

In development
In OmniTwin, agent-native has a narrow meaning: software agents act on the twin under an approval gate and a bound identity. The credential names the Tenant, and a human approves a write by default. The site does not use the term in its looser sense, and none of the four agents is wired yet, so this describes the design.

Identity-bound write

Available
An identity-bound write is a change whose Tenant is taken from the caller's credential rather than from the request payload, so a caller cannot write into another tenant by naming one. That much is enforced by the database today. Recording which human or agent principal made each change is part of the same design and is in development.

Idempotency key

Available
An idempotency key is an identifier the sender attaches to a request so that repeating it has the same effect as sending it once. OmniTwin uses the event id, paired with the Tenant, so a retried lease event is recorded once. The sender creates the id, not the server, because after a timeout the sender cannot know whether the first attempt landed, and only an id it already holds lets it resend safely.

Build state

The three words this site uses to say whether something works.

Wired

Available
Also: Available
Wired, shown on reference pages as available, means the capability works today in the private beta. It is built, deployed and callable, and a reader can rely on it as described.

In development

In development
In development means the capability is being built and is not callable yet. It is real work in progress, so the description may still change before it ships.

Planned

Planned
Planned means the capability is designed but not started. It describes intent, and nothing on this site should be read as a commitment to a date.

Get beta access

Everything marked available is in the limited beta.

Join the beta