Implementation & Tooling #

Documents what each role runs and how it is configured — what Deevnet runs today, and what is under evaluation — organized by substrate architecture layer. Each page records what was chosen and why. The section opens with Hardware: the physical boxes, one page per model.

How to operate what is selected here is in the runbook; finished projects built on it are under Completed Projects.

Roles and what fills them #

The roles themselves — what each does, and where it sits in the network — are defined in Architecture. This section only says what fills them.

The software this site wrote for itself — the Deevnet API, the Terraform provider tenants use, and the runtime tools around them — is Deevnet Software. Everything else the management and control planes run — OpenBao, the MQTT broker, the log store, Grafana — is listed in the Software Catalog.

Scope #

This section answers the question:

“Why did we choose this, and under what conditions would we change it?”

Each role page documents:

It does not restate the role, and it holds no procedures: those are in the runbook.

Evaluations #

What each selection was checked against, by item: its current verdict, and every evaluation behind it, plus the candidates being considered. See Evaluations. Hardware in service is evaluated on its model’s Hardware page. The process and criteria are the Evaluation policy.

Software Catalog #

Every piece of software in use, with its version, license and support model, grouped by layer, including the services bundled inside OPNsense: see Software Catalog.

Technology Stack #