# Video production: documentation site using Next.js ## Summary A documentation site 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; state_transitions (record_type, from_state, to_state): the allowed state machine. 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 workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). ## Infrastructure requirements - [Compute](/discover/primitive/compute): verified (Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.) - [Postgres](/discover/primitive/postgres): verified (Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.) - [CDN](/discover/primitive/cdn): verified (The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.) ## 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 and a published bucket for public assets (CDN_*) - A review of which video production data classes may be handled at all; this blueprint models public information only ## Exact tested configuration - template: `node-22` - runtime: `node` - size: `s-1vcpu-1gb` - install: `npm install` - build: `npm run build --if-present` - start: `npm run start` ## Steps 1. **Model the video production domain.** Create the tables customer_workspaces, projects, cuts, customer_assets, state_transitions. 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 versioned documents with a state machine (draft, review, published) scoped to a product version 3. **Workflow step 2.** Publish assets for released versions to the CDN bucket 4. **Workflow step 3.** Serve only published versions publicly 5. **Workflow step 4.** Deploy and verify the version list and a published page 6. **Deploy.** Run the synchronous deploy once and read the result. Re-running with no change is a no-op. ``` ample deploy . --name --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=... --env CDN_PUBLIC_URL=... ``` 7. **Verify.** Run the pattern self-test(s) from the example (/p/relational-records) and your own acceptance checks for the video production workflow. ``` ample logs --kind build ``` ## Tested examples - **Next.js pattern fixture** (tests/deploy-canaries/next-js-patterns): Verified relational records basis for this blueprint. ## Success checks - app responds on its public URL (`/` on the live URL, expect ample canary next js patterns) - relational-records self-test from the example (`/p/relational-records` on the live URL, expect to see the pattern fixture checks) ## Limitations - The technical basis (relational records 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 Estimated 10.00 USD per month (size prices from pricing.toml at build revision a1b8c38919e59cd035ebabaced73cf84ece24371). - app server x1 `s-1vcpu-1gb`: 5.00 USD - managed PostgreSQL database x1 `s-1vcpu-1gb`: 5.00 USD Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included. ## Verification evidence - canary_run on 2026-09-21T02:34:39Z at revision `1d28ae0-dirty (CLI 0.1.21)`: 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 relational records checks passed: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). The blueprint's Video production schema and workflow below build on that verified basis and were not separately executed. (expires 2027-03-20T02:34:39Z) Last verified: 2026-09-21T02:34:39Z ## Execution binding MCP tool `ample_deploy` (registry `mcp:ample_deploy`), schema hash `876465fce906da0c` observed 2026-09-21T03:19:59.461917+00:00 at revision `49962bcade4f`, binding state `current`, required scopes: servers:write, databases:read, buckets:read.