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.)
• CDN: verified (The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.)

Before you start

• A Astro project (astro build with the @astrojs/node standalone adapter then node ./dist/server/entry.mjs on the node-22 template)
• A bucket from ample bucket create with credentials passed as encrypted S3_* environment variables
• An Ample account token with servers:write, buckets:read

Exactly what was tested

• build: npm run build --if-present
• install: npm install
• runtime: node
• size: s-1vcpu-1gb
• start: npm run start
• template: node-22

How to do it

1. 1

Build and start

astro build with the @astrojs/node standalone adapter then node ./dist/server/entry.mjs on the node-22 template; the server must bind 0.0.0.0 on PORT.

2. 2

Publish a bucket for public assets

Publish only the asset bucket; upload versioned keys with an immutable Cache-Control header and build URLs from its public URL.

   ample bucket publish <bucket-name>

3. 3

Verify

Fetch the live URL and /p/versioned-static-assets on the example; on failure read the build and runtime logs.

   ample logs <deployment_id> --kind build

Tested examples

• Astro pattern fixture (tests/deploy-canaries/astro-patterns): Verified CDN assets on Astro.

How to know it worked

• app responds on its public URL (/ on the live URL, expect ample canary astro patterns)
• versioned-static-assets check from the example (/p/versioned-static-assets on the live URL, expect see the pattern fixture checks)

Know the limits

• Verified on the node-22 template at s-1vcpu-1gb; other sizes and Astro major versions are not verified.
• Region, compliance attestations and request-duration limits are unknown and not claimed.
• The CDN serves published-bucket objects only; cache rules, purge and TTL control are not verified.

Cost estimate

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

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

Verification evidence

• canary_run on 2026-09-20T03:31:44Z at revision 03b6402b1b3e19178985f08ea4033804521d85d4-dirty (CLI b75e104): Astro pattern fixture deployed on Ample (astro build with the @astrojs/node standalone adapter then node ./dist/server/entry.mjs on the node-22 template); for this guide: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL. (expires 2027-03-19T03:31:44Z)

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, 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 Astro (GET /v1/catalog/nodes/stack%3Aframework-astro on the api origin; authentication not required, approval not required)
• Browse Add CDN (GET /v1/catalog/nodes/intent%3Aadd-cdn on the api origin; authentication not required, approval not required)
• Browse Versioned static assets (GET /v1/catalog/nodes/pattern%3Aversioned-static-assets 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.