Schedule DemoStart Free Trial

Unified Observability Platform for Modern IT Operations

Summarize with AI what Motadata does:
© 2026 Mindarray Systems Limited. All rights reserved.
Privacy PolicyTerms of Service
Generally available · August 2026

ObserveOps Infinity.
Four foundations.

It needs less hardware. It cleans up your data before anything gets stored. It’s one edition instead of four. And it’s built to run AI agents when they arrive.

See what changedRead the licensing model

1 edition

Replaces NM · NO · HIO · FSO

up to 30–40%

Lower hardware footprint

Included

The observability pipeline, in the base platform

0

Locked features or paid upgrades

The decision behind the release

Hardware got expensive. We decided that was our problem, not yours.

Infinity started with four costs our customers were carrying that they never should have. We fixed each one inside the product, before it could show up in a quote.

01

The hardware cost

Buying more servers than the software should have needed.

Fixed

02

The raw-data cost

Keeping every log and metric in full, with no simple way to say no.

Pipeline added

03

The complexity cost

Four editions, long comparison tables, and paywalls in front of a product you already bought.

Tiers retired

04

The re-platforming cost

Being told the next generation of features needs a different product.

Same platform

Observability is expensive to run. It keeps everything, in full, forever, and you pay for it twice. Once for the software, and once for the servers underneath.

That worked while hardware got cheaper every year. It doesn’t any more. Server, memory and storage prices have climbed sharply around the world, and most vendors have simply passed the rise on to their customers.

We gave our engineers a different job: treat the customer’s hardware bill as a limit we have to design around.

Four foundations came out of that. Each one removes a cost. And each one makes the next one possible.

Hardware TCO

The same observability, on a lot less hardware.

The problem

Hardware prices have gone up everywhere we sell. Observability needs heavy compute to take data in, and heavy storage to keep it. So the price rise lands on your infrastructure bill. Most vendors treat that as something outside their control. We treated it as a problem with our own engineering.

What we did

We made the hardware footprint the thing we had to design around in this release. We rebuilt how data comes in, how it’s stored, how it’s rolled up, how it’s indexed, and how efficiently our collectors run. Same device counts. Same retention. Same queries. Far fewer resources.

What it means for you

Fewer servers for every thousand devices you monitor. Less storage for the same retention. Lower cost underneath too, across hypervisor, power and rack space. And a shorter path to HA and DR, because staying resilient no longer doubles a bill that was already high.

A guide to the footprint · same deployment

Previous generationbaseline 100%
ObserveOps Infinityup to 30–40% lower

This is a guide, not a promise. The real number depends on your mix of devices, how long you keep data, how often you poll, which add-ons you run, and your topology. Every deployment is sized properly against the official Motadata sizing matrix, and your quote comes from the finished sizing worksheet.

Foundation two compounds the saving. Data the pipeline never stores needs no disk to buy.

Observability Pipeline

Every signal gets shaped before it lands.

Here is what the pipeline does today. There is room built in to keep adding to it.

01
PARSE

Better parsing

We give your data structure the moment it arrives, whatever the format or the vendor. Logs, events, traps, flows and metrics all come in as fields you can search.

Why this counts as a foundation

The pipeline is what makes the other three hold up. It is why the hardware footprint came down: data you never store needs no disk. And it is why the platform is ready for agents, because an agent can only reason over data that has structure and context behind it. We built it as a control plane you can extend. The stages above are where it starts.

What it means for you

You pay in line with what your data is actually worth. Retention becomes a setting you change in minutes. Sensitive fields get masked before they are ever written. And incidents open with the context already attached.

Unified Infinity licensing

We retired the tiers. What is left is Infinity.

The problem

There used to be four ObserveOps editions: NM NO HIO FSO. Feature comparison grids. Paywalls in front of things you had already deployed the platform for. Weeks spent asking “which edition do I need?” when the real question was “what do I need to monitor?”

What we did

