NetBox hosting: which device sits where, and on which address.
Your network no longer lives in one administrator's head or in a scattered Excel file, but in a system.
Short answer
NetBox is the administration of a network. It records IP addresses and prefixes, VLANs, racks, devices, cables and circuits, with an API other programmes can read. It replaces spreadsheets and paid IPAM and DCIM packages. Jevana uses NetBox itself for its own infrastructure, and runs it for clients on our own hardware in the Netherlands.
What happens when the network lives only in someone's head
A network grows. A VLAN is added for the cameras, an extra switch in the server room, a cable nobody can trace any more. After a few years one person knows how it fits together, and that person is on holiday when it goes wrong.
NetBox is where that gets written down. Not as a drawing that goes stale, but as data you can search and that matches what is installed, because every change goes in there first.
This is how we use it for our own servers and network. So it is not something we only sell to others.
What it holds
Addresses
- IP addresses and prefixes, with what is free and what is used
- VLANs and where they run
Places and devices
- Racks and the position of each device in them
- Switches, servers, firewalls and their interfaces
Connections
- Cables between ports
- Circuits from a provider, with both ends
For other tools
- An API that scripts and other programmes can read from
- Changes are recorded
In brief
- Replaces
- Spreadsheets and paid IPAM and DCIM packages.
- For whom
- IT teams and service providers who manage more than a handful of devices.
- Our part
- We set it up, update it and watch it. There is a daily backup, also kept at a second location.
- Licence
- Apache 2.0. NetBox is a trademark of its owner, and Jevana has no formal tie with the project.
- Own use
- Jevana uses NetBox itself as the administration of its own infrastructure.
- Leaving
- Everything can be taken along through the API or an export.
Questions
What is the difference between IPAM and DCIM in NetBox?
IPAM stands for IP address management: which addresses and networks you have and how much of it is in use. DCIM stands for data centre infrastructure management: the racks, devices and cables that network runs on. NetBox does both in one system. So you can go from an address straight to the port on the switch.
Do we need NetBox if we have only one office?
Usually not. For one office with a switch and a firewall, a well-kept document is enough. NetBox pays off when there are several locations, many VLANs, server rooms, or when you manage networks for clients. The line is the moment nobody is sure any more that the documentation is right.
Can NetBox take over data from other systems?
Yes. NetBox has an API and can import data, for example from a spreadsheet of IP addresses or devices. Other programmes can read from it in turn, such as scripts that build configuration. What you connect, we decide with you: fill it first, automate later. The goal is an administration everyone trusts.
Can NetBox work with signing in through our existing accounts?
Yes. NetBox can support sign-in through a central login, so colleagues come in with their existing account and you manage rights in one place. You set who may change what. An administrator can alter a cable while a colleague can only look, and someone who leaves is locked out at once.
Goes well with
-
Apache Guacamole
Reach a Windows or Linux machine from a web page, without a port open to the internet.
-
authentik
One login for all your applications, with two-factor authentication, on a server we keep up to date.
-
Network installation
A business network for a new or refitted building: cabinet, switches, wifi and firewall, drawn and documented.
-
Uptime Kuma
A monitor that tells you when something stops responding, from a place outside the network it watches.
Tell us what you run.
An introduction costs nothing. You talk straight away to one of the two people who will actually do the work.
or email info@jevana.systems