## The short version

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

## What it needs

- [Compute](/content/discover/primitive/compute/index.html): verified (Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.)
- [Postgres](/content/discover/primitive/postgres/index.html): 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](/content/discover/primitive/s3-compatible-object-storage/index.html): verified (Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.)

## Before you start

- 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

## How to do it

1.  Model the nonprofits domain

Create the tables course_groups, memberships, sessions, materials, document_access. Programs and cohorts live in course_groups; keep the sensitive classes (beneficiary identity and case notes, donor records) out of this schema.

2.  Workflow step 1

Model groups, memberships and roles

3.  Workflow step 2

Authorize access to materials by membership and role (401, 403 negative tests)

4.  Workflow step 3

Store materials in the private bucket and stream them through the app

5.  Workflow step 4

Deploy and verify the negative tests and an authorized download

```
   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=...
   ```

6.  Verify

Run the pattern self-test(s) from the example (/p/private-document-library) and your own acceptance checks for the nonprofits workflow.

```
   ample logs <deployment_id> --kind build
   ```

## Tested examples

- **Next.js pattern fixture** (`tests/deploy-canaries/next-js-patterns`): Verified private document library basis for this blueprint.

## How to know it worked

- app responds on its public URL (`/` on the live URL, expect ample canary next js patterns)
- private-document-library self-test from the example (`/p/private-document-library` on the live URL, expect see the pattern fixture checks)

## Cost estimate

Estimated 10.00 USD per month (size prices from pricing.toml at build revision ca0b484a7a9957c573a88d3a32dc603c3c10135a).

- app server x1 `s-1vcpu-1gb`: 5.00 USD
- managed PostgreSQL database x1 `s-1vcpu-1gb`: 5.00 USD

Upper-bound monthly price of the tested sizes. Buckets are allocation-priced per quota and not included.

## Verification evidence

- canary_run on 2026-09-21T02:34:39Z at revision `1d28ae0 (CLI 0.1.21)`: 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 Nonprofits schema and workflow below build on that verified basis and were not separately executed. (expires 2027-03-20T02:34:39Z)

## Execution binding

MCP tool `ample_deploy` (registry `mcp:ample_deploy`), schema hash `876465fce906da0c` observed 2026-09-22T00:31:22.774679+00:00 at revision `e6446ceea69b`. Binding state at export: schema_changed. Required scopes: servers:write, databases:read, buckets:read.