## The short version

A reporting dashboard blueprint for real estate brokerages built with Django on Ample. Domain schema:

- **listings** (reference, address, price, listing_type, publishing_status, agency_id): property listings with publishing status;
- **agencies** (name, license_number, region): agencies or branches;
- **listing_media** (listing_id, object_key, cdn_key, sort_order): public media per listing;
- **reports** (agency_id, period, object_key, generated_at): agency-scoped reports;
- **exports** (id, definition, object_key, row_count, generated_at, authorized_role): generated artifacts and who may download them.

Public information: published listings with media, agent and agency profiles, buying and selling guides. Kept out of scope until handling is reviewed: vendor and buyer identity, offers and negotiations, unpublished listings. Only listings with publishing_status = published appear publicly; offers and identities are out of scope. Technical basis verified on Django: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3).

## What it needs

- [Compute](/content/discover/primitive/compute/index.html): verified (Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.)
- [Postgres](/content/discover/primitive/postgres/index.html): 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](/content/discover/primitive/s3-compatible-object-storage/index.html): verified (Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.)

## 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 real estate brokerages data classes may be handled at all; this blueprint models public information only

## How to do it

1.  Create the tables listings, agencies, listing_media, reports, exports. Property listings with publishing status lives in listings; keep the sensitive classes (vendor and buyer identity, offers and negotiations, unpublished listings) out of this schema.

2.  Model report definitions scoped to the agency

3.  Generate report artifacts from queries and store them with metadata

4.  Authorize downloads (401 without identity)

5.  Deploy and verify an authorized export and the rejected anonymous request

```  
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.  Run the synchronous deploy once and read the result. Re-running with no change is a no-op.

7.  Run the pattern self-test(s) from the example (/p/generated-downloads) and your own acceptance checks for the real estate brokerages workflow.

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

## Tested examples

- **Django pattern fixture** (`tests/deploy-canaries/django-patterns`): Verified generated downloads basis for this blueprint.

## How to know it worked

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

## Cost estimate

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

- app server x1 `s-1vcpu-1gb`: 5.00 USD
- managed PostgreSQL database 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-09-20T03:31:44Z at revision `03b6402b1b3e19178985f08ea4033804521d85d4 (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 generated downloads checks passed: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). The blueprint's Real estate brokerages 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-22T00:31:22.774679+00:00 at revision `e6446ceea69b`. Binding state at export: schema_changed. Required scopes: servers:write, databases:read, buckets:read.