Features
Every feature
The complete list for datacenters and dedicated and colocation providers: traffic, enforcement, WHMCS, switches, servers and security. Nothing is listed that the product does not do.
Traffic measurement
Usage read from the switch port itself, with every gap admitted rather than filled in.
- Counters read over SNMP from the switch itself, 64-bit wherever the interface offers them
- Collection interval set per switch
- Rollups at five minutes, one hour and one day
- 95th percentile on the direction you bill
- Billing basis of download, upload or total, per service, per server or per site
- Counter wraps and resets detected instead of showing up as a spike
- Every sample marked usable, after a gap, after a reset or suspect
- A window nobody measured reports nothing rather than zero
- Usage against allowance, with the percentage written beside every meter
- Date and time range picker with a correct Solar Hijri calendar
Quotas and enforcement
How much each customer may use, and what happens when they go over or stop paying.
- A base allowance per service, plus purchased or granted extra traffic
- Carried-over traffic debt held per service
- Automatic block of the customer's switch port on overage
- Automatic block on an unpaid invoice
- A grace period you set before any block
- An AI review of each block before it is carried out
- Automatic unblock once the customer buys traffic or pays
- A locked port is never changed by automation
- Ships switched off; arming it takes a full administrator and a typed confirmation
WHMCS and the customer portal
Your billing system stays where it is, and DCManage works with it in both directions.
- A WHMCS module that connects WHMCS to the platform
- Two-way integration with WHMCS
- Services read from WHMCS with their source identifiers kept
- An unpaid invoice can block the port, and paying it lifts the block
- A customer portal where each customer sees their own services and usage
- Customer sign-in kept separate from operator sign-in
- Import from an existing DCManage module through a read-only snapshot
Switches
Reach every switch the way it allows, and read what you need from it.
- Cisco IOS and NX-OS, with a generic mode for other devices
- SSH, Telnet and SNMP, chosen per switch
- Port lock, so neither automation nor a manual action changes a port you have pinned
- Extra-Permit: access lists and object groups managed from the panel
- MAC address lookup in the forwarding table
- Port discovery on demand or on a schedule
- CPU, memory and uptime for every switch
- Hardware and TCAM usage
- Credentials encrypted per switch and never shown again
- Consecutive failures and last answer time for every device
Ports
Where a measurement becomes a customer.
- The full port table of every switch, with status and negotiated speed
- Traffic collection switched on or off per port
- Port-to-server mapping, with the source of each mapping recorded
- Ambiguous mappings left unattached and counted, never guessed
- A port lock recorded with its reason and honoured even while enforcement is off
- A traffic chart for every port over any range
Server control
The management controller of every server, from that server's own page.
- iLO, iDRAC, IPMI and Redfish
- Power on, power off and restart
- HTML5 console
- Virtual media
- Hardware inventory and health: memory, drives, RAID, fans and power supplies
- Controller event logs
- Reached directly, through a SOCKS proxy or over a WireGuard tunnel
- Credentials encrypted on the server record and never displayed
Datacenters and racks
What is racked, cabled and sold, in one place.
- Datacenters with a code, name, location and notes
- Racks per site with a configurable height
- Rack-unit elevation with switches and passive equipment together
- Patch panels, power strips and blanking plates as rack items
- Double-booked rack units reported rather than drawn on top of each other
- Servers with hostname, address, asset tag, serial and rack position
- Multi-unit servers drawn across every unit they fill
Monitoring integrations
Keep the monitoring you have and compare it with the platform's own figures.
- PRTG, Zabbix, Cacti and LibreNMS
- The platform's own SNMP collector, shown as a source of its own
- Traffic reconciliation: both figures for the same port, side by side
- Sensors attached to ports only where both systems agree; the rest are counted, not guessed
- Sensor data kept locally, so no page waits on a remote system
- A source that stops answering is paused automatically and tried again later
- Request timeout and certificate verification per source
Reaching management networks
Controllers and switches on ranges your panel has no route to.
- A WireGuard tunnel to the management network
- SOCKS5, SOCKS4 and HTTP CONNECT proxies
- Optional proxy username and password, encrypted
- Names resolved at the far end, for names only the private range knows
- A proxy chosen per switch, per server controller and per monitoring source
- Reachability check that sends no credential
- A proxy in use cannot be deleted from under the equipment that relies on it
Roles and sign-in
Who may do what, set once and enforced everywhere.
- Roles as named sets of fine-grained permissions
- Individual exceptions per administrator, where a revoke always wins
- Permissions grouped by risk, with high and critical ones marked
- Two-factor sign-in
- The last full administrator cannot be removed or demoted
- Nobody can change their own roles or permissions
- Sign-in throttling per account and per address
- An address allow-list checked before the sign-in form is shown
Audit log
A record of what happened that nobody can edit.
- Every change and every refusal recorded
- Editing and deleting entries refused by the database itself, not only by the code
- Who, from where and with which request, on every entry
- Before and after values for every changed field
- Secrets removed before anything is stored
- Readable action names in both languages, filtered by action and outcome
API
For the work that should not need a browser.
- API keys with their own permissions
- Keys limited to source addresses or networks
- An optional expiry date per key
- Keys revoked without being deleted, so the audit trail stays complete
- The secret shown once, when the key is created
- Reference documentation generated from the permissions a key can hold
Running it
The parts you only notice when they go wrong.
- Installs on your own Linux server, with PostgreSQL
- Signed updates, verified before they are applied
- A scheduler with a status page: what ran, when, and for how long
- Each scheduled task in its own process, so one slow task holds up nothing
- Device work queued and reported back to the page that asked for it
- The web process cannot read device credentials
- Daily partition maintenance and pruning of old samples
The interface
Built for long shifts, in either language.
- Persian and English throughout, with right to left done properly
- Solar Hijri and Gregorian dates
- Light and dark themes
- Two densities, for scanning hundreds of ports
- Tables that become labelled cards on a phone
- Live filters that do not reload the page
- No external assets: no font service, CDN or analytics, so it works on a closed network
- Keyboard navigation and a visible focus outline everywhere
Good to know before you start
Said here, so nothing surprises you after you buy.
- Enforcement ships switched off. You arm it when its figures agree with yours, with a full administrator and a typed confirmation.
- DCManage does not issue invoices. WHMCS stays your billing system, and DCManage works alongside it.
- Nothing is installed on customer machines. Everything is read from your network equipment and management controllers.
- It runs on your own Linux server with PostgreSQL, and the data stays with you.
See DCManage for yourself
Open the live demo with invented data, or tell us about your datacenter and we will reply with a quote.