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.
Member payment status comes from your payment provider; it is not modeled here and no PCI claim is made.

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).

Representative Queries

• Creator businesses: asset library using Next.js
• Where can I host Creator businesses: Asset library built with Next.js?
• I need a genuinely specialized asset library workflow covering sponsor/client workspaces, publication guides and content assets.

Resource Requirements

• primitive:compute
• primitive:postgres
• primitive:s3-compatible-object-storage

Infrastructure Requirements

1. Compute
   • Status: verified
   • Summary: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
2. Postgres
   • Status: verified
   • Summary: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
3. S3-compatible object storage
   • Status: verified
   • Summary: 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

Tested Configuration

• Template: node-22
• Runtime: node
• Size: s-1vcpu-1gb
• Install: npm install
• Build: npm run build --if-present
• Start: npm run start

Workflow Steps

1. Model the creator businesses domain
   Create the tables customer_workspaces, content_items, customer_assets, releases, uploads. Member accounts or communities live in customer_workspaces; keep the sensitive classes (member identity and payment status, private community posts) out of this schema.
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. Re-running with no change is a no-op.
7. Verify
   Run the pattern self-test(s) from the example (/p/browser-file-uploads) and your own acceptance checks for the creator businesses workflow.

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.
• No health, financial, privacy or other compliance claim is made. Member payment status comes from your payment provider; it is not modeled here and no PCI claim is made.
• 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

• Currency: USD
• Monthly Amount: 10.0
• Authoritative: true
• Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
• Components:
  • app server
    • Size: s-1vcpu-1gb
    • Quantity: 1.0
    • Monthly Amount: 5.0
  • managed PostgreSQL database
    • Size: s-1vcpu-1gb
    • Quantity: 1.0
    • Monthly Amount: 5.0
• Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

Next Actions

1. Browse the catalog index
   • Method: GET
   • Relative Path: /v1/catalog
   • Requires Authentication: false
2. Search published recipes by intent, stack and constraints
   • Method: POST
   • Relative Path: /v1/catalog/search
   • Requires Authentication: false
3. Prepare a side-effect-free deployment plan for an authorized project
   • Method: POST
   • Relative Path: /v1/catalog/plan
   • Requires Authentication: true
4. Read the existing agent authentication setup
   • Method: GET
   • Relative Path: /mcp/setup
   • Requires Authentication: false
5. Browse Creator businesses
   • Method: GET
   • Relative Path: /v1/catalog/nodes/industry%3Acreator-businesses
   • Requires Authentication: false
6. Browse Asset library
   • Method: GET
   • Relative Path: /v1/catalog/nodes/workload%3Aasset-library
   • Requires Authentication: false
7. Browse Next.js
   • Method: GET
   • Relative Path: /v1/catalog/nodes/stack%3Aframework-next-js
   • Requires Authentication: false
8. Browse Deploy web app
   • Method: GET
   • Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app
   • Requires Authentication: false

Examples

• Next.js pattern fixture: Verified browser file uploads basis for this blueprint.
  • Source Ref: tests/deploy-canaries/next-js-patterns

Evidence Summary

1. Canary Run
   • Summary: Next.js pattern fixture deployed on Ample; 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. The blueprint's Creator businesses schema and workflow below build on that verified basis and were not separately executed.
   • Observed At: 2026-09-21T02:34:39Z
   • Implementation Revision: 1d28ae0-dirty (CLI 0.1.21)
   • Expires At: 2027-03-20T02:34:39Z
   • Scope: checks: /p/browser-file-uploads, pattern: browser-file-uploads, template: node-22