🏗️ Architecture on Deevnet Infrastructure Platform

Builder

Mon, 01 Jan 0001 00:00:00 +0000

Builder #

Purpose #

The builder is responsible for provisioning and configuring all substrate infrastructure.

Every Deevnet Infrastructure Platform site needs a way to be created from scratch:

How do you provision infrastructure when no infrastructure exists yet?

The builder answers this by providing:

A self-contained provisioning role
All artifacts needed for deployment
Automation to configure every substrate component
Authority transition from bootstrap to production

Design Principles #

Self-Contained — The builder carries everything needed to stand up a substrate: IaC/CaC definitions, OS images, network boot infrastructure, and Git repositories.

Network Segmentation

Mon, 01 Jan 0001 00:00:00 +0000

Network Segmentation #

Defines the network segmentation model for Deevnet sites.

Purpose #

Network segmentation divides each substrate into isolated broadcast domains with controlled routing between them. This provides:

Security boundaries — Limit blast radius when devices are compromised
Traffic isolation — Separate management, storage, and workload traffic
Operational clarity — Each segment has a defined purpose and trust level

Segment Model #

Each substrate implements nine segment types:

Addressing

Mon, 01 Jan 0001 00:00:00 +0000

Addressing #

Defines the IP addressing convention for Deevnet sites.

Addressing Convention #

Each site is assigned a /16 block from the 10.0.0.0/8 RFC1918 space:

Site	Address Block
dvnt	10.10.0.0/16
dvntm	10.20.0.0/16

The addressing pattern is: 10.{site_id}.{vlan_id}.0/24

The second octet identifies the site
The third octet matches the VLAN ID for that segment
Each segment subnet is a /24 within the site’s /16

This creates a predictable, self-documenting address scheme where any IP immediately reveals which site and segment it belongs to.