page:blueprints:accounting firms:client portal:next js

Accounting firms: client portal using Next.js

A client portal blueprint for accounting firms built with Next.js on Ample. Domain schema:

Public information:

Service lines and typical engagement periods, filing calendars and deadlines, office locations. Kept out of scope until handling is reviewed: tax identifiers and financial statements, bank and payroll records, identity documents.

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:

Resource Requirements:

Infrastructure Requirements:

  1. Compute: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
  2. Postgres: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
  3. S3-compatible object storage: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

Framework:

Next.js

Workload:

Client portal

Industry:

Accounting firms

Release Status:

Published

Support Status:

Verified

Execution Status:

Ready

Prerequisites:

Tested Configuration:

Workflow Steps:

  1. Model the accounting firms domain: Create the tables client_entities, engagements, document_requests, deliverables, document_access. The businesses and individuals served lives in client_entities; keep the sensitive classes (tax identifiers and financial statements, bank and payroll records, identity documents) out of this schema.
  2. Model client entities and engagement periods; every document belongs to one engagement.
  3. Authorize by client entity and role before any storage access (401 without identity, 403 for the wrong client).
  4. Store documents in the private bucket and stream them through the app.
  5. Deploy: Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
    • Command: ample deploy . --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 accounting firms workflow.
    • Command: ample logs --kind build

Examples:

Success Checks:

  1. app responds on its public URL
    • Kind: http_get
    • Path: /
    • Expect: ample canary next js patterns
  2. private-document-library self-test from the example
    • Kind: http_get
    • Path: /p/private-document-library
    • Expect: see the pattern fixture checks.

Limitations:

Cost Estimate: