# Digital agencies: form collection using Next.js

## Summary
A form collection blueprint for digital agencies built with Next.js on Ample. Domain schema:
- **client_entities** (name, brand, primary_contact_role): client brands
- **engagements** (client_entity_id, campaign_or_project, period_start, period_end, status): retainers and projects
- **approval_rounds** (engagement_id, round_no, asset_object_key, status, decided_at): creative approval rounds
- **deliverables** (engagement_id, title, object_key, version): final assets delivered
- **uploads** (id, owner_reference, object_key, content_type, size, uploaded_at): validated uploads linked to their owner.

**Public information:** services and case studies, team, contact. Kept out of scope until handling is reviewed: unreleased creative and campaign plans, client analytics exports, brand credentials. Unreleased creative is confidential; brand platform credentials never belong in these flows.

## Representative Queries
- Digital agencies: form collection using Next.js
- Where can I host Digital agencies: Form collection built with Next.js?
- I need a genuinely specialized form collection workflow covering client projects, creative review and campaign deliverables.

## Technical Basis
Technical basis verified on Next.js: 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).

## Resource Requirements
- **primitive:compute**
- **primitive:postgres**
- **primitive: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.

## 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 digital agencies data classes may be handled at all; this blueprint models public information only

## Workflow Steps
1. **Model the digital agencies domain:** Create the tables client_entities, engagements, approval_rounds, deliverables, uploads. Client brands live in client_entities; keep the sensitive classes (unreleased creative and campaign plans, client analytics exports, brand credentials) out of this schema.
2. **Model document requests per engagement with due dates and status.**
3. **Validate uploaded files (type, size) before storing them in the private bucket and linking them to the request.**
4. **Authorize uploads by client entity.**
5. **Deploy and verify rejection of disallowed files and a linked upload.**
6. **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=...)
7. **Run the pattern self-test(s) from the example (/p/browser-file-uploads) and your own acceptance checks for the digital agencies workflow.** (ample logs  --kind build)

## Examples
- **Next.js pattern fixture:** Verified browser file uploads basis for this blueprint.

## Limitations
- The technical basis was verified with the pattern fixture; the digital agencies 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.
- Verified on the node-22 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.

## Cost Estimate
- **Currency:** USD
- **Monthly Amount:** 10.0
- **Components:**
  - app server: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0
  - managed PostgreSQL database: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0
- **Note:** Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

## Evidence Summary
- 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 checks passed: 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.

## Last Verified At
2026-09-21T02:34:39Z