Third-party
systems integrations

Keep your traffic, planning, and MAM systems where they are. Stream Circle can operate as the playout layer connected to existing broadcast systems through BXF, APIs, or agreed custom interfaces.

Planning, rights, commercials, metadata, media files, graphics, playout, and reporting often sit in separate tools. Stream Circle connects to these environments so broadcasters can modernise playout without replacing the systems already used by teams.

Best suited for: established broadcasters that want to modernise playout while keeping existing planning, MAM, or archive systems in place.

PROVYS Sphere + Stream Circle

From schedule to playout and back

PROVYS Sphere manages the planning and business side of broadcast operations. Stream Circle acts as the playout.

Together, they run TV channels according to the planned program: playlists and metadata move from PROVYS Sphere to Stream Circle, and as-run logs return for reconciliation, reporting, and follow-up processes.

Typical PROVYS Sphere + Stream Circle workflow

1. Plan in PROVYS Sphere
   Prepare schedules, programme metadata, commercial structures, rights windows, and timing information.
2. Export schedule data
   Send playlist data to Stream Circle using BXF standard or other compatible interfaces.
3. Prepare media for playout
   Stream Circle checks playlist requirements and downloads media from MAM, storage, or via other delivery workflows.
4. Run the playlist in Stream Circle
   Operators monitor the running playlist/s, handle live inputs, control graphics, and manage last-minute changes.
5. Return of as-run logs
   Stream Circle exports aired data back to PROVYS Sphere for reconciliation and reporting.

Integration scope

Depending on connected systems and project setup, Stream Circle integrations can cover:

• Playlist exchange
• Programme and commercial metadata
• Media availability
• Secondary graphics
• Operator changes
• As-run logs and other reporting data

Other third-party integrations

Stream Circle can interconnect with 3rd party traffic, planning, MAM, archive, storage, graphics, and reporting systems.

Typical integration scenarios include traffic systems, MAM or archive systems, content ingest and storage workflows, graphics and secondary event systems, as-run log reporting. Cloud, hybrid, or on-premises deployments are fully supported.