I'm looking for a documentation platform for a fairly small IT environment: one server rack, about six physical servers, and roughly 30–40 virtual machines. I want something more structured than spreadsheets, plain wiki pages, or standalone diagram files, but less complex and time-consuming than a full-scale data center inventory system.
Ideally, it would let me track relationships such as which VM runs on which server, assigned IP addresses, operating systems, services, updates, and other configuration details. Built-in IP address management and some kind of diagramming or visual relationship view would be especially useful.
I've considered wiki platforms because they're flexible, but I'd prefer an object-based system with reusable records and relationships. A simpler alternative to a large infrastructure inventory platform would be ideal, though recommendations for well-designed wiki setups are welcome too.
5 Answers
For this size of environment, a wiki paired with a dedicated IP address manager can work well. BookStack or DokuWiki are good for structured write-ups, while phpIPAM can handle address allocation. You can link the systems together manually or automate updates if you really need them, without having to build a full data center inventory model.
A lightweight documentation stack could combine a wiki for service and system pages with diagrams made in Excalidraw or a similar tool, while keeping the configuration in version control. It’s flexible and inexpensive, but it won’t automatically understand relationships between physical hosts, VMs, networks, and services unless you create that structure yourself.
If you want an all-in-one commercial product, Hudu or IT Glue provide object-based documentation, relationships, and infrastructure records. They’re commonly used for smaller environments too, but the subscription cost may be difficult to justify for a small personal or internal setup.
You could simplify a larger inventory platform rather than replace it. One person used it successfully for a similar setup by hiding unnecessary fields and importing server and VM data from the virtualization platform with scripts. It takes some initial configuration, but it gives you proper relationships instead of scattered spreadsheets and markdown tables.
Wiki.js, BookStack, and DokuWiki are worth comparing. Wiki.js is a flexible option if you want a modern interface and content stored in a way that can be backed up or versioned. The tradeoff is that you’ll need to design the page structure yourself, since these tools generally don’t provide the same object and relationship model as an inventory system.
That’s useful to know. The biggest concern was having to create vendors, products, models, and other layers before adding a single server. Automating imports and trimming the interface might make it manageable after all.