December 18, 2025 · CincopaUI · Player · API · Integrations · Video

🎥 🗂️ Customer-Owned Cloud Backup for Ownership and Hosting-Ready Streaming

Available for Enterprise and large-scale customers

We are introducing Customer-Owned Cloud Backup, allowing Cincopa customers to continuously replicate their entire account into their own cloud environment.

This is a continuance backup, not a one-time export.
Your data stays continuously synchronized in your own cloud infrastructure - whether that is a public cloud such as AWS or Google Cloud, an isolated enterprise cloud deployment, or a customer-managed private data center.

Customer-owned cloud backup showing source and metadata backup and hosting-ready backup

💡 Our philosophy

We believe customers should choose Cincopa because of reliability, flexibility, and trust - not because their data is locked in.

Customer-Owned Cloud Backup was built to give customers full ownership of their content, long-term confidence in their platform choice, and a clear path for continuity or migration if their needs change.

This capability reflects our commitment to enterprise readiness, transparency, and customer-first architecture.

Customers can choose between two backup levels, depending on their recovery, compliance, and infrastructure needs:

  • 🔐 Backup Level 1: Source & Metadata Continuity Backup
  • 🎥 Backup Level 2: Hosting-Ready Streaming & Runtime Separation

|

🔐 Backup Level 1: Source & Metadata Continuity Backup

This level provides a continuously updated, customer-owned archive of your core media assets and related data.

Included in this level

  • Original source video files
  • Video metadata (titles, descriptions, tags)
  • Subtitles and captions (SRT and related files)
  • Attached files and supporting assets

Security, durability, and control

  • Stored in a private, customer-owned bucket or object storage
  • Optional customer-managed encryption
  • Optional object versioning to protect against accidental deletes or overwrites

What this level is for

  • Compliance and governance requirements
  • Long-term data ownership and retention
  • Internal archiving and audit needs
  • Guaranteed access to original content independent of Cincopa

This level ensures your core assets are always protected and owned by you.
It is designed for recovery and migration scenarios rather than immediate playback.

🎥 Backup Level 2: Hosting-Ready Streaming & Runtime Separation

This level builds on Level 1 and adds everything required to start streaming within minutes, without re-uploading or re-encoding.

Included in this level

Everything from Level 1, plus:

  • Streaming-ready assets (encoded renditions and manifests)
  • Thumbnails and poster images
  • ⚙️ Runtime metadata files
  • Full library structure (folders, galleries, playlists, courses)
  • Player and playback configuration data

Hosting-ready and CDN-flexible

  • Assets are stored in a deterministic, hosting-ready structure
  • A CDN can be configured to pull streaming assets directly from the private bucket or object storage
  • The storage remains private and secured
  • Customers can switch CDN providers without changing content or storage

Runtime separation use cases

This level enables a powerful enterprise deployment model:

  • Cincopa as a management studio for ingestion, transcoding, metadata management, library structure, and player configuration
  • Runtime delivery on customer-controlled infrastructure, outside of Cincopa

This is especially relevant for organizations such as banks, financial institutions, and regulated enterprises that require:

  • Playback infrastructure inside a private or restricted network
  • Full separation between content management and content delivery
  • Control over where runtime traffic is served and logged

⚖️ Why two levels

Different organizations have different risk profiles and infrastructure constraints.

  • 🔐 Level 1 focuses on ownership, security, and regulatory continuity
  • 🎥 Level 2 is designed for organizations that cannot afford downtime or that require full control over runtime delivery

Both levels provide:

  • Continuous replication rather than a one-time snapshot
  • Customer-owned infrastructure and credentials
  • Optional encryption and versioning controls
  • No impact on live playback or platform performance

⚙️ How it works

  • Continuous replication to customer-owned cloud or private object storage
  • Support for public cloud, isolated enterprise cloud deployments, and private data centers
  • CDN integration via origin pull from private storage

📌 Availability

Customer-Owned Cloud Backup is available for Enterprise and high-volume customers.

To enable this feature or discuss which backup level fits your organization, please contact your Cincopa account manager or sales team.

🔒 Closing note

Customer-Owned Cloud Backup is part of Cincopa’s long-term commitment to enterprise trust, customer ownership, and operational confidence.

For integrations that need time-limited API access, see self-generated temporary tokens (v3). The token update covers API access controls alongside the storage and continuity options described here.

Published December 28, 2025

NEXT STEP

Continue Exploring

Start with one product area, one documentation surface, one support library, one internal portal, or one embedded training flow. Get that collection working well, help viewers understand what is inside, then reuse the same gallery across adjacent destinations without duplicating the library.