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.)
• Postgres: verified (Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.)
• S3-compatible object storage: verified (Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.)

PREREQUISITES

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)
• A PostgreSQL driver reading DATABASE_URL (auto-provisioned when omitted)
• Bucket credentials from ample bucket create passed as encrypted S3_* environment variables
• A review of which home services data classes may be handled at all; this blueprint models public information only

TESTED CONFIGURATION

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

STEP BY STEP

How to do it

1. Model the home services domain
   Create the tables services, parts_stock, jobs, job_lines, events. Service catalog as skus lives in services; keep the sensitive classes (customer addresses and access notes, payment details) out of this schema.

2. Workflow step 1
   Model SKUs and stock movements; derive stock from movements

3. Workflow step 2
   Apply movements transactionally with an optimistic version check on the SKU

4. Workflow step 3
   Record an event per movement for history

5. Workflow step 4
   Deploy and verify history and rejected stale updates

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

6.  **Deploy**  
    Run the synchronous deploy once and read the result. Re-running with no change is a no-op.

7.  **Verify**  
    Run the pattern self-test(s) from the example (/p/transactional-workflows) and your own acceptance checks for the home services workflow.

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

EXAMPLES

Tested examples

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

SUCCESS CHECKS

How to know it worked

• app responds on its public URL (/ on the live URL, expect ample canary django patterns)
• transactional-workflows self-test from the example (/p/transactional-workflows on the live URL, expect see the pattern fixture checks)

LIMITATIONS

Know the limits

• The technical basis (transactional workflows on Django) was verified with the pattern fixture; the home services 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. Customer addresses and access instructions are personal data; keep them out until handling is reviewed.
• 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.
• Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified.
• PutObject and GetObject with path-style addressing are verified; other S3 operations and CDN cache rules are not.

COST

Cost estimate

Estimated 10.00 USD per month (size prices from pricing.toml at build revision a1b8c38919e59cd035ebabaced73cf84ece24371).

• app server x1 s-1vcpu-1gb: 5.00 USD
• managed PostgreSQL database 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.

EVIDENCE

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 transactional workflows checks passed: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). The blueprint's Home services schema and workflow below build on that verified basis and were not separately executed. (expires 2027-03-19T03:31:44Z)

EXECUTION

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, databases:read, buckets:read.

NEXT ACTIONS

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 Home services (GET /v1/catalog/nodes/industry%3Ahome-services on the api origin; authentication not required, approval not required)
• Browse Inventory manager (GET /v1/catalog/nodes/workload%3Ainventory-manager 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.