Digital agencies: form collection using Next.js · Ample Computer
Digital agencies: form collection using Next.js
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.
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).
What it runs on
Computeverified
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.Postgresverified
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
Buckets speak the S3 API with SigV4 credentials Ample Computer issues;ample bucket upload-urlreturns 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 createpassed as encrypted S3_* environment variablesA review of which digital agencies 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
Model the digital agencies domain. Create the tables client_entities, engagements, approval_rounds, deliverables, uploads. Client brands lives in client_entities; keep the sensitive classes (unreleased creative and campaign plans, client analytics exports, brand credentials) out of this schema.
Workflow step 1. Model document requests per engagement with due dates and status.
Workflow step 2. Validate uploaded files (type, size) before storing them in the private bucket and linking them to the request.
Workflow step 3. Authorize uploads by client entity.
Workflow step 4. Deploy and verify rejection of disallowed files and a linked upload.
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=...
- Verify. 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 <deployment_id> --kind build
How it was checked
- ✓ app responds on its public URL· http get/ → "ample canary next js patterns"
- ✓ browser-file-uploads self-test from the example· http get/p/browser-file-uploads → "see the pattern fixture checks"
Evidence
- 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 browser file uploads 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 (reject=ok upload=ok linked=ok). The blueprint's Digital agencies schema and workflow below build on that verified basis.
Tested examples
- Next.js pattern fixture. Verified browser file uploads basis for this blueprint.
What it doesn’t cover
The technical basis (browser file uploads on Next.js) was verified with the pattern fixture; the digital agencies schema and workflow are an original design for this blueprint, built on that basis.
Unreleased creative is confidential; brand platform credentials never belong in these flows.
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-urlreturns presigned upload URLs.