Entities are scattered
Devices, VMs, switches, access points, domains, NAS systems, and services are often listed in different places with no shared structure.
CMDB
NEGELLAN
Customer network documentation
Document client networks in one place.
NEGELLAN helps infrastructure teams document customer networks: devices, relationships, passwords, notes, wiki pages, and client-ready views connected to the same site structure.
The problem
Customer network documentation is still broken.
A real client site is more than an inventory list. You need to know which devices exist, how they belong together, where passwords are stored, and which notes explain the setup. Today that knowledge is usually spread across tools.
Structure is manual
Even when discovery finds devices, someone still has to turn noisy results into a site tree that humans can actually read and maintain.
Passwords live elsewhere
Credentials are sensitive, but they also need context: which device, service, customer, and location they belong to, and who accessed them.
Existing tools do not fit
Generic wikis, password managers, spreadsheets, and monitoring tools each cover one part. None of them becomes the actual network documentation.
The solution: NEGELLAN
One system for entities, credentials, and wiki documentation.
NEGELLAN builds a structured documentation layer for every customer and site. Assets become real entities, credentials are assigned to the resources they unlock, and wiki articles can link directly to the devices and services they describe.
Current state of development
Already working on real client networks
The product already has a web interface, server API, desktop discovery app, database-backed asset structure, credential assignment, and wiki-linked resources.
Structured entities
Customers, sites, assets, groups, relationships, documentation sections, and discovery snapshots are stored as connected data instead of loose notes.
Secure desktop discovery
Discovery runs from the desktop app inside the customer network or VPN. The server receives snapshots without needing direct access to internal systems.
Credential storage with context
Passwords and API keys are assigned to the device or service they belong to, with audit trails for viewing and editing sensitive data.
Wiki based on assets
Wiki articles can reference assets by stable human-readable tags, so notes, procedures, and explanations stay connected to real infrastructure.
Client-ready documentation
The same data can be organized into readable site documentation and shared with clients when the documentation is ready.
Built because no existing tool fits
NEGELLAN is not just a wiki, not just a password manager, not just discovery, and not just monitoring. It is the missing layer between all of them.
How it works
Discover locally. Structure assets. Document around them.
NEGELLAN starts with the systems you can access today, turns them into structured assets, and lets your team build documentation and wiki pages on top.
Collect data from inside the client network
Discovery
The desktop app scans reachable systems through the access you already have.
NEGELLAN does not need the cloud server to reach into a customer network. The desktop app runs on your workstation or through VPN, talks to Proxmox, AD/DC, UniFi, NAS, or a network scan, and uploads controlled snapshots to the server.
- No need to expose internal management interfaces to the internet.
- Start with the sources you have access to today.
- Keep raw snapshots so later discoveries can be compared.
Turn discovered devices into real documentation entities
Structure
Create assets, relationships, groups, and site trees from discovery results.
Discovery results are useful, but they are not documentation yet. NEGELLAN helps turn devices, VMs, switches, storage, domains, and services into structured entities that belong to a customer and site.
- Group assets into readable documentation sections.
- Keep technical relationships separate from the presentation tree.
- Mark missing information instead of hiding it.
Add passwords, notes, wiki pages, and client-facing structure
Documentation
Use the asset structure as the base for the actual customer documentation.
NEGELLAN connects the things teams normally keep apart: inventory, passwords, wiki articles, technical notes, and the documentation tree. The result is a customer site that can be maintained internally and shared when ready.
- Assign credentials directly to assets and services.
- Link wiki articles to stable human-readable asset tags.
- Share selected documentation with clients without losing internal structure.
The visible fabric of every client site
Network infrastructure
Gateways, switches, wireless access, topology context, and site connectivity.
NEGELLAN treats network infrastructure as the first layer of site understanding. Gateways, switches, wireless systems, uplinks, and relationship context define how the rest of the environment can be documented.
- Captures gateway, switch, wireless, and topology context in one presentation layer.
- Keeps network relationships readable without hiding the technical graph underneath.
- Supports environments with full controller access, partial access, or simple network scans.
Virtual infrastructure without losing the physical context
Proxmox clusters
Nodes, VMs, CPU, memory, disk usage, and notes metadata.
NEGELLAN connects Proxmox inventory to the wider client site, so nodes and VMs become part of the documentation instead of living in a separate silo.
- Documents nodes, guests, resources, and VM metadata in context.
- Shows compute relationships alongside network, storage, and identity information.
- Helps teams understand capacity, placement, and service ownership faster.
Identity discovery as documentation structure
Microsoft AD / DC
Domain-aware client discovery and documentation grouping.
Domain data gives infrastructure documentation a strong naming and ownership backbone. NEGELLAN uses it to identify clients, organize assets, and connect technical inventory to real operational structure.
- Groups domain-joined clients into clear documentation areas.
- Helps separate real endpoints from noisy or duplicate observations.
- Connects identity context to assets, relationships, and site documentation.
Storage documentation that belongs with the site
NAS inventory
Storage pools, disks, capacity, and relationships to the rest of the site.
Storage is rarely isolated. NEGELLAN brings NAS pools, disks, capacity, and relationships into the same documentation structure as compute, network, and client systems.
- Documents pools, disks, capacity, and device relationships.
- Keeps storage assets connected to the systems and services that depend on them.
- Makes storage state understandable for internal teams and client-facing views.
Early focus
Made for MSPs and hands-on infrastructure teams.
NEGELLAN.COM
An early product for better infrastructure memory.
The first version is focused on getting real client networks into a clear, maintainable documentation structure.