Now there is one edition: ObserveOps Infinity. You get the whole platform from day one: monitoring, topology, SLO, dashboards, AIOps, automation, the observability pipeline and security. You are counted only on what you monitor. Nothing is held behind a bigger plan, because there is no bigger plan.

And a second change that matters

Log and Flow used to be priced per GB per day. They are now priced per source. You are licensed on how many things you watch. If an application suddenly gets chatty, your license stays exactly where it was.

ObserveOps Infinity Platform

Base · full platform, incl. pipeline & AIOps

Monitored Device

Flow Monitoring

Flow Source / Exporter

Log Monitoring

Log Source

NCCM

Managed Network Device

APM

Instrumented App / Agent

RUM

Front-end Application

Terms: 1-year · 3-year · perpetual with ATS. Base SKU family MD-OO-PLT. Add-ons attach in any combination to the same edition. Quantities move within volume bands. The edition itself never changes.

Existing customers: nothing is forced. Your deployment carries on under the contract you have, and you move to Infinity when it suits you.

Agentic AI for observability

The platform is ready. The agents come next.

The problem

Most “AI in observability” is bolted on top of a data layer that cannot support it. An agent cannot reason over data that has no structure. It cannot act safely when it has no idea who owns a system or what it connects to. And you cannot trust it when nobody knows how far its actions reach. The gap shows up the moment a demo becomes a deployment.

What we did

We built the groundwork first, and that groundwork is the other three foundations. Structured, enriched, governed data gives an agent something it can reason over. One edition with nothing locked means agentic features reach every customer, on the plan they already hold. And the room we freed up in the hardware budget means there is capacity to run it.

What it means for you

Agentic features will be released onto this platform, on this license. Your deployment, your purchase and your instrumentation all stay as they are. Deploying Infinity today is how you get ready.

Data with structure and context

We parse and enrich as data arrives. That is the starting point for anything an agent reasons over.

Shipped

A governed data lifecycle

Retention and masking run on policy. These are the guardrails that keep automation auditable.

Shipped

AIOps, correlation & anomaly detection

Less noise, and patterns you would otherwise miss. Included in the base platform today.

Shipped

Runbook automation & approvals

A safe way to act. These are the hands an agent will use later.

Shipped

Agentic capabilities

Autonomous investigation and guided fixes. On this same platform and license.

Releasing soon

Read it from where you sit

Four foundations. Three very different budgets.

CIO · CFO

A lower cost, and one you can predict.

  • We cut the infrastructure cost instead of passing it on to you
  • Your license follows what you watch, not how much data it produces
  • One edition, with no upgrade bill hiding in year two
  • No new product to buy when agentic features arrive

Head of Infrastructure · NOC

Less to run. More to see.

  • Fewer servers to run, patch and keep highly available
  • Retention is a setting you change, not a purchase you make
  • Alerts arrive with the CI, site, owner and service already attached
  • Spikes and event storms get absorbed, not dropped

SRE · Platform Engineering

A data layer worth building on.

  • Data arrives structured and enriched, before it is stored
  • Masking and governance happen on the way in, not after the fact
  • One platform to instrument, with nothing locked behind a tier
  • The foundation agentic tooling will actually need

FAQ

Frequently Asked Questions

Common questions about ObserveOps Infinity and what the platform does.

No. Two things changed, and both go in your favor. You need less hardware. And Log/Flow moved from per GB per day to per source, so your license no longer grows just because your data does. On top of that, things that used to be held behind a higher tier are now included. Your exact numbers are a conversation with your account manager. The direction of the model is lower cost and more predictability.

This is what we mean by customer-first.

Every one of these four foundations cost us something. Years of engineering. License revenue we chose to leave on the table. And a pricing model that stays flat even as a customer’s data grows. We think that is the right trade. Building a product ecosystem is only worth it when the customer feels the benefit of the engineering.

Talk to licensingRead the licensing guide

Four foundations. One edition.