NAB Web Banner
Solutions

AMPP Explained

Your production reality changes fast. Your toolset should keep up.

Every production team knows the moment where the plan breaks.

A last-minute format request, a new distribution destination, a surprise remote contribution, an unexpected need for monitoring, a new replay requirement, a graphics change, a codec you did not anticipate, an integration that suddenly matters because the show moved locations.

The AMPP App Store exists for that moment.

It is where AMPP OS users select the capabilities they need and deploy them into their environment, without re-architecting their operation every time reality shifts. It is the place where software-defined production becomes practical, because the tools are ready, deployable, versioned, and designed to connect into a larger production system rather than living as isolated utilities.

This page exists for a simple reason: before someone creates an AMPP OS account, they need to understand what they gain access to, how broad the store is, and why the store matters as part of a complete production platform.

What the AMPP App Store is

The AMPP App Store is the catalog and delivery mechanism for AMPP OS applications, solutions, service licenses, and system packages. It is where you:

Choose the apps that match your production model, select the version you want to deploy, read release notes to understand what changed and make informed operational decisions, deploy to your AMPP OS environment with confidence that the app will connect to the rest of your system.

The store is designed for real operations, not demos. That is why it supports version selection, release transparency, and a structure that maps to how productions are actually built: inputs and outputs, processing, monitoring, control, switching, replay, workflow, automation, audio, graphics, and complete solutions.

Just as importantly, the store is not static. It is continuously evolving as new tools are added, existing tools gain capability, and Alliance Partner integrations expand what the ecosystem can do.

The AMPP OS Suite context

The AMPP App Store is one element of the AMPP OS Suite, alongside tools that help you plan, operate, and learn.

AMPP Assist is the AI help tool inside the suite. It is there to help teams move faster with more confidence, answering configuration questions, clarifying deployment choices, and reducing the friction that normally comes with complex systems.

Production Builder is where you plan and configure entire productions. It turns the store from a catalog into an operational workflow. You can design a production blueprint, define how components connect, then deploy the production with a single action.

The App Store is the place you go to find the ingredients. Production Builder is how you turn those ingredients into a deployable production.

AMPP OS is the backbone, the apps are the outcomes

A common misunderstanding in the market is to treat AMPP OS as “a set of apps.” That framing misses what makes the ecosystem valuable.

AMPP OS is the operational backbone. It provides the foundation that makes software-defined production reliable at scale: orchestration, lifecycle management, operational visibility, security, and performance engineering for real-time media.

That backbone can be deployed on-prem, in the cloud, or anywhere in between. Hybrid is not a special case. It is a normal deployment model.

This matters because production teams do not want two disconnected worlds, one for hardware and one for software. They want one operational system, one control model, and one way to extend capabilities without creating new complexity.

AMPP OS provides that operational fabric. The App Store is how you activate it with the right capabilities.

Leading the Media Revolution

Discover the future of media production and delivery with Grass Valley’s AMPP – the Agile Media Processing Platform that revolutionizes content creation, management, and distribution. Whether on-prem or in the cloud, AMPP provides your team with a flexible, scalable, and secure hybrid workflow that empowers you to work from anywhere.

Welcome to the dawn of a new age in Media Production and Delivery.

MXL, FrameCache and why apps connect like a system

Apps only feel “platform-grade” when they interconnect as one production system rather than as separate tools. True platform behavior means media, timing, and control operate cohesively—without friction between applications.

Inside AMPP OS, applications exchange media and timing with extremely low latency through shared memory architecture using FrameCache Professional, evolving toward full MXL-based exchange. The practical impact is straightforward: applications can be chained together in real time without file shuffling, unmanaged copies, or compromises in quality.

When media exchange is designed for density and low latency, operational and computational efficiency follow. You do more with the compute you already have, avoid the hidden cost of inefficient toolchains, and gain the flexibility to scale, reconfigure, or move productions between locations. That underlying media fabric is what separates a collection of tools from a true operational platform.

What is in the store

The goal of this page is not to list every feature of every app because the store evolves continuously. The goal is to show the breadth of categories and the kinds of building blocks available.

Below is a functional map of the store categories, based on the categories visible in your current AMPP App Store environment.

Core app familes:

AMPP Inputs

A catalog of input options including SDI, ST 2110, SRT, NDI, RIST, RTMP, and MXL flows. This is where you bring signals into AMPP OS across on-prem, cloud, and hybrid scenarios. In the current view, this category shows 18 products.

AMPP Outputs

Output options to deliver signals back out of AMPP OS across the same types of transport and integration paths. In the current view, this category shows 12 products.

Play and Record

Playback, clip players, recorders, time delay, and record-related utilities that support production and playout workflows. In the current view, this category shows 8 products.

Playout and Master Control

Tools and packages that support channel operations, master control functions, secondary events, preview, thumbnailing, SCTE monitoring, and related channel workflow components. In the current view, this category shows 22 products.

Production Switching

Production switcher applications and components that scale from compact configurations to advanced software production switching, including Live Producer X and Maverik X, with supporting driver components. In the current view, this category shows 14 products.

Replay

Replay and ingest components including LiveTouch X and Production Replay X options and related supporting utilities. In the current view, this category shows 11 products.

Graphics

Graphics and keying building blocks, including keyers and DVE plus HTML graphics related capabilities. In the current view, this category shows 10 products.

Monitoring

Multiviewers and monitoring tools such as Kaleido IP X variants plus waveform and analysis tools that help teams maintain operational confidence in live environments. In the current view, this category shows 17 products.

