Creator businesses: asset library using Next.js

Summary

A asset library blueprint for creator businesses built with Next.js on Ample. Domain schema: customer_workspaces (name, membership_tier, joined_at): member accounts or communities; content_items (title, tier_required, object_key, published_at, version): versioned content releases; customer_assets (workspace_id, title, object_key, visibility): downloads granted to a member; releases (content_item_id, version, notes): release notes per version; uploads (id, owner_reference, object_key, content_type, size, uploaded_at): validated uploads linked to their owner. Public information: free content and previews, membership tiers, creator profile. Kept out of scope until handling is reviewed: member identity and payment status, private community posts.

Infrastructure requirements

• 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: 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.)
• S3-compatible object storage: verified (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 creator businesses 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 creator businesses domain. Create the tables customer_workspaces, content_items, customer_assets, releases, uploads.
2. Workflow step 1. Model assets linked to their owning group or workspace.
3. Workflow step 2. Validate uploads and store them in the private bucket; link each object to its row.
4. Workflow step 3. Authorize downloads by membership.
5. Workflow step 4. Deploy and verify rejection of disallowed files and a linked upload.
6. Deploy. Run the synchronous deploy once and read the result.
7. Verify. Run the pattern self-test(s) from the example and your own acceptance checks for the creator businesses workflow.

Tested examples

• Next.js pattern fixture: Verified browser file uploads basis for this blueprint.

Success checks

• App responds on its public URL.
• Browser-file-uploads self-test from the example.

Limitations

• The technical basis (browser file uploads on Next.js) was verified with the pattern fixture; the creator businesses schema and workflow are an original design for this blueprint and were not executed as a separate application.

Cost estimate

Estimated 10.00 USD per month.

Verification evidence

• canary_run on 2026-09-21T02:34:39Z at revision: Next.js pattern fixture deployed on Ample.

Execution binding

MCP tool ample_deploy, schema hash 876465fce906da0c observed 2026-09-21T03:19:59.461917+00:00 at revision 49962bcade4f.