How to build a vendor portal for real estate brokerages with Django on Ample | Ample

The short version

A vendor portal 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;
• document_access (document_id, principal_reference, role, granted_at): who may read which document.

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: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok).

What it needs

• Compute: verified (Apps run in isolated x86_64 Firecracker microVMs; 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.)

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. Model the real estate brokerages domain
   Create the tables listings, agencies, listing_media, reports, document_access. 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. Workflow step 1
   Model vendors scoped to the agency with roles

3. Workflow step 2
   Authorize document access by vendor and role (401, 403 negative tests)

4. Workflow step 3
   Store vendor documents in the private bucket

5. Workflow step 4
   Deploy and verify the negative tests and an authorized download

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

7. Verify
   Run the pattern self-test(s) from the example (/p/private-document-library) 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 private document library basis for this blueprint.

How to know it worked

• app responds on its public URL (/ on the live URL, expect ample canary django patterns)
• private-document-library self-test from the example (/p/private-document-library 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 private document library checks passed: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok). 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.

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 Real estate brokerages (GET /v1/catalog/nodes/industry%3Areal-estate-brokerages on the api origin; authentication not required, approval not required)
• Browse Vendor portal (GET /v1/catalog/nodes/workload%3Avendor-portal 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.

Identifiers and status

Recipe page:blueprints:real-estate-brokerages:vendor-portal:django. Revision r1.

release published support verified execution blocked (schema_changed: live tool schema differs from the recorded binding)

Formats: HTML | Markdown | JSON contract