SECURITY & DEPLOYMENTYour footage.
A defined boundary.
Customer review belongs in an authenticated, customer-scoped environment. The public sales demo is a separate simulation with no customer uploads.
Architecture and pilot requirements below reflect the product repository. They are not a certification or confirmation that every control has passed acceptance in a particular deployment.
PRODUCT ARCHITECTURE / AZUREFollow the media. Follow the decision.
- 01 / Named userCustomer OIDC identity React frontend on Azure Static Web Apps.
- 02 / Governed ingestAzure Container Apps API private Azure Blob Storage for media and documents; short-lived signed playback.
- 03 / ProcessingSeparately scaled Container Apps workers scanning, extraction, FFmpeg media measurements and Microsoft Foundry specialist review.
- 04 / Evidence & decisionTenant-scoped PostgreSQL records findings, citations, revisions and human dispositions version-bound signed approval snapshot.
This describes the product deployment. This public marketing website is hosted separately.
Media handling
The pilot design uses private media storage and isolated processing workers. Originals, proxies, thumbnails, captions and document extractions must be included in the agreed data inventory. Upload only media you are authorized to process.
Access controls
The product supports viewer, editor, approver and admin roles, server-derived identity and organization checks, and revocable access. Pilots require customer OIDC configuration and demonstrated cross-organization denial. Public demo access is not a customer workspace.
Retention & deletion
There is no universal retention period promised here. Agree durations for originals, derivatives, extracted text, indexes, logs and backups before upload, including legal holds and exported copies. Deletion and recovery exercises must retain verification evidence.
Regional processing
The pilot proposal calls for dedicated Azure resources in a customer-approved region. Confirm database, storage, scanning, worker and AI endpoint locations together. Model availability and routing must match the approved processing schedule; no blanket residency guarantee is implied.
AI boundaries
Live specialist review uses configured Microsoft Foundry deployments. The public demo uses stored or scripted examples. The pilot requires an agreed no-training policy and approved provider terms. Record model and source context, distinguish observation from inference, and keep release authority with a named human.
Before customer footage
Complete the customer-specific security packet: regions and subprocessors, retention, identity and isolation tests, encryption and key evidence, deletion and restore tests, incident contacts and notification terms. A deployment configuration alone is not acceptance evidence.
Review the boundary before the first upload.
Discuss deployment requirements See the pilot plan Source basis: product README, Private Deployment, Security Packet and Market Readiness documentation. Customer-specific terms and operational evidence are agreed during pilot scoping.