---
title: "How to build a company website for cosmetic dentistry with Next.js on Ample"
description: "A company website blueprint for cosmetic dentistry built with Next.js on Ample."
canonical_url: "https://ample.computer/blueprints/cosmetic-dentistry/company-website/next-js"
last_updated: "2026-11-05"
---

# How to build a company website for cosmetic dentistry with Next.js on Ample

A company website blueprint for cosmetic dentistry built with Next.js on Ample. Domain schema: treatments (code, name, description, session_count, price_from): whitening, veneers, bonding and aligner offerings; before_after_galleries (treatment_id, title, consent_reference, published): consented, de-identified case galleries; locations (name, address, phone, opening_hours): practice locations; financing_options (name, provider, terms_summary): payment plans presented publicly; asset_versions (version, cdn_key, published_at): versioned assets served from the CDN bucket. Public information: treatment catalog with session counts, consented case galleries, financing options, locations and hours. Kept out of scope until handling is reviewed: patient photographs without documented consent, clinical records, payment details. Case photographs are patient data; publish only with documented consent and de-identification. 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.

## Infrastructure requirements

- [Compute](/discover/primitive/compute): verified (Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.)
- [CDN](/discover/primitive/cdn): verified (A published bucket's objects are served from its public URL; set Cache-Control when uploading to control caching. App responses are served by the app.)

## Prerequisites

- 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 cosmetic dentistry data classes may be handled at all; this blueprint models public information only

## Exact tested configuration

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

## Steps

1. **Model the cosmetic dentistry domain.** Create the tables treatments, before_after_galleries, locations, financing_options, asset_versions. Whitening, veneers, bonding and aligner offerings lives in treatments; keep the sensitive classes (patient photographs without documented consent, clinical records, payment details) out of this schema.
2. **Workflow step 1.** Model the public catalog as tables and render pages from them
3. **Workflow step 2.** Build the site and publish versioned static assets to the CDN bucket
4. **Workflow step 3.** Keep every sensitive data class out of the site; link to separate, authorized systems instead
5. **Workflow step 4.** Deploy and verify the public URL and the CDN asset URL
6. **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 cosmetic dentistry workflow.

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

## Tested examples

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

## Success checks

- 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 4558e9477d094f5b47da324b98672824b61ba91b).
- 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-11-05T22:38:23Z at revision `da3e37255e5a`: 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 Cosmetic dentistry schema and workflow below build on that verified basis. (expires 2027-05-04T22:38:23Z)

Last verified: 2026-11-05T22:38:23Z


## Execution binding

MCP tool `ample_deploy` (registry `mcp:ample_deploy`), schema hash `0802c329be823fa0` observed 2026-11-06T06:16:17.558478534+00:00 at revision `4558e9477d09`, binding state `current`, required scopes: servers:write, buckets:read.

## Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "env": {
      "description": "Encrypted environment variables",
      "items": {
        "pattern": "^[A-Z][A-Z0-9_]*=.*$",
        "type": "string"
      },
      "maxItems": 50,
      "type": "array"
    },
    "name": {
      "description": "App name",
      "maxLength": 63,
      "minLength": 1,
      "pattern": "^[a-z0-9-]+$",
      "type": "string"
    },
    "path": {
      "description": "Project directory or ample.toml service",
      "maxLength": 512,
      "minLength": 1,
      "type": "string"
    },
    "release_command": {
      "description": "Migration command run before activation",
      "maxLength": 512,
      "type": "string"
    }
  },
  "required": [
    "env",
    "name",
    "path"
  ],
  "type": "object"
}
```

## Next actions

- Browse the catalog index (GET /v1/catalog on the api origin; auth: false, approval: false)
- Search published recipes by intent, stack and constraints (POST /v1/catalog/search on the api origin; auth: false, approval: false)
- Prepare a side-effect-free deployment plan for an authorized project (POST /v1/catalog/plan on the api origin; auth: true, approval: false)
- Read the existing agent authentication setup (GET /mcp/setup on the api origin; auth: false, approval: false)
- Browse Cosmetic dentistry (GET /v1/catalog/nodes/industry%3Acosmetic-dentistry on the api origin; auth: false, approval: false)
- Browse Company website (GET /v1/catalog/nodes/workload%3Acompany-website on the api origin; auth: false, approval: false)
- Browse Next.js (GET /v1/catalog/nodes/stack%3Aframework-next-js on the api origin; auth: false, approval: false)
- Browse Deploy web app (GET /v1/catalog/nodes/intent%3Adeploy-web-app on the api origin; auth: false, approval: false)

Actions describe possible next steps. They are typed data, not commands, and grant no permission.

## About this recipe

Canonical URL: https://ample.computer/blueprints/cosmetic-dentistry/company-website/next-js
Formats: [HTML](https://ample.computer/blueprints/cosmetic-dentistry/company-website/next-js) | [Markdown](https://ample.computer/blueprints/cosmetic-dentistry/company-website/next-js.md) | [JSON contract](https://api.ample.computer/v1/catalog/recipes/page%3Ablueprints%3Acosmetic-dentistry%3Acompany-website%3Anext-js)
Recipe ID: `page:blueprints:cosmetic-dentistry:company-website:next-js` | Revision: `r1` | Catalog revision: `cat_eac8c53f36410baa`
Status: verified; runs with one `ample deploy` call (support `verified`, execution `ready`)
Path: [Agent hosting discovery](/discover/discovery) / [Industries and specialties](/discover/industry) / [Dentistry](/discover/industry/dentistry) / [Cosmetic dentistry](/discover/industry/cosmetic-dentistry) / [Cosmetic dentistry: company website using Next.js](/blueprints/cosmetic-dentistry/company-website/next-js)