---
title: "Orthodontics: company website using Next.js"
description: "A company website blueprint for orthodontics built with Next.js on Ample."
canonical_url: "https://ample.computer/blueprints/orthodontics/company-website/next-js"
last_updated: "2026-09-21"
---

# Orthodontics: company website using Next.js

Canonical URL: https://ample.computer/blueprints/orthodontics/company-website/next-js
Formats: [HTML](https://ample.computer/blueprints/orthodontics/company-website/next-js) | [Markdown](https://ample.computer/blueprints/orthodontics/company-website/next-js.md) | [JSON contract](https://api.ample.computer/v1/catalog/recipes/page%3Ablueprints%3Aorthodontics%3Acompany-website%3Anext-js)
Recipe ID: `page:blueprints:orthodontics:company-website:next-js` | Revision: `r1` | Catalog revision: `cat_f13ab9a494120b5e`

Status: release `published`, support `verified`, execution `ready`

## Summary

A company website blueprint for orthodontics built with Next.js on Ample. Domain schema: appliance_types (code, name, description, typical_duration_months): braces and aligner options; treatment_stages (appliance_type_id, stage_no, name, what_to_expect): public description of treatment phases; locations (name, address, phone, opening_hours): practice locations; age_groups (name, guidance): children, teens and adults guidance; asset_versions (version, cdn_key, published_at): versioned assets served from the CDN bucket. Public information: appliance options and durations, stage-by-stage expectations, age-group guidance, locations. Kept out of scope until handling is reviewed: patient scans and treatment plans, progress photos, guardian and minor identity. Orthodontic plans and progress imagery are health data; keep them out of scope until handling is reviewed. No compliance is claimed. 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.

Path: [Agent hosting discovery](/discover/discovery) / [Industries and specialties](/discover/industry) / [Dentistry](/discover/industry/dentistry) / [Orthodontics](/discover/industry/orthodontics) / [Orthodontics: company website using Next.js](/blueprints/orthodontics/company-website/next-js)

## Infrastructure requirements

- [Compute](/discover/primitive/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](/discover/primitive/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

- 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 orthodontics 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 orthodontics domain.** Create the tables appliance_types, treatment_stages, locations, age_groups, asset_versions. Braces and aligner options lives in appliance_types; keep the sensitive classes (patient scans and treatment plans, progress photos, guardian and minor identity) 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 orthodontics 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 515b7316fc6e5a81679407ae0c811146ceb2c5c7).
- 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.

## 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. The blueprint's Orthodontics schema and workflow below build on that verified basis and were not separately executed. (expires 2027-03-20T02:34:39Z)

Last verified: 2026-09-21T02:34:39Z


## 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 `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 Orthodontics (GET /v1/catalog/nodes/industry%3Aorthodontics 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.