TAMS is a specification, not a product. What makes it useful in practice is the implementations built on top of it — the recorders, players, servers and application layers that turn the spec into working systems.

This page lists known implementations: products and platforms that use TAMS natively as their storage and retrieval foundation.

Implementation: Phrame

Phrame is a cloud-native media platform built natively on TAMS. It provides everything needed to deploy a production TAMS-based system — recorders, the TAMS server, players, monitoring, browser-based operator interfaces and output tools — packaged as containerised components that can be combined into deployable solutions.

What Phrame does

Phrame can be understood in two ways, depending on who is asking.

For product managers and commercial teams, Phrame is a platform that delivers specific solutions: a compliance recorder, a news logger, a remote monitoring system, a replay and review tool. Each of these is a defined, deployable product with a clear outcome.

For broadcast engineers, Phrame is a component-based platform. Each media function — signal input, recording, playback, monitoring, graphics, overlay, multiviewing, WebRTC delivery — is packaged as a separate containerised service. These services can be orchestrated, scaled and combined to match the exact system required.

The practical consequence is that Phrame can be sold and deployed as a finished solution, while the underlying platform remains flexible enough to extend, customise and redeploy for new requirements.

Phrame components

A Phrame-based system is assembled from specialist media services, including:

• Input processors — accept media from SDI, SRT, NDI, transport stream and other sources
• TAMS recorders — write incoming media to the TAMS store in real time
• TAMS server — maintains the time-indexed registry of stored media
• TAMS players — retrieve media from the store for playback and delivery
• Compositor / multiviewer — combines multiple feeds into configurable layouts for monitoring
• Overlay engine — adds graphics, clocks, metadata displays and other overlays
• HTML renderer — renders browser-based operator interfaces and control views
• WebRTC delivery — low-latency streaming of media and multiviewer layouts to browsers
• File playback module — plays back recorded content in forward, reverse and variable speed
• Output processors — deliver media to SDI, HLS, or other downstream destinations
• S3-compatible storage integration — writes to and reads from any S3-compatible object store
• Observability — monitoring and metrics using industry-standard tools

Phrame packaged solutions

Phrame components are pre-integrated into the following deployable solutions:

Compliance recording Records required feeds continuously, stores media in S3-compatible storage, and provides browser-based search, review and export for authorised users. The recorded media is simultaneously available for other applications — news logging, highlights, audit — without duplication.

News logging Captures live feeds at configurable quality and bitrate settings. Journalists and editors access content via a browser interface — search by time, create clips, export to standard formats.

Remote monitoring and multiviewing Multiple live feeds are displayed in configurable browser-based layouts. Operators access their own views from any location. Low-latency WebRTC delivery. The same compositor output can drive SDI or HLS for facility displays.

Replay and review Frame-accurate retrieval from any recorded feed. Forward, reverse and variable-speed playback. Clip export to MP4 or MXF.

Phrame and infrastructure

Phrame is designed to be infrastructure-agnostic. The platform runs on public cloud (AWS, GCP, Azure), private cloud, and on-premise environments. Storage uses any S3-compatible object store — including AWS S3, Google Cloud Storage, MinIO and Garage.

For organisations deploying Phrame through infrastructure partners, the platform can run on top of existing distributed infrastructure, enabling media services to be offered without requiring dedicated broadcast hardware at every location.

Deployment model

Phrame is deployed as containerised services using standard orchestration tools. Configuration can be version-controlled. The platform exposes observability data via Prometheus-compatible metrics and standard dashboards.

Find out more about Phrame

For further information about Phrame, contact us.

Other implementations

The TAMS ecosystem is growing. Additional implementations — including tools from the open-source community and other commercial products — will be listed here as they are confirmed.

If you have built something on TAMS and would like it listed, please get in touch via the community channels on the About page.

Note on interoperability

Because TAMS is an open specification, implementations from different vendors or developers are interoperable at the storage and index layer. A recorder from one implementation can write to a TAMS store that is read by a player from another. This is a deliberate design goal of the specification.