## Creator businesses: client portal using Next.js

### Summary
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; it is not modeled here and no PCI claim is made. 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).

### Representative Queries
1. Creator businesses: client portal using Next.js
2. Where can I host Creator businesses: Client portal built with Next.js?
3. I need a genuinely specialized client portal workflow covering sponsor/client workspaces, publication guides and content assets.

### Workflow Steps
1. **Model the creator businesses domain**: Create the tables customer_workspaces, content_items, customer_assets, releases, document_access. 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 client entities and engagement periods; every document belongs to one engagement.
3. **Workflow step 2**: Authorize by client entity and role before any storage access (401 without identity, 403 for the wrong client).
4. **Workflow step 3**: Store documents in the private bucket and stream them through the app.
5. **Workflow step 4**: Deploy and verify the negative authorization tests and an authorized download.
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/private-document-library) and your own acceptance checks for the creator businesses workflow.

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

### Success Checks
1. App responds on its public URL.
2. Private-document-library self-test from the example.

### Limitations
- 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 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.

### Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **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 tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

### 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 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 and were not separately executed.

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

### Formats
- [HTML](/content/blueprints/creator-businesses/client-portal/next-js/index.html)
- [Markdown](/content/blueprints/creator-businesses/client-portal/next-js.md)
- [JSON](https://api.ample.computer/v1/catalog/recipes/page%3Ablueprints%3Acreator-businesses%3Aclient-portal%3Anext-js)
