## The short version A campaign site blueprint for general dentistry built with Next.js on Ample. Domain schema: - **services** (code, name, description, duration_minutes, price_from): the treatments a practice offers; - **locations** (name, address, phone, opening_hours, accessibility_notes): each practice location; - **dentists** (name, registration_number, specialties, location_id): the clinicians listed publicly; - **insurance_plans** (name, accepted_at_location_id): plans accepted per location; - **asset_versions** (version, cdn_key, published_at): versioned assets served from the CDN bucket. Public information: service catalog with prices from, locations, hours and parking, clinician profiles and registrations, accepted insurance plans. Kept out of scope until handling is reviewed: patient identity and contact details, clinical records, x-rays and treatment notes, appointment history tied to a person. 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. Technical basis verified on Next.js: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL alongside the app's own public HTTPS URL. --- ## What it needs - [Compute](/content/discover/primitive/compute/index.html): verified (Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.) - [CDN](/content/discover/primitive/cdn/index.html): verified (A published bucket's objects are served at its public_url. It does not front app compute and is not a cache or key-value store.) --- ## 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 --- ## How to do it 1. **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. 2. **Workflow step 1** Model the campaign's offers and locations as tables with start and end dates 3. **Workflow step 2** Build the site and publish versioned static assets to the CDN bucket 4. **Workflow step 3** Collect no personal data on the site itself; hand off to an authorized system 5. **Workflow step 4** Deploy, verify the public URL and the CDN asset URL, and retire the campaign by end date 6. **Deploy** Run the synchronous deploy once and read the result. Re-running with no change is a no-op. ``` ample deploy . --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 --kind build ``` --- ## Tested examples - **Next.js pattern fixture** (`tests/deploy-canaries/next-js-patterns`): Verified public web service 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) - versioned-static-assets self-test from the example (`/p/versioned-static-assets` on the live URL, expect see the pattern fixture checks) --- ## Cost estimate Estimated 5.00 USD per month (size prices from pricing.toml at build revision ca0b484a7a9957c573a88d3a32dc603c3c10135a). - app server x1 `s-1vcpu-1gb`: 5.00 USD Upper-bound monthly price of the tested sizes. 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 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. --- ## 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: schema_changed. 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 General dentistry (`GET /v1/catalog/nodes/industry%3Ageneral-dentistry` on the api origin; authentication not required, approval not required) - Browse Campaign site (`GET /v1/catalog/nodes/workload%3Acampaign-site` 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) 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.