Management consultancies: client portal using Laravel · Ample Computer
Management consultancies: client portal using Laravel
A client portal blueprint for management consultancies built with Laravel 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 Laravel: 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 Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.
Postgresverified 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.
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 variablesA review of which management consultancies data classes may be handled at all; this blueprint models public information only
Exact tested configuration
install composer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader
runtime php
sizes - 1vcpu-1gb
start frankenphp php-server --listen :$PORT --root public
template php-8.5
Steps
Model the management consultancies domain. Create the tables client_entities, engagements, workstreams, deliverables, document_access. Client organizations lives in client_entities; keep the sensitive classes (client strategy documents, financial models, interview notes) out of this schema.
Workflow step 1. Model client entities and engagement periods; every document belongs to one engagement
Workflow step 2. Authorize by client entity and role before any storage access (401 without identity, 403 for the wrong client)
Workflow step 3. Store documents in the private bucket and stream them through the app
Workflow step 4. Deploy and verify the negative authorization tests and an authorized download
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/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 ✓ private-document-library self-test from the example
Evidence
- November 6, 2026 · canary run
Laravel pattern fixture deployed on Ample; 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
- Laravel pattern fixture. Verified private document library basis for this blueprint.
What it doesn’t cover
- The technical basis (private document library on Laravel) 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 php-8.5 template at s-1vcpu-1gb.
- Managed PostgreSQL 16 with pgvector.
- Buckets speak the standard S3 API.