# Video production: client portal using Next.js

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; upload large files straight to the bucket with `ample bucket upload-url`. 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).

**Verified** November 5, 2026

## What it runs on

- [Computeverified](/content/discover/primitive/compute/index.html)
  Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

- [Postgresverified](/content/discover/primitive/postgres/index.html)
  Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

- [S3-compatible object storageverified](/content/discover/primitive/s3-compatible-object-storage/index.html)
  Buckets speak the S3 API with SigV4 credentials Ample Computer issues; `ample bucket upload-url` returns a presigned upload URL. PutObject and GetObject are checked by canary.

## You need

- 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

## Exact tested configuration

- `build` npm run build --if-present
- `install` npm install
- `runtime` node
- `sizes` 1vcpu-1gb
- `start` npm run start
- `template` node-22

## Steps

1. **Model the video production domain.** Create the tables customer_workspaces, projects, cuts, customer_assets, document_access. 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 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.

```
   $ ample deploy . --name <app-name> --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...
   ```

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.

```
   $ ample logs <deployment_id> --kind build
   ```

## How it was checked

✓ app responds on its public URL · http get/ → “ample canary next js patterns”  
✓ private-document-library self-test from the example · http get/p/private-document-library → “see the pattern fixture checks”

## Evidence

1. November 5, 2026 · canary run  
   Next.js pattern fixture deployed on Ample (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template); the private document library checks passed: 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). The blueprint's Video production schema and workflow below build on that verified basis.

## Tested examples

- **Next.js pattern fixture.** Verified private document library basis for this blueprint.

## What it doesn’t cover

- 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, built on that basis.
- Footage is large and confidential; upload large files straight to the bucket with `ample bucket upload-url`.
- Verified on the node-22 template at s-1vcpu-1gb.
- Managed PostgreSQL 16 with pgvector.
- Buckets speak the standard S3 API (PutObject and GetObject with path-style addressing are checked by the fixture); `ample bucket upload-url` returns presigned upload URLs.
