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

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 at runtime
• An Ample account token with servers:write, databases:read

TESTED CONFIGURATION

Exactly what was tested

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

STEP BY STEP

How to do it

1. 1

Build and start

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 server must bind 0.0.0.0 on PORT.

2. 2

Read DATABASE_URL at runtime

Open connections from the environment inside handlers or a pool; omit DATABASE_URL to auto-provision a managed database or pass --env DATABASE_URL=... for an existing one.

3. 3

Verify

Fetch the live URL and /p/relational-records on the example; on failure read the build and runtime logs.

ample logs <deployment_id> --kind build

EXAMPLES

Tested examples

• Laravel pattern fixture (tests/deploy-canaries/laravel-patterns): Verified database connection on Laravel.

SUCCESS CHECKS

How to know it worked

• app responds on its public URL (/ on the live URL, expect ample canary laravel patterns)
• relational-records check from the example (/p/relational-records on the live URL, expect see the pattern fixture checks)

LIMITATIONS

Know the limits

• Verified on the php-8.5 template at s-1vcpu-1gb; other sizes and Laravel major versions are not verified.
• Region, compliance attestations and request-duration limits are unknown and not claimed.
• Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified.

COST

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 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-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); for this guide: a managed PostgreSQL database auto-provisioned and injected as DATABASE_URL, with real queries succeeding at request time (records=ok). (expires 2027-03-19T20:36:21Z)

EXECUTION

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 at export: current. Required scopes: servers:write, databases: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 Laravel (GET /v1/catalog/nodes/stack%3Aframework-laravel on the api origin; authentication not required, approval not required)
• Browse Connect app to database (GET /v1/catalog/nodes/intent%3Aconnect-app-to-database on the api origin; authentication not required, approval not required)
• Browse Relational records (GET /v1/catalog/nodes/pattern%3Arelational-records 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.