# Management consultancies: client portal using Next.js

A client portal blueprint for management consultancies built with Next.js on Ample. Domain schema: client_entities (name, industry, primary_contact_role): client organizations; engagements (client_entity_id, scope_title, phase, period_start, period_end): engagement periods and phases; workstreams (engagement_id, name, owner, status, due_at): tracked workstreams; deliverables (engagement_id, title, version, object_key, released_at): versioned deliverables shared with the client; document_access (document_id, principal_reference, role, granted_at): who may read which document. Public information: service offerings and case studies (anonymized), consultant profiles, engagement model. Kept out of scope until handling is reviewed: client strategy documents, financial models, interview notes. Client strategy material is confidential; authorization is modeled per engagement. 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 runs on

- [Computeverified](/content/discover/primitive/compute/index.html)  
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

- [Postgresverified](/content/discover/primitive/postgres/index.html)  
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](/content/discover/primitive/s3-compatible-object-storage/index.html)  
Buckets speak the S3 API with SigV4 credentials Ample Computer issues; `ample bucket upload-url` returns 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 create` passed as encrypted S3_* environment variables
- A review of which management consultancies 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

1. **Model the management consultancies domain.** Create the tables client_entities, engagements, workstreams, deliverables, document_access. Client organizations live in client_entities; keep the sensitive classes (client strategy documents, financial models, interview notes) 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.

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

7. **Verify.** Run the pattern self-test(s) from the example (/p/private-document-library) and your own acceptance checks for the management consultancies 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

1. 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 Management consultancies 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 management consultancies schema and workflow are an original design for this blueprint, built on that basis.
- Client strategy material is confidential; authorization is modeled per engagement.
- 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-url` returns presigned upload URLs.
