Creator businesses: client portal using Next.js · Ample Computer
Creator businesses: client portal using Next.js
A client portal 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; document_access (document_id, principal_reference, role, granted_at): who may read which document. 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. Technical basis verified on Next.js: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok).
Verified November 5, 2026
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 creator businesses 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 creator businesses domain. Create the tables customer_workspaces, content_items, customer_assets, releases, document_access. Member accounts or communities lives in customer_workspaces; keep the sensitive classes (member identity and payment status, private community posts) out of this schema.
Workflow step 1. Model client entities and engagement periods; every document belongs to one engagement.
Workflow step 2. Authorize by client entity and role before any storage access (401 without identity, 403 for the wrong client).
Workflow step 3. Store documents in the private bucket and stream them through the app.
Workflow step 4. Deploy and verify the negative authorization tests and an authorized download.
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/private-document-library) and your own acceptance checks for the creator businesses workflow.
$ ample logs <deployment_id> --kind build
How it was checked
✓ app responds on its public URL· http get/ → “ample canary next js patterns”
✓ private-document-library self-test from the example· http get/p/private-document-library → “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 private document library checks passed: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok). The blueprint's Creator businesses schema and workflow below build on that verified basis.
Tested examples
- Next.js pattern fixture. Verified private document library basis for this blueprint.
What it doesn’t cover
The technical basis (private document library on Next.js) was verified with the pattern fixture; the creator businesses schema and workflow are an original design for this blueprint, built on that basis.
Member payment status comes from your payment provider.
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.