Digital agencies: client portal using Laravel

Summary

A client portal blueprint for digital agencies built with Laravel on Ample. Domain schema: client_entities (name, brand, primary_contact_role): client brands; engagements (client_entity_id, campaign_or_project, period_start, period_end, status): retainers and projects; approval_rounds (engagement_id, round_no, asset_object_key, status, decided_at): creative approval rounds; deliverables (engagement_id, title, object_key, version): final assets delivered; document_access (document_id, principal_reference, role, granted_at): who may read which document. Public information: services and case studies, team, contact. Kept out of scope until handling is reviewed: unreleased creative and campaign plans, client analytics exports, brand credentials. Unreleased creative is confidential; brand platform credentials never belong in these flows. 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).

Infrastructure requirements

• Compute: verified (Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.)
• Postgres: verified (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: verified (Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.)

Prerequisites

• 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 create passed as encrypted S3_* environment variables
• A review of which digital agencies data classes may be handled at all; this blueprint models public information only

Exact tested configuration

• template: php-8.5
• runtime: php
• size: s-1vcpu-1gb
• install: composer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader
• start: frankenphp php-server --listen :$PORT --root public

Steps

1. Model the digital agencies domain. Create the tables client_entities, engagements, approval_rounds, deliverables, document_access. Client brands live in client_entities; keep the sensitive classes (unreleased creative and campaign plans, client analytics exports, brand credentials) 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.

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

6. Verify. Run the pattern self-test(s) from the example (/p/private-document-library) and your own acceptance checks for the digital agencies workflow.

   ample logs <deployment_id> --kind build
   

Tested examples

• Laravel pattern fixture (tests/deploy-canaries/laravel-patterns): Verified private document library basis for this blueprint.

Success checks

• app responds on its public URL (/ on the live URL, expect ample canary laravel patterns)
• private-document-library self-test from the example (/p/private-document-library on the live URL, expect to see the pattern fixture checks).

Limitations

• The technical basis (private document library on Laravel) was verified with the pattern fixture; the digital agencies 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. Unreleased creative is confidential; brand platform credentials never belong in these flows.
• Public content and synthetic examples only until actual data-handling requirements have been reviewed.
• Verified on the php-8.5 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 verified.

Cost estimate

Estimated 10.00 USD per month (size prices from pricing.toml at build revision a1b8c38919e59cd035ebabaced73cf84ece24371).

• app server x1 s-1vcpu-1gb: 5.00 USD
• managed PostgreSQL database x1 s-1vcpu-1gb: 5.00 USD

Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

Verification evidence

• canary_run on 2026-09-20T20:36:21Z at revision 118ad1c6d7d23d4c2ce069254bab9ec9d37cd57b-dirty (CLI 118ad1c): 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 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 Digital agencies schema and workflow below build on that verified basis and were not separately executed. (expires 2027-03-19T20:36:21Z)

Execution binding

MCP tool ample_deploy (registry mcp:ample_deploy), schema hash 876465fce906da0c observed 2026-09-21T03:19:59.461917+00:00 at revision 49962bcade4f, binding state current, required scopes: servers:write, databases:read, buckets:read.