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:
- client_entities (legal_name, entity_type, fiscal_year_end, jurisdiction): the businesses and individuals served;
- engagements (client_entity_id, service_line, period_start, period_end, status): bookkeeping, tax and audit engagements by period;
- document_requests (engagement_id, title, due_at, status, uploaded_object_key): requests for source documents;
- deliverables (engagement_id, title, object_key, released_at): returns and statements released to the client;
- document_access (document_id, principal_reference, role, granted_at): who may read which document.
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:
- Accounting firms: client portal using Next.js
- Where can I host Accounting firms: Client portal built with Next.js?
- I need a genuinely specialized client portal workflow covering engagement periods, client entities and document authorization.
Resource Requirements:
- primitive:compute
- primitive:postgres
- primitive:s3-compatible-object-storage
Infrastructure Requirements:
- Compute: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
- 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.
- 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:
- 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 createpassed as encrypted S3_* environment variables - A review of which accounting firms data classes may be handled at all; this blueprint models public information only.
Tested Configuration:
- Template: node-22
- Runtime: node
- Size: s-1vcpu-1gb
- Install: npm install
- Build: npm run build --if-present
- Start: npm run start
Workflow Steps:
- 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.
- Model client entities and engagement periods; every document belongs to one engagement.
- Authorize by client entity and role before any storage access (401 without identity, 403 for the wrong client).
- Store documents in the private bucket and stream them through the app.
- 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=...
- 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:
- Title: Next.js pattern fixture
- Description: Verified private document library basis for this blueprint.
- Source Ref: tests/deploy-canaries/next-js-patterns
Success Checks:
- app responds on its public URL
- Kind: http_get
- Path: /
- Expect: ample canary next js patterns
- private-document-library self-test from the example
- Kind: http_get
- Path: /p/private-document-library
- Expect: see the pattern fixture checks.
Limitations:
- The technical basis (private document library on Next.js) was verified with the pattern fixture; the accounting firms 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. Financial records and tax identifiers are regulated in most jurisdictions; the portal flows here model authorization only and claim no compliance.
- Public content and synthetic examples only until actual data-handling requirements have been reviewed.
- Verified on the node-22 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified.
- PutObject and GetObject with path-style addressing are verified; other S3 operations and CDN cache rules are not.
Cost Estimate:
- Currency: USD
- Monthly Amount: 10.0
- Authoritative: true
- Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
- Components:
- Name: app server
Size: s-1vcpu-1gb
Quantity: 1.0
Monthly Amount: 5.0 - Name: managed PostgreSQL database
Size: s-1vcpu-1gb
Quantity: 1.0
Monthly Amount: 5.0
- Name: app server
- Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.