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

Before you start

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

How to do it

1. 1

Model the logistics operators domain

Create the tables service_products, capacity_movements, shipments, shipment_lines, exports. Shipping services as skus lives in service_products; keep the sensitive classes (consignee addresses, commercial invoices, customs documents) out of this schema.

2. 2

Workflow step 1

Model report definitions scoped to the agency

3. 3

Workflow step 2

Generate report artifacts from queries and store them with metadata

4. 4

Workflow step 3

Authorize downloads (401 without identity)

5. 5

Workflow step 4

Deploy and verify an authorized export and the rejected anonymous request

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/generated-downloads) and your own acceptance checks for the logistics operators workflow.

ample logs <deployment_id> --kind build

Tested examples

• Next.js pattern fixture (tests/deploy-canaries/next-js-patterns): Verified generated downloads basis for this blueprint.

How to know it worked

• app responds on its public URL (/ on the live URL, expect ample canary next js patterns)
• generated-downloads self-test from the example (/p/generated-downloads on the live URL, expect see the pattern fixture checks)

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.

Verification evidence

• canary_run on 2026-09-21T02:34:39Z at revision 1d28ae0 (CLI 0.1.21): Next.js pattern fixture deployed on Ample (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template); the generated downloads checks passed: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). The blueprint's Logistics operators schema and workflow below build on that verified basis and were not separately executed. (expires 2027-03-20T02:34:39Z)

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.

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 Logistics operators (GET /v1/catalog/nodes/industry%3Alogistics-operators on the api origin; authentication not required, approval not required)
• Browse Reporting dashboard (GET /v1/catalog/nodes/workload%3Areporting-dashboard on the api origin; authentication not required, approval not required)
• Browse Next.js (GET /v1/catalog/nodes/stack%3Aframework-next-js 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)