## Video production: asset library using Django

### Summary
A asset library blueprint for video production built with Django on Ample. Domain schema: customer_workspaces (client_name, project_count): client organizations; projects (workspace_id, title, stage, delivery_due_at): productions in flight; cuts (project_id, version, object_key, review_status, reviewed_at): versioned cuts for review; customer_assets (workspace_id, project_id, object_key, visibility): final deliverables and raw footage access; uploads (id, owner_reference, object_key, content_type, size, uploaded_at): validated uploads linked to their owner. Public information: showreel and services, production process, contact. Kept out of scope until handling is reviewed: unreleased footage, talent releases and contracts, client brand material. Footage is large and confidential; the storage checks here use small objects, so verify large-file behavior separately. Technical basis verified on Django: content-type and size validation that rejects disallowed files, an object written to a private bucket and a row linking the record to the object key (reject=ok upload=ok linked=ok).

### Representative Queries
- Video production: asset library using Django
- Where can I host Video production: Asset library built with Django?
- I need a genuinely specialized asset library workflow covering project reviewers, delivery specifications and video asset versions.

### Resource Requirements
- **Compute**
- **Postgres**
- **S3-compatible object storage**

### Infrastructure Requirements
- **Compute**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
- **Postgres**: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
- **S3-compatible object storage**: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

### Workflow Steps
1. **Model the video production domain**: Create the tables customer_workspaces, projects, cuts, customer_assets, uploads. Client organizations live in customer_workspaces; keep the sensitive classes (unreleased footage, talent releases and contracts, client brand material) out of this schema.
2. **Workflow step 1**: Model assets linked to their owning group or workspace
3. **Workflow step 2**: Validate uploads and store them in the private bucket; link each object to its row
4. **Workflow step 3**: Authorize downloads by membership
5. **Workflow step 4**: Deploy and verify rejection of disallowed files and a linked upload
6. **Deploy**: Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
7. **Verify**: Run the pattern self-test(s) from the example (/p/browser-file-uploads) and your own acceptance checks for the video production workflow.

### Examples
- **Django pattern fixture**: Verified browser file uploads basis for this blueprint. Source: tests/deploy-canaries/django-patterns

### Success Checks
- **App responds on its public URL**
- **Browser-file-uploads self-test from the example**

### Limitations
- The technical basis (browser file uploads on Django) was verified with the pattern fixture; the video production schema and workflow are an original design for this blueprint and were not executed as a separate application.
- No health, financial, privacy or other compliance claim is made. Footage is large and confidential; the storage checks here use small objects, so verify large-file behavior separately.
- Public content and synthetic examples only until actual data-handling requirements have been reviewed.

### Cost Estimate
- Currency: **USD**
- Monthly Amount: **10.0**
- Components:
  - **App server**: s-1vcpu-1gb, quantity: 1.0, monthly amount: 5.0
  - **Managed PostgreSQL database**: s-1vcpu-1gb, quantity: 1.0, monthly amount: 5.0
  - Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

### Next Actions
1. **Browse the catalog index**
2. **Search published recipes by intent, stack and constraints**
3. **Prepare a side-effect-free deployment plan for an authorized project**