Accounting firms: project tracker using Laravel · Ample Computer
Accounting firms: project tracker using Laravel
A project tracker blueprint for accounting firms built with Laravel 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;
- state_transitions (record_type, from_state, to_state): the allowed state machine.
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. Financial records and tax identifiers are regulated in most jurisdictions; the portal flows here model authorization. Technical basis verified on Laravel: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true).
What it runs on
-
- Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.
-
- 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
- Buckets speak the S3 API with SigV4 credentials Ample Computer issues;
ample bucket upload-urlreturns a presigned upload URL. PutObject and GetObject are checked by canary.
- Buckets speak the S3 API with SigV4 credentials Ample Computer issues;
You need
- A Laravel project (composer install --no-dev from composer.lock, then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 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
Exact tested configuration
composer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader- runtime: php
- sizes: 1vcpu-1gb
frankenphp php-server --listen :$PORT --root public- template: php-8.5
Steps
Model the accounting firms domain.
- Create the tables client_entities, engagements, document_requests, deliverables, state_transitions. 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.
Workflow step 1.
- Model engagements and workstreams with explicit status transitions.
Workflow step 2.
- Scope every query by client entity.
Workflow step 3.
- Attach deliverables as private objects linked to workstreams.
Workflow step 4.
- Deploy and verify transitions and cross-client isolation.
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=...Verify.
- Run the pattern self-test(s) from the example (/p/relational-records) and your own acceptance checks for the accounting firms workflow.
$ ample logs <deployment_id> --kind build
How it was checked
- ✓ app responds on its public URL· http get/ → “ample canary laravel patterns”
- ✓ relational-records self-test from the example· http get/p/relational-records → “see the pattern fixture checks”
Evidence
- November 6, 2026 · canary run
- Laravel pattern fixture deployed on Ample (composer install --no-dev from composer.lock, then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 template); the relational records checks passed: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). The blueprint's Accounting firms schema and workflow below build on that verified basis.
Tested examples
- Laravel pattern fixture. Verified relational records basis for this blueprint.
What it doesn’t cover
- The technical basis (relational records on Laravel) was verified with the pattern fixture; the accounting firms schema and workflow are an original design for this blueprint, built on that basis.
- Financial records and tax identifiers are regulated in most jurisdictions; the portal flows here model authorization.
- Verified on the php-8.5 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-urlreturns presigned upload URLs.