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

PREREQUISITES

Before you start

• A Gin project (CGO_ENABLED=0 go build -o app ./... then ./app on the ubuntu-24.04 template (go.sum committed for a reproducible build))
• An Ample account token with servers:write

TESTED CONFIGURATION

Exactly what was tested

• build: CGO_ENABLED=0 go build -o app ./...
• runtime: go
• size: s-1vcpu-1gb
• start: ./app
• template: ubuntu-24.04

STEP BY STEP

How to do it

1. 1

Build and start

CGO_ENABLED=0 go build -o app ./... then ./app on the ubuntu-24.04 template (go.sum committed for a reproducible build); the server must bind 0.0.0.0 on PORT.

2. 2

Deploy

Run the synchronous deploy once and read the result.

ample deploy . --name <app-name> --public

3. 3

Verify

Fetch the live URL on the example; on failure read the build and runtime logs.

ample logs <deployment_id> --kind build

EXAMPLES

Tested examples

• Gin pattern fixture (tests/deploy-canaries/gin-patterns): Verified build and start on Gin.

SUCCESS CHECKS

How to know it worked

• app responds on its public URL (/ on the live URL, expect ample canary gin patterns)

LIMITATIONS

Know the limits

• Verified on the ubuntu-24.04 template at s-1vcpu-1gb; other sizes and Gin major versions are not verified.
• Region, compliance attestations and request-duration limits are unknown and not claimed.

COST

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.

EVIDENCE

Verification evidence

• canary_run on 2026-09-21T01:15:54Z at revision 50dbac567d2c5cc8e55e6c748a646be0025d9cfb-dirty (CLI 0.1.21): Gin pattern fixture deployed on Ample (CGO_ENABLED=0 go build -o app ./... then ./app on the ubuntu-24.04 template (go.sum committed for a reproducible build)); for this guide: the app built and started with the documented commands and answered on its public HTTPS URL. (expires 2027-03-20T01:15:54Z)

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.

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 Gin (GET /v1/catalog/nodes/stack%3Aframework-gin on the api origin; authentication not required, approval not required)
• Browse Configure deployment (GET /v1/catalog/nodes/intent%3Aconfigure-deployment on the api origin; authentication not required, approval not required)
• Browse Public web service (GET /v1/catalog/nodes/pattern%3Apublic-web-service 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.