Requirements:

CoreBit runs on Linux only (Tested on Ubuntu).

CoreBit is lightweight and build for performance. It uses multi threaded polling for optimal performance.
System requirements depends on how many devices is monitored. It has been tested on a single core vmware machine with 309 Mikrotik devices, with a polling time under 30 sec.
It is designed for "On Premise" installation, no Cloud solution with monthly subscription, it only requires Internet when activating the license first time.

Installation:

CoreBit installs easily with one command in under 5 minutes.

Just run this line in shell on the server that shall run CoreBit. (See below for install options)

curl -fsSL https://licensing.corebit.ease.dk/install.sh | sudo bash -s

After installation you are presented with access url, and basic commands to manage the installation.

Optional install options:

--update Update existing installation 
--uninstall Remove the application
--no-db Skip database setup (use external DB)
--db-host HOST PostgreSQL host (default: localhost)
--db-port PORT PostgreSQL port (default: 5432)
--db-name NAME Database name (default: corebit)
--db-user USER Database user (default: corebit)
--port PORT Application port (default: 3000)
--licensing-url URL Licensing server URL (default: https://licensing.corebit.ease.dk)
--run-as-root Run service as root (see note below)
--verbose Show detailed output for debugging

Network Access on Ubuntu 24.04+
Ubuntu 24.04 removed setuid from the ping utility, which can cause network probing issues when running as a non-root user.
The installer automatically grants CAP_NET_RAW and CAP_NET_ADMIN capabilities to the service, which should resolve this.
 If you still experience network issues (devices showing offline despite being reachable), you can use the --run-as-root option.

Quick start guide..

Default login to CoreBit is admin/admin.

1. Create a new map, edit it, and make it your default map (Can be changed later)
2. Configure Credential Profiles. Make sure to have created profiles to match what might be found when scanning your network. Scanning will try all your profiles until one gives data.
3. Tune concurrent probe threads and failure count in settings to avoid mass probe failures
4. Install Node exporter on all linux and windows hosts, it is recommended to add --collector.netdev.address-info to exporter, so Ip addresses are discovered from devices.
5. Press Scan, enter ip range and select profiles matching your devices in the range. (Scans can be saved for later use)
6. Start building you network diagram.

If you experience problems, please create an issue in github