Features

What Topolux does today. Projects and devices, inspections and reports, connectivity checks, topology, issues and to-dos, and task history with evidence. The business baseline, network overview and triage are rolling out during the trial.

This page lists only features that are already live. Features marked Rolling out during the trial use a large language model. They are being opened up in stages during the trial, so not every account can use them yet.

The web console and the mobile app have the same features, so everything below works on both (where the way you do something differs, it says so). The only difference is that the mobile app has a built-in phone executor.

Projects and devices

  • Organized by project: each project is one network. Its devices, tasks, reports and issues all belong to it.
  • Add devices in bulk: on the web, upload a spreadsheet (CSV / XLSX) or paste a list, up to 100 devices per batch. In the app, paste a list. One device per line. Each line is checked, and problem lines are flagged without holding up the rest.
  • Login templates: set one common login method per project. Devices added in bulk use it by default, and any single device can have its own.
  • Test connection: when you add a device, Topolux tries to connect once to confirm the address, port and account work, and reads the device’s hostname and vendor. On the web this needs a standalone executor that is online. The app uses the credentials stored on the phone.
  • Subnet scan: scan a subnet from the devices page and add the devices it finds to the project in one step.
  • Device details: each device’s basic information and inspection history.

Inspections and reports

  • Routine inspections: inspect every device in the project from a template and compile the results into one report. Findings go into the issue list. No language model is involved; judgments come from thresholds and rules.
  • Schedules: run automatically on chosen days and times. Repeated failures are flagged, and you can jump straight to the last run. A schedule that keeps failing is turned off automatically once it reaches the limit.
  • SNMP interface inspections: collect interface data over SNMP and summarize it. Runs only on a standalone executor.
  • Report center: all reports in one place. Download them as PDFs, and the file’s integrity is verified automatically after download.

Connectivity checks

Ping chosen targets. By default, if packet loss is above 1%, Topolux checks again after about a minute and then reports. The result reflects the path from where the check ran to the target. Useful before and after a change, or when a user reports a problem.

Topology

Once every device in a project has been inspected, the topology is generated automatically. You do not need a business baseline first.

Issues and to-dos

  • Issue list: problems found by inspections are collected in one place. Track them by status, and reopen one if it comes back after being resolved.
  • To-do cards: anything that needs your decision or approval shows up as a card in your to-do list. One example is whether to keep trusting a device whose host key has changed. Cards can be handled on the web or in the Android app.

Task history and evidence

  • Steps and timeline: see each task’s steps, where each one ran and how long it took.
  • Original evidence: every finding opens to the command output collected at the time.
  • Retry, cancel and feedback: retry a failed task, cancel one in progress, and give feedback on the results.

Features rolling out during the trial

The features below use a large language model. The model only produces proposals and suggestions. It never connects to devices and never approves anything for you. Raw configurations and logs are never sent to it, and whatever does reach it is redacted first.

Business baseline Rolling out during the trial

A record of what your network looks like when it is healthy, in four layers:

  • Structure: device roles and locations, links, uplinks, address zones and business objects. Once confirmed, business roles and key links are marked on the topology.
  • State: the operating state of each module.
  • Configuration: the full configuration, with passwords and other sensitive values masked.
  • Metrics: recent valid readings, from which normal ranges are worked out automatically.

To set it up, Topolux collects data, works out the baseline, and asks you at most three questions. The first version is published once you confirm the summary. After that, every daily inspection is compared with the confirmed baseline. Differences are gathered into one confirmation list, and you decide item by item whether each is an expected change or something to investigate.

Network overview Rolling out during the trial

A summary of risk levels, key points and suggested checks across the whole network, with a link to the task that produced it.

Triage Rolling out during the trial

Describe the symptoms and when they happened. Topolux plans what to check and how, and once you confirm, the executor collects the data and Topolux returns an analysis. If the analysis fails, it falls back to a rule-based summary.

Topolux is currently available by invitation. Contact us to request a trial.

Request a trial