A leaner hardware footprint. A real observability pipeline underneath. One unified edition that retires every tier. And a platform engineered to carry agentic AI. Not four features — four foundations.
1 edition
Replaces NM · NO · HIO · FSO
up to 30–40%
Lower hardware footprint*
In base
Extensible observability pipeline
0 walls
Upgrade gates or feature locks
The decision behind the release
Infinity did not begin as a feature list. It began as four costs we concluded our customers should never have been asked to carry — and a commitment to engineer them out of the product rather than price them into the deal.
01
Paying for iron because the platform was never optimised for it.
Engineered down02
Storing everything at full fidelity because there was nowhere to decide otherwise.
Pipeline introduced03
Four editions, feature checklists and upgrade walls between you and the platform you already bought.
Tiers retired04
Being asked to buy a new product every time the industry moves — most recently, for AI.
Built on the same platformObservability is, by nature, hungry — it stores everything, forever, at full fidelity, and charges you for the privilege on both the software line and the infrastructure line. That model held while hardware got cheaper every year. It stopped holding. Server, memory and storage pricing has climbed sharply worldwide, and the industry's answer has largely been to pass it through. Motadata's engineering team took the opposite brief: treat the customer's hardware bill as our design constraint, not their problem. What follows are the four foundations that came out of that brief. Each one removes a cost. Together, they make the next one possible.
Hardware TCO
The problem
Hardware pricing has risen sharply across every market we sell into. For an observability platform — compute-heavy at ingest, storage-heavy at rest — that inflation lands directly on the customer's infrastructure bill. Most vendors treat it as an external condition. We treated it as a defect in our own engineering.
What we did
The Motadata engineering team took the hardware footprint itself as the design constraint for this release. Ingest paths, storage layout, rollup strategy, index structures and collector efficiency were re-engineered so the platform does the same work — same device counts, same retention, same query behaviour — on significantly fewer resources.
What it means for you
Fewer nodes per thousand monitored devices. Smaller storage provisioning for the same retention window. Lower hypervisor, power and rack cost underneath. And a shorter, cheaper path to HA and DR — because standing up a resilient topology no longer doubles a bill that was already too high.
Indicative footprint · equivalent deployment
* Indicative and workload-dependent. Actual reduction varies with device mix, retention policy, polling interval, add-on modules and topology. Every deployment is sized against the official Motadata sizing matrix — always quote from the sizing worksheet, never from this figure alone.
The saving compounds with foundation two: what the pipeline never stores, you never have to buy disk for.
Observability Pipeline
What the pipeline does today — and it is built to keep growing.
Structure at ingest across formats and vendors — logs, events, traps, flows and metrics arrive as fields, not strings.
The problem
Traditional observability ingests everything as-is and sorts it out later. That makes storage the primary cost driver, makes retention a budget decision rather than an operational one, and leaves every downstream feature — correlation, AIOps, and eventually agents — reasoning over unstructured, context-free data.
What we did
We put a full observability pipeline in front of the datastore, and we put it in the base platform rather than behind an add-on. Every signal is parsed, transformed, enriched, governed and tiered while it is still in motion.
Why this is a foundation, not a feature
The pipeline is what makes the hardware reduction hold at scale, what turns retention into a policy, and what produces the structured, context-carrying telemetry that agentic AI needs. Remove it and the other three foundations lose their footing.
What it means for you
You store what has value and you keep the context that makes it useful. Retention windows become an operational choice, compliance is handled at ingest, and your data volume stops driving your infrastructure bill.
Unified Infinity licensing
The problem
Four editions meant four feature checklists, four upgrade conversations and a wall between a customer and a capability they had already deployed the platform for. It made buying harder than it needed to be and it made the roadmap harder to deliver against.
What we did
One edition. ObserveOps Infinity replaces NM, NO, HIO and FSO, and the full platform — including the pipeline and AIOps — is in the base. Add-ons remain genuinely optional and separately metered, so you buy the modules you actually run.
And a second change that matters
Log and Flow moved from per GB/day to per source. Your licence is now tied to what you monitor rather than how much data it happens to emit — which means your cost stops growing automatically with your estate's verbosity.
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 + ATS. Base SKU family MD-OO-PLT. Add-ons attach in any combination to the same edition — quantities move within volume bands, the edition never changes.
Existing customers: there is no forced migration. Live deployments continue on their current contract and move to Infinity at a moment that suits them.
Agentic AI readiness
The problem
Most “AI in observability” is a capability bolted onto a data layer that cannot support it. An agent cannot reason over telemetry that has no structure, cannot act on data that carries no ownership or service context, and cannot be trusted in an estate where its blast radius is undefined. The demo works; the deployment does not.
What we did
We built the prerequisites first — and they are precisely the other three foundations. Structured, enriched, policy-governed telemetry from the pipeline gives an agent something it can actually reason on. One edition with nothing gated means agentic capability arrives for every customer, not a premium tier. Headroom in the hardware envelope means there is room to run it.
What it means for you
Agentic capability will be released onto this platform, on this licence — not into a separate product that requires you to re-platform, re-procure or re-instrument. Deploying Infinity today is how you are ready for it.
Parsing and enrichment at ingest — the substrate any agent has to reason over.
Policy-driven retention and masking — the guardrails that make autonomy auditable.
Noise reduction and pattern detection, included in the base platform today.
The safe execution path — the hands an agent will eventually use.
Released onto this platform and this licence. No date, and no re-platforming when it arrives.
Read it from where you sit
CIO · CFO
Head of Infrastructure · NOC
SRE · Platform Engineering
FAQ
Find answers to common questions about ObserveOps Infinity and our platform capabilities.
No. Two things moved and both move in your favour: hardware requirements went down, and Log/Flow moved from per GB/day to per source, which decouples your licence from your data growth. The edition consolidation means capabilities that used to sit behind a higher tier are now included. Your specific commercials are a conversation with your account manager — but the direction of the model is toward less cost and more predictability, not more.
Every one of these foundations cost us something — engineering years, licence revenue we chose not to gate, a pricing model that no longer grows automatically with a customer's data. We consider that the correct trade. A product ecosystem is only worth building if the customer gets the benefit of the engineering, not the invoice for it.
Four foundations. One edition.