NEMO

Network Operations Workspace – Turn Network Events into Action

The NEMO Philosophy

Network engineers should spend their time solving network problems, not searching for network information.

CCIE Expertise Docker · VPS
Get in touch

Why was NEMO built?

NEMO is the result of 25 years of service provider and enterprise network operations experience. During this time, I encountered the same problem again and again: network operations teams were technically proficient, yet could not work with sufficient efficiency.

It was not knowledge that was missing — it was information.

More precisely: the information needed for day-to-day operations was scattered across different systems. Constantly switching between monitoring tools, syslog, CLI, inventories, configurations and various records consumed a significant portion of the working day. Instead of diagnosing problems, time was spent gathering information.

NEMO changes this.

It does not add yet another data source. It collects, classifies and interprets existing information from an operational perspective.

The goal is simple:

Every morning, a network engineer should see on a single screen exactly what needs attention today.

Why not another monitoring system?

Most monitoring systems excel at collecting data. The problem is not a lack of data — it is too much data. Another monitoring system would simply be yet another interface to check each day.

NEMO does not replace existing monitoring systems.

It interprets the information that network devices already produce and prioritises it from a daily operations perspective.

Why was it built by a CCIE?

Because the most important question is not what can be displayed, but what actually matters.

After twenty-five years of service provider and enterprise operations experience, I know precisely which events require immediate action and which are a natural part of normal network behaviour.

This experience is embedded in NEMO's decision logic.

Why focus on the most important events?

Not all events are equal. A user port going down is a natural part of daily operations. A trunk link failure between switches, however, demands immediate investigation.

NEMO's goal is not to display every event. The goal is for the right event to appear with the right priority.

Why doesn't it try to solve every problem?

Because no system solves every problem. NEMO does not aspire to be a universal network management platform.

Its goal is far simpler: to reduce the time engineers spend on daily routine tasks.

If less time goes to searching for information and performing repetitive tasks, more time remains for solving real problems.

A simple example

A user port inactive for 120 days is not a fault in itself. But it can represent a significant security risk. NEMO automatically identifies such ports — so decommissioning or disabling them becomes a daily routine task, not the result of a manual search.

Interested in NEMO?

Tell us about your environment — we'll show you what NEMO can do for your network operations team.

info@nemo.network