# Real estate brokerages: vendor portal using Django

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

**Verified** November 6, 2026

## What it runs on

- [Computeverified](/content/discover/primitive/compute/index.html)  
  Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

- [Postgresverified](/content/discover/primitive/postgres/index.html)  
  Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

- [S3-compatible object storageverified](/content/discover/primitive/s3-compatible-object-storage/index.html)  
  Buckets speak the S3 API with SigV4 credentials Ample Computer issues; `ample bucket upload-url` returns a presigned upload URL. PutObject and GetObject are checked by canary.

## You need

- 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

## Exact tested configuration

installpython3 -m pip install --target .ample/python -r requirements.txt

runtimepython

sizes-1vcpu-1gb

startPYTHONPATH=.ample/python:${PYTHONPATH:-} python3 run.py

templatepython-3.12

## Steps

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

## How it was checked

✓app responds on its public URL· http get/ → “ample canary django patterns”  
✓private-document-library self-test from the example· http get/p/private-document-library → “see the pattern fixture checks”

## Evidence

1. November 6, 2026 · canary run  
   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.

## Tested examples

- **Django pattern fixture.** Verified private document library basis for this blueprint.

## What it doesn’t cover

- The technical basis (private document library on Django) was verified with the pattern fixture; the real estate brokerages schema and workflow are an original design for this blueprint, built on that basis.
- Only listings with publishing_status = published appear publicly; offers and identities are out of scope.
- Verified on the python-3.12 template at s-1vcpu-1gb.
- Managed PostgreSQL 16 with pgvector.
- Buckets speak the standard S3 API (PutObject and GetObject with path-style addressing are checked by the fixture); `ample bucket upload-url` returns presigned upload URLs.
