karam-ajaj

atlas: Discover and Visualize Network Infrastructure

Atlas scans Docker containers and nearby network hosts, then presents discovered devices in an interactive dashboard. It suits homelabs and small infrastructure setups that need scheduled discovery and visibility across multiple subnets.

View on GitHub Compare
Stars
1.3k
Forks
76
Stars, last 30 days
+13

Our take

Health score

26/100

How it is scored
Activity
35
Community
29
Issues
21
Pull requests
20

+13 stars in the last 30 days

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

1,346

Forks

76

Change since Nov 15, 2026: 0 stars·0 forks

Overview

Atlas is a self-hosted network discovery and monitoring tool for mapping Docker containers and reachable hosts. It collects network details such as addresses, ports, and network membership, stores results in SQLite, and displays them in a React dashboard.

It is aimed at operators who want a continuously refreshed view of a homelab or managed network without assembling separate scanning and visualization tools. Scanning can cover detected local networks or explicitly configured subnets.

Key Features

  • Discovers reachable local and neighboring hosts using fast scans and deeper port and OS enrichment.
  • Inspects Docker containers, including their network interfaces and associated IPs, MACs, ports, and network names.
  • Supports scanning multiple interfaces and configured subnets.
  • Presents discovered infrastructure in interactive graph and table views, with a logs panel.
  • Persists scan data in SQLite.
  • Schedules fast, Docker, and deep scans, with intervals configurable through environment variables or the UI.
  • Provides a FastAPI backend and API documentation, with optional UI and API authentication.

Use Cases

  • Homelab administrators can map devices and Docker services across one or more LAN subnets.
  • DevOps teams can review container network membership and exposed ports alongside other discovered hosts.
  • Infrastructure operators can schedule recurring scans to keep a network inventory current.
  • Users managing multiple network interfaces can distinguish a host's presence across interfaces in the dashboard.

Getting Started

Run Atlas as a Docker container with host networking and the required network capabilities and Docker socket mount:

docker run -d --name atlas --network=host \
  --cap-add=NET_RAW --cap-add=NET_ADMIN \
  -v /var/run/docker.sock:/var/run/docker.sock \
  keinstien/atlas:{tag}

See the README for configuration, authentication, subnet scanning, and deployment details. The project also provides a live demo.

Considerations

  • Host networking, NET_RAW, NET_ADMIN, and access to /var/run/docker.sock are required by the documented Docker setup. These permissions and the socket mount grant access to sensitive host capabilities.
  • Network scans can probe reachable devices and ports. Configure subnets and scan intervals for networks you are authorized to assess.
  • Authentication is disabled by default. Set an admin password before exposing the UI or API beyond a trusted environment.
  • The README describes scheduled scans and interval defaults, but its automation notes also mention a 30-minute schedule. Check the current configuration and README before relying on a specific cadence.
  • The repository reports 1.3k stars and 76 forks, but those figures alone do not establish production readiness.

Found this useful?

Share it with someone who would like atlas.