Common customer questions about IPAM, monitoring, configuration backup, deployment, and support.

IPAM Manager uses license packages based on the number of managed devices. The current commercial structure is centered around practical tiers such as 100, 200, and 500 devices, while the downloadable trial is intended for evaluation with support for up to 10 devices for 14 days.

The platform learns the network by collecting information directly from the network devices themselves through supported protocols and valid credentials. This is a major advantage of the platform: instead of relying on broad IP range scanning to guess which networks are in use across the organization, it queries the live infrastructure to identify devices, discover neighbors, build topology, and understand the real network environment with higher accuracy and better operational context.

The current release is focused on common enterprise network vendors and operating systems used in switching, routing, and firewall environments. This includes support areas such as Cisco IOS, Fortinet FortiGate, Aruba AOS-CX, ArubaOS-Switch or HP ProCurve, and Juniper Junos in the supported workflows documented for the product.

IPAM Manager is designed as an on-premises product. It is intended for organizations that want to keep IP address management, discovery data, topology context, and operational control inside their own environment rather than moving administrative network data into a third-party cloud service.

Yes. The website and download package structure support both Linux and Windows delivery. This allows customers to evaluate and deploy the platform in the operating system that best fits their internal standards and operational model.

No. IPAM Manager is broader than basic IP tracking. In addition to address and subnet administration, the platform is positioned around inventory visibility, discovery workflows, topology mapping, operational logs, audit context, and day-to-day administrative control.

The platform is built for controlled administrative environments and supports a security-oriented operating model. That includes features and deployment patterns such as authenticated access, audit visibility, hardened reverse-proxy deployment, and tighter control over administrative workflows in environments that require stronger governance.

Yes. Backup and restore are part of the platform workflow so administrators can preserve and recover important application data and operational state as part of routine maintenance, migration, or recovery planning.

The core product is intended to operate inside the customer environment. Internet access may still be relevant for package download, documentation retrieval, support communication, or update delivery, but the operating model itself is centered on local deployment and internal administration.

A downloadable trial is available for evaluation, and the current website messaging positions that trial around 14 days and support for up to 10 devices. Ongoing product support is primarily intended for licensed customers, while evaluation and pre-purchase questions can also be submitted through the support page or the support mailbox.

Yes. IPAM Manager includes an integrated monitoring engine that adds essential operational visibility to the IPAM workflow. It helps administrators track device availability, key health indicators, and active alerts from the same platform used for subnet, inventory, topology, and discovery operations.

The monitoring engine focuses on practical day-to-day visibility, including ping availability, SNMP reachability, response status, latency awareness, CPU usage, memory usage, active alerts, and recovery state. It is designed to give network teams fast operational context without forcing them to switch between separate tools.

Yes. Monitoring alerts can be connected to email notification rules so administrators can receive updates when important device-status changes occur. This supports faster response to availability, performance, and recovery events.

No. The monitoring engine is designed as a practical operational layer inside the IPAM platform. It gives network teams essential alert visibility and device-status awareness while keeping IPAM, inventory, topology, and configuration context together.

Yes. IPAManager includes network configuration management capabilities that help administrators collect, store, back up, compare, and review router, switch, firewall, and other network device configurations as part of the broader IPAM and network administration workflow.

Yes. The configuration backup engine helps preserve network device configurations, maintain successful backup versions, support configuration version comparison, and reduce the risk of losing critical router, switch, or firewall configuration data.

Configuration backup adds important operational context to IPAM. Administrators can manage IP space, review inventory, inspect topology, monitor device status, and preserve configuration history from one coordinated workspace instead of relying on disconnected tools.

Monitoring helps administrators identify when something changes or requires attention, while configuration management helps preserve the device state needed for review, recovery, and operational comparison. Together, they give teams stronger visibility across IPAM, device health, topology, inventory, and configuration history.

Yes. IPAManager supports practical network device monitoring using ping availability and SNMP reachability context, so administrators can review device health close to IPAM, inventory, topology, and discovery data.

Yes. The monitoring workflow includes CPU and memory visibility for supported devices, alongside availability, latency, alert state, and recovery context. This helps teams detect basic performance conditions without leaving the IPAM platform.

Yes. Config Management is designed to keep backup versions available for review and comparison, helping administrators identify configuration changes between saved device backups.

IPAManager is focused on common enterprise network vendors used in switching, routing, and firewall environments, including Cisco, Fortinet, Aruba, Juniper, and HP workflows documented for supported product areas. Configuration backup behavior depends on device support, credentials, and the relevant workflow configuration.

IPAManager is positioned as a coordinated on-prem platform for IPAM, discovery, topology, inventory, essential monitoring, alerting, and configuration backup. It can reduce the need for disconnected operational tools, while very large environments may still keep specialized enterprise monitoring platforms for deeper telemetry.