Loading session…
Loading content, please wait.// INFRASTRUCTURE
$ node inspect --topology
Click a node to run node inspect — its role, specs, metrics, and operational notes. Hover to highlight its connections.
Kandarp Kumar Thakur's DevOps stack rendered as an interactive topology — eight technology-family nodes connected by their real relationships, each inspectable.
Status: active (Up 1y). The cloud substrate — EC2 compute instances provisioned for workloads that need elastic scale. Everything that leaves the home lab runs on, routes through, or is delivered from here.
Stack: EC2, IAM, Security Groups, EBS, CloudWatch.
Specs: Service: EC2, Region: ap-south-1, IaC: Manual + Scripts, Cost: Free tier.
Metrics: Uptime: 99.9%, Instances: 3, Regions: 1, SLO: 99.5%.
Status: active (Up 1y). The packaging boundary — every self-hosted service is built into an immutable image and shipped as a container. Powers CasaOS, the chat platform, and the open-source app fleet with reproducible builds.
Stack: Docker, Compose, CasaOS, BuildKit.
Specs: Engine: containerd, Runtime: runc, Images: 20+, Base: alpine.
Metrics: Containers: 12, Images: 20+, Networks: 4, Volumes: 8.
Status: active (Up 1y). The kernel everything stands on — the host OS for the self-hosted server. Tuned for throughput, hardened by default, and the foundation for Docker, CasaOS, and the NAS stack.
Stack: Debian, systemd, iptables, cgroups, bash.
Specs: Distro: Debian 12, Init: systemd, Shell: bash 5.2, Hardening: Firewall + fail2ban.
Metrics: Hosts: 2, Load: 0.6, Uptime: 1y, Services: 18.
Status: active (Up 3y). The origin — every commit, branch, and release lives here. GitHub Actions turns each push into a build and a test run, closing the loop from source to deploy across all projects.
Stack: Git, GitHub, Actions, Pages.
Specs: Host: github.com, User: @kandarp-thakur, Repos: 10+, Branch: main.
Metrics: Commits: 1.2k+, Repos: 10+, Releases: 8, Pipeline: CI/CD.
Status: active (Up 1y). The fabric that connects and segments every node — VLANs isolate traffic between the server fleet, the NAS, and client networks. Traffic flows through here on its way to and from the firewall.
Stack: VLAN, Subnets, DHCP, DNS, Switching.
Specs: Topology: VLAN-segmented, VLANs: 4, DNS: local, Mesh: L2.
Metrics: Latency: <2ms, Throughput: 1 Gbps, VLANs: 4, Hosts: 15+.
Status: active (Up 1y). The perimeter and segmentation layer — stateful rules and rate limiting that gate every inbound and outbound packet. Cloud security enforced as code, defending the self-hosted server and the NAS.
Stack: iptables, fail2ban, Security Groups, NAT.
Specs: Mode: stateful, Rules: 40+, Default: deny, Policy: IaC + manual.
Metrics: Blocked: 5k/d, Rules: 40+, Alerts: 2/d, Bans: 120+.
Status: active (Up 1y). The persistent layer — enterprise NAS running TrueNAS for backups, media, and shared datasets served over the network. Snapshotted and scrubbed on a schedule so data survives any single failure.
Stack: TrueNAS, ZFS, NFS, SMB, Snapshots.
Specs: Platform: TrueNAS, Filesystem: ZFS, Raw: 8 TB, RAID: RAID-Z1.
Metrics: Capacity: 8 TB, Used: 3.2 TB, Snapshots: 90, Scrub: 0 errors.
Status: active (Up 3y). The automation layer — scripts that provision, scan, and report across the whole topology. Powers the wireless pentest framework (Scapy), the chat platform backend, and the glue between CLI, APIs, and infrastructure.
Stack: Python 3, Scapy, Django, WebSockets, Boto3.
Specs: Version: 3.12, Runtime: venv, Framework: Django, Security: Scapy.
Metrics: Scripts: 30+, Projects: 3, Modules: 12, Runs/d: 50+.
Connections: github → docker (builds), docker → linux (runs on), linux → aws (extends to), aws → firewall (protected by), firewall → networking (filters), networking → nas (mounts), networking → linux (connects), python → github (automates), python → docker (orchestrates), python → aws (provisions).