Tools

Platform and operational utilities such as control, timing, health monitoring, gateways, registries, and FrameCache components. In the current view, this category shows 18 products.

Workflow

Workflow building blocks and connectors that let you integrate systems and automate content movement and metadata driven actions, including cloud storage integrations, transcode integration points, triggers, and workflow engine components. In the current view, this category shows 30 products.

Processing

Processing tools including high-quality conversion, muxing, clean switching, and other media processing elements that allow you to adapt signals without breaking your production model. In the current view, this category shows 22 products.

Audio Production

Audio I/O and audio mixing building blocks, supporting different channel counts and operational use cases. In the current view, this category shows 4 products.

Automation

Automation building blocks that connect to orchestration and system control, enabling productions to execute complex action chains with speed and consistency. In the current view, this category shows 4 products.

Shading

Shading tools such as Creative Grading HUB configurations that help teams maintain consistent looks and creative control across productions. In the current view, this category shows 3 products.

Capturing

Capture utilities such as Web Capture X. In the current view, this category shows 1 product.

Framelight X

Apps that support the Framelight X environment, including editing, logging, render components, proxies, registrars, schedulers, and integrations. In the current view, this category shows 15 products.

Connected apps

Connected is where hybrid capability becomes real in practice. These are applications and connectors that bridge to external systems or hardware-driven environments while still behaving as part of AMPP OS.

In the connected view shown, families include categories such as Graphics, Production Switching, and Intercom, with examples including partner graphics tools, K-Frame CS X options, and Telos Infinity intercom components.

This is strategically important because it shows how the App Store supports a multi-vendor reality and how AMPP OS deployments can extend existing investments rather than forcing a reset.

Solutions & Service Licenses

Solutions are curated packages that assemble multiple components into deployable outcomes. The store view shown includes Playout and Master Control solutions and Live Solutions such as PCR configurations.

This is where a team can choose a complete functional bundle when they want speed and predictability, while still operating inside the same AMPP OS environment.

Service Licenses are capability unlocks and operational extensions that you can apply where needed, such as Dante channel licensing, JPEG-XS encoding and decoding, plus other functional enhancements that attach to production environments.

This matters because real operations do not only need applications. They need the right licenses in the right places at the right time, aligned with the operational model.

ACE-3901 side

ACE as the bridge between today and AMPP OS

A major reason AMPP OS can be deployed pragmatically is that it can connect to existing installations.

ACE-3901-GRID is part of how Grass Valley bridges SDI onboarding into AMPP OS and it is the first step in integrating hardware into AMPP OS and MXL workflows. The intent is not to force a binary shift but to enable a gradual, controlled evolution from traditional infrastructure into software-defined and hybrid production models.

Learn more about ACE-3901

The App Store is where that hybrid reality becomes tangible because you can deploy the components and connectors that turn integration into something repeatable rather than custom.

Tokens, PAYG and Subscription

The store UI shows two commercial modes that map directly to operational needs: PAYG and Subscription. In practice, teams want a model that matches how productions behave.

Tokens are how many AMPP OS environments manage consumption and allocation across tools, workloads, and time. Instead of designing operations around permanent overprovisioning, tokens let you align capacity with production rhythm.

For a production team, the value is business agility without sacrificing operational confidence: you can scale up for a major event, scale down afterward, and keep the system consistent.

A bias to watch here is that token models can be misunderstood as “metered complexity.” The messaging should keep the focus on what operators actually care about: predictable control, scalable capacity, and the ability to respond quickly to change.

Why this matters now

Software-defined production has moved from concept to adoption because the driver is simplification. Teams want to collapse stacks, reduce middleware, and standardize integration so deployments become repeatable and agile.

The AMPP App Store matters now because it operationalizes that shift. It makes software-defined capability deployable, version-controlled, and integrated into a platform that is built for real-time media exchange and real operations.

It is also a practical answer to a reality most teams are already living: distributed operations. When your team, your compute, and your contribution sources can be anywhere, the ability to select and deploy the right capability without rebuilding the system becomes a strategic advantage.

Education

If you are new to AMPP OS, the store can look like “a lot of options.” The goal of this site and the surrounding AMPP OS Suite experience is to make the ecosystem understandable.

Education is built into how AMPP OS is experienced

AMPP Assist supports learning in-context while configuring and deploying
Release notes provide operational clarity on what changed and why
Production Builder helps translate goals into a deployable system design
Categories help teams navigate by function instead of guessing product names

This reduces risk, speeds up onboarding, and makes it easier for teams to adopt software-defined models without losing the confidence they built in traditional control rooms.

Getting started

Access to the AMPP App Store is available with an AMPP OS account.

That account gives you access to the AMPP OS Suite experience, including the store, Production Builder, and AMPP Assist. The goal is not only to give you tools but to give you a system that helps you plan, deploy, and operate with confidence.

Moving Forward

Every production operates within its own rhythm. Some prioritize live immediacy. Others focus on operational consistency and repeatability. Others depend on hybrid flexibility to keep the operation resilient as workflows evolve.
The AMPP App Store helps you build the toolset that matches your reality, then adapt it as reality changes.
If you would like, we can help you map the right categories and components to your production model, including which elements should run on-prem, which belong in the cloud, and how to design a hybrid deployment that stays operationally simple.
Because when the platform removes friction, creators and operators get back what matters most: the freedom to build engaging content with confidence, at the pace your audience expects, and with the control your operation requires.