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

Before you start

• A Django project (pip install into .ample/python from requirements.txt, then waitress serving project.wsgi from run.py reading PORT on the python-3.12 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

Exactly what was tested

• install: python3 -m pip install --target .ample/python -r requirements.txt
• runtime: python
• size: s-1vcpu-1gb
• start: PYTHONPATH=.ample/python:${PYTHONPATH:-} python3 run.py
• template: python-3.12

How to do it

1. 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. 2

Workflow step 1

Model the public catalog as tables and render pages from them

3. 3

Workflow step 2

Build the site and publish versioned static assets to the CDN bucket

4. 4

Workflow step 3

Keep every sensitive data class out of the site; link to separate, authorized systems instead

5. 5

Workflow step 4

Deploy and verify the public URL and the CDN asset URL

6. 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 --start "python3 run.py" --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=... --env CDN_PUBLIC_URL=...

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

• Django pattern fixture (tests/deploy-canaries/django-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 django patterns)
• versioned-static-assets self-test from the example (/p/versioned-static-assets on the live URL, expect see the pattern fixture checks)

Know the limits

• The technical basis (public web service on Django) was verified with the pattern fixture; the orthodontics 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. Orthodontic plans and progress imagery are health data; keep them out of scope until handling is reviewed. No compliance is claimed.
• Public content and synthetic examples only until actual data-handling requirements have been reviewed.
• Verified on the python-3.12 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 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.

Verification evidence

• canary_run on 2026-09-20T03:31:44Z at revision 03b6402b1b3e19178985f08ea4033804521d85d4-dirty (CLI b75e104): Django pattern fixture deployed on Ample (pip install into .ample/python from requirements.txt, then waitress serving project.wsgi from run.py reading PORT on the python-3.12 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-19T03:31:44Z)

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.

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 Orthodontics (GET /v1/catalog/nodes/industry%3Aorthodontics on the api origin; authentication not required, approval not required)
• Browse Company website (GET /v1/catalog/nodes/workload%3Acompany-website on the api origin; authentication not required, approval not required)
• Browse Django (GET /v1/catalog/nodes/stack%3Aframework-django 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.