page:blueprints:nonprofits:member portal:next js

Nonprofits: member portal using Next.js

Summary

A member portal blueprint for nonprofits built with Next.js on Ample. Domain schema:

• course_groups (program, cohort, start_at, end_at): programs and cohorts;
• memberships (course_group_id, participant_reference, role): participants, volunteers and staff;
• sessions (course_group_id, starts_at, title, location): program sessions and events;
• materials (course_group_id, title, object_key, visibility): program materials;
• document_access (document_id, principal_reference, role, granted_at): who may read which document.

Public information: mission and programs, events, donation entry point. Kept out of scope until handling is reviewed: beneficiary identity and case notes, donor records. Beneficiary and donor data are sensitive; donations are handled by your payment provider and are not modeled here.

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

Framework

Next.js

Workload

Member portal

Industry

Nonprofits

Release Status

published

Support Status

verified

Execution Status

ready

Resource Requirements

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

Infrastructure Requirements

1. Compute: Verified, summary: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request.
2. Postgres: Verified, summary: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database.
3. S3-compatible object storage: Verified, summary: Buckets are S3-compatible with issued credentials.

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 nonprofits data classes may be handled at all; this blueprint models public information only

Workflow Steps

1. Model the nonprofits domain: Create the tables course_groups, memberships, sessions, materials, document_access.
2. Model groups, memberships and roles
3. Authorize access to materials by membership and role (401, 403 negative tests)
4. Store materials in the private bucket and stream them through the app
5. Deploy and verify the negative tests and an authorized download: Run the synchronous deploy once and read the result.
6. Verify: Run the pattern self-test(s) from the example (/p/private-document-library) and your own acceptance checks for the nonprofits workflow.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Basis: size prices from pricing.toml
  • App server: s-1vcpu-1gb, 5.0
  • Managed PostgreSQL database: s-1vcpu-1gb, 5.0
• Note: Always-on monthly price of the tested sizes.

Limitations

• Verified on the node-22 template.
• Managed PostgreSQL 16 only; extensions, connection limits not verified.

Tested Configuration

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

Next Actions

1. Browse the catalog index
2. Search published recipes by intent, stack and constraints
3. Prepare a side-effect-free deployment plan for an authorized project
4. Read the existing agent authentication setup
5. Browse Nonprofits
6. Browse Member portal
7. Browse Next.js
8. Browse Deploy web app

Success Checks

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

Evidence Summary

Next.js pattern fixture deployed on Ample; the private document library checks passed. The blueprint's Nonprofits schema and workflow build on that verified basis.