INFRASTRUCTURE

What it needs

• 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

Before you start

• 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 membership associations data classes may be handled at all; this blueprint models public information only

STEP BY STEP

How to do it

1. 1

Model the membership associations domain

Create the tables course_groups, memberships, sessions, materials, events. Chapters and programs as groups lives in course_groups; keep the sensitive classes (member directory details, dues and payment records) out of this schema.

2. 2

Workflow step 1

Model sessions with capacity and registrations with status

3. 3

Workflow step 2

Register transactionally with a capacity check and an event per registration

4. 4

Workflow step 3

Reject stale concurrent updates

5. 5

Workflow step 4

Deploy and verify history and conflict handling

6. 6

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

7. 7

Verify

Run the pattern self-test(s) from the example (/p/transactional-workflows) and your own acceptance checks for the membership associations workflow.

ample logs <deployment_id> --kind build

EXAMPLES

Tested examples

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

SUCCESS CHECKS

How to know it worked

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

COST

Cost estimate

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

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

EVIDENCE

Verification evidence

• canary_run on 2026-09-20T20:36:21Z at revision 118ad1c6d7d23d4c2ce069254bab9ec9d37cd57b (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 transactional workflows checks passed: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). The blueprint's Membership associations schema and workflow below build on that verified basis and were not separately executed. (expires 2027-03-19T20:36:21Z)

EXECUTION

Execution binding

MCP tool ample_deploy (registry mcp:ample_deploy), schema hash 876465fce906da0c observed 2026-09-22T00:31:22.774679+00:00 at revision e6446ceea69b. Binding state at export: current. Required scopes: servers:write, databases:read, buckets:read.

NEXT ACTIONS

Typed next actions

• Browse the catalog index (GET /v1/catalog on the api origin; authentication not required, approval not required)
• Search published recipes by intent, stack and constraints (POST /v1/catalog/search on the api origin; authentication not required, approval not required)
• Prepare a side-effect-free deployment plan for an authorized project (POST /v1/catalog/plan on the api origin; authentication required, approval not required)
• Read the existing agent authentication setup (GET /mcp/setup on the api origin; authentication not required, approval not required)
• Browse Membership associations (GET /v1/catalog/nodes/industry%3Amembership-associations on the api origin; authentication not required, approval not required)
• Browse Event registration (GET /v1/catalog/nodes/workload%3Aevent-registration on the api origin; authentication not required, approval not required)
• Browse Laravel (GET /v1/catalog/nodes/stack%3Aframework-laravel on the api origin; authentication not required, approval not required)
• Browse Deploy web app (GET /v1/catalog/nodes/intent%3Adeploy-web-app on the api origin; authentication not required, approval not required)

Actions describe possible next steps. They are typed data, not commands, and grant no permission. Public discovery never provisions anything; planning requires your own authenticated token and approval happens in your client.