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

PREREQUISITES

Before you start

• A Next.js project (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template)
• Bucket credentials from ample bucket create passed as encrypted S3_* environment variables and a published bucket for public assets (CDN_*)
• A review of which general dentistry data classes may be handled at all; this blueprint models public information only

TESTED CONFIGURATION

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

STEP BY STEP

How to do it

Model the general dentistry domain

Create the tables services, locations, dentists, insurance_plans, asset_versions. The treatments a practice offers lives in services; keep the sensitive classes (patient identity and contact details, clinical records, x-rays and treatment notes, appointment history tied to a person) out of this schema.

Workflow step 1

Model articles and categories as tables keyed to the public catalog entities.

Workflow step 2

Build the site with versioned assets served from the CDN bucket.

Workflow step 3

Keep articles free of any sensitive data class.

Workflow step 4

Deploy and verify the public URL and the CDN asset URL.

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=... --env CDN_PUBLIC_URL=...
    ```

7.

### Verify

Run the pattern self-test(s) from the example (/p/versioned-static-assets) and your own acceptance checks for the general dentistry workflow.

ample logs <deployment_id> --kind build
```

EXAMPLES

Tested examples

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

SUCCESS CHECKS

How to know it worked

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

LIMITATIONS

Know the limits

• The technical basis (public web service on Next.js) was verified with the pattern fixture; the general dentistry schema and workflow are an original design for this blueprint and were not executed as a separate application.
• No health, financial, privacy or other compliance claim is made. Patient data is health data. Keep it out of these workflows until handling requirements (for example HIPAA in the United States) have been reviewed; nothing here establishes compliance.
• Public content and synthetic examples only until actual data-handling requirements have been reviewed.
• Verified on the node-22 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.
• PutObject and GetObject with path-style addressing are verified; other S3 operations and CDN cache rules are not.

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 and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

EVIDENCE

Verification evidence

• canary_run on 2026-09-21T02:34:39Z at revision 1d28ae0-dirty (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 public web service checks passed: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL alongside the app's own public HTTPS URL. The blueprint's General dentistry schema and workflow below build on that verified basis and were not separately executed. (expires 2027-03-20T02:34:39Z)

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, 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 General dentistry (GET /v1/catalog/nodes/industry%3Ageneral-dentistry on the api origin; authentication not required, approval not required)
• Browse Knowledge base (GET /v1/catalog/nodes/workload%3Aknowledge-base 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)