# Video production: client portal using Next.js

## Summary
A client portal blueprint for video production built with Next.js 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; document_access (document_id, principal_reference, role, granted_at): who may read which document. 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 Next.js: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok).

## Representative Queries
- Video production: client portal using Next.js
- Where can I host Video production: Client portal built with Next.js?
- I need a genuinely specialized client portal workflow covering project reviewers, delivery specifications and video asset versions.

## Resource Requirements
- `primitive:compute`
- `primitive:postgres`
- `primitive:s3-compatible-object-storage`

## Infrastructure Requirements
1. **Compute**  
   Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
2. **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.
3. **S3-compatible object storage**  
   Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

## Prerequisites
- A Next.js project (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template)
- A PostgreSQL driver reading DATABASE_URL (auto-provisioned when omitted)
- Bucket credentials from `ample bucket create` passed as encrypted S3_* environment variables
- A review of which video production data classes may be handled at all; this blueprint models public information only

## Workflow Steps
1. **Model the video production domain**  
   Create the tables customer_workspaces, projects, cuts, customer_assets, document_access. Client organizations lives 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 client entities and engagement periods; every document belongs to one engagement.
3. **Workflow step 2**  
   Authorize by client entity and role before any storage access (401 without identity, 403 for the wrong client).
4. **Workflow step 3**  
   Store documents in the private bucket and stream them through the app.
5. **Workflow step 4**  
   Deploy and verify the negative authorization tests and an authorized download.
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/private-document-library) and your own acceptance checks for the video production workflow.

## Success Checks
- **App responds on its public URL**  
   Kind: `http_get`  
   Path: `/`  
   Expect: `ample canary next js patterns`
- **private-document-library self-test from the example**  
   Kind: `http_get`  
   Path: `/p/private-document-library`  
   Expect: `see the pattern fixture checks`

## Limitations
- The technical basis (private document library on Next.js) 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.
- Verified on the node-22 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified.
- PutObject and GetObject with path-style addressing are verified; other S3 operations and CDN cache rules are not.

## Cost Estimate
- **Monthly Amount:** $10.00 (USD)  
   - **Basis:** size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty  
   - **Components:**  
     - App server (s-1vcpu-1gb): $5.00  
     - Managed PostgreSQL database (s-1vcpu-1gb): $5.00
   - 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**  
   Method: `GET`  
   Relative Path: `/v1/catalog`
2. **Search published recipes by intent, stack and constraints**  
   Method: `POST`  
   Relative Path: `/v1/catalog/search`  
   Body:  
   ```json
   {"limit":5,"query":"Video production: client portal using Next.js"}
   ```
3. **Prepare a side-effect-free deployment plan for an authorized project**  
   Method: `POST`  
   Relative Path: `/v1/catalog/plan`  
   Body:  
   ```json
   {"inputs":{},"projectId":"","recipeId":"page:blueprints:video-production:client-portal:next-js","recipeRevision":"r1"}
   ```
4. **Read the existing agent authentication setup**  
   Method: `GET`  
   Relative Path: `/mcp/setup`
5. **Browse Video production**  
   Method: `GET`  
   Relative Path: `/v1/catalog/nodes/industry%3Avideo-production`
6. **Browse Client portal**  
   Method: `GET`  
   Relative Path: `/v1/catalog/nodes/workload%3Aclient-portal`
7. **Browse Next.js**  
   Method: `GET`  
   Relative Path: `/v1/catalog/nodes/stack%3Aframework-next-js`
8. **Browse Deploy web app**  
   Method: `GET`  
   Relative Path: `/v1/catalog/nodes/intent%3Adeploy-web-app`
