+```
+
+For the nav, pair it with the wordmark:
+
+```tsx
+
+
+
+ netOrk
+
+
+```
+
+Use `netOrk` consistently — the `Ork` part
+in sky-400 ties the wordmark to the accent color.
+
+### `` references
+
+```html
+
+
+```
+
+---
+
## Core Principle
**The website looks like a dark-mode dev tool, not a SaaS landing page.**
diff --git a/index.html b/index.html
new file mode 100644
index 0000000..9d43285
--- /dev/null
+++ b/index.html
@@ -0,0 +1,17 @@
+
+
+
+
+
+
+ + netOrk ships with custom NAPALM drivers for 11 device types and supports all built-in NAPALM + drivers. Capability availability varies by driver. +
+| Driver | +Device type | + {CAPS.map((c) => ( ++ {c.label} + | + ))} +Status | +
|---|---|---|---|
| {d.name} | +{d.deviceType} | + {CAPS.map((c) => ( ++ + {d[c.key]} + + | + ))} +
+ All standard NAPALM drivers are supported. Capabilities depend on the upstream NAPALM implementation. +
++ Complete reference for all netOrk capabilities. +
+
+ {code}
+
+ )
+}
+
+function Step({ n, title, children }: { n: number; title: string; children: React.ReactNode }) {
+ return (
+ Documentation
++ Get netOrk running from zero to a managed device in under 10 minutes. +
++ Clone the repository, copy the example environment file, and deploy with a single command. +
++ The deploy script builds images, pushes them to the target host, and starts Docker Compose. + Alembic migrations run automatically on first start. +
++ Once the containers are up, navigate to your server IP in a browser. +
+{card.body}
+| Hostname | +IP | +Driver | +Status | +
|---|---|---|---|
| {r.name} | +{r.ip} | +{r.driver} | +
ap-001.lan
+10.0.0.10
+GL.iNet
OpenWRT 23.05
openwrt
2 min ago
| Interface | +IP | +State | +
|---|---|---|
| {iface} | +{ip} | +{state} | +
Drift detected — VLAN 20 (iot)
+ap-002.lan: VLAN name mismatch. Expected "iot", got "IoT-devices".
+ +2
+Critical
+7
+High
+14
+Medium
+10.0.0.50:514 (UDP)
+3 decisions · 0 bans (24 h)
++ netOrk discovers, monitors, and manages your routers, switches, access points, + firewalls, and servers from a single UI — regardless of vendor. + No SaaS dependency. Runs on your infrastructure. +
++ Managing a mixed network means juggling a different admin UI for every vendor — + one for OPNsense, one for HP ProCurve, one for OpenWRT, one for Proxmox. + Config changes happen directly on devices with no audit trail. + You find out something drifted when it breaks. +
++ ICMP sweep, SNMP scan, and HTTP probing find devices before you add them. + Fingerprinting identifies vendor and platform automatically. + Adopt results into your inventory with a single click. +
++ Every device is polled on a configurable interval via NAPALM. + Interface status, ARP tables, DHCP leases, VLAN membership, + Docker containers, and SNMP health metrics — all in one place. +
++ Define desired state in netOrk. On every poll, device config is compared against it. + Drifted devices get a warning; a one-click fix stream applies the correction and + shows you live SSH output. +
++ netOrk ships with custom NAPALM drivers for 11 device types, plus all built-in NAPALM drivers. + New drivers follow a documented registration pattern. +
++ Hostname, IP, vendor, OS version, last poll time, and active warnings on one card. + Tabbed detail view for interfaces, LLDP neighbors, ARP table, VLAN membership, + packages, services, and scheduled jobs. +
++ Define VLAN names and SSID settings once. netOrk compares them against every polled + device and pushes corrections automatically via UCI (OpenWRT) or the device's native API. +
++ Wazuh agent status, CVE counts by severity, and recent alerts — all linked to the device + record. One-click agent install if the agent is missing. + Graylog syslog forwarding status with auto-fix. +
++ Integrations (Wazuh, Graylog, CrowdSec, apt-cacher-ng) are plugins that register into + the plugin system — they can be enabled or disabled per deployment without code changes. + Adding a new integration follows a documented pattern with a hook bus, typed metadata, + and a plugin registry. +
+ + Plugin system docs → + ++ netOrk runs in Docker Compose. Five containers: API, two worker pools, a Beat scheduler, + and an nginx UI server. No external dependencies beyond Redis and PostgreSQL. +
+
+ {`# Clone + configure
+git clone https://gitea.example.com/netork/netork.git
+cp .env.example .env
+# edit .env (DB URL, Redis password, secret key)
+
+# Deploy
+bash scripts/deploy.sh 192.168.1.10`}
+
+