Cosmetic dentistry: company website using Django

Summary

A company website blueprint for cosmetic dentistry built with Django 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.

Infrastructure requirements

• 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

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

Exact tested configuration

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

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

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

Success checks

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

Limitations

• The technical basis (public web service on Django) was verified with the pattern fixture; the cosmetic 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. Case photographs are patient data; publish only with documented consent and de-identification. No health-data 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.