Atlas view

Networking

This domain groups systems that solve Networking problems - shared vocabulary, common interfaces, and repeatable operational constraints. Use this page to see which systems already exist, what they ingest and emit, and which patterns we repeatedly rely on in this problem space.

Domains are how we avoid reinventing the same solution in slightly different shapes. When a domain repeats, it’s a signal to standardize schemas, mapping layers, auth patterns, and operator workflows.

Domain guide

How to read this domain

Definition

This domain groups systems focused on networking workflows, shared data models, and repeatable operational constraints.

What belongs

  • Systems where networking is the primary problem space.
  • Integrations that move, validate, or enforce data in this domain.
  • Operational tools that reduce risk and manual work for this domain.

What doesn't

  • Generic tools where networking is incidental metadata.
  • One-off experiments without domain-specific constraints.

Typical integrations and constraints

  • Source-of-truth feeds, vendor APIs, and scheduled extracts.
  • Schema drift, credential scope, and compliance requirements.
  • Role-based access and operational review cycles.

Common interfaces

  • REST/JSON APIs and vendor export endpoints.
  • CSV, SQL views, or Sheets-based boundary objects.
  • Auth boundaries (service accounts, OAuth, SSO).
Results 3 projects
Experiment · Deprecated

iscdhcp

Automate consistent DHCP configuration generation across multiple sites from a normalized file-based configuration layout. It ingests Configuration files …

Automation Engines Operational Adoption
Open project
Experiment · Active

pwnagotchi

Provide local configuration and host-side networking helpers for Pwnagotchi devices. It ingests TOML config overrides, interface names and produces Modified …

Automation Engines Operational Adoption
Open project