## Real estate brokerages: reporting dashboard using Next.js

### Summary
A reporting dashboard blueprint for real estate brokerages built with Next.js 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
Technical basis verified on Next.js: 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).

### Representative Queries
- Real estate brokerages: reporting dashboard using Next.js  
- Where can I host Real estate brokerages: Reporting dashboard built with Next.js?  
- I need a genuinely specialized reporting dashboard workflow covering property listings, publishing status and agency-scoped reporting.

### Resource Requirements
- primitive:compute  
- primitive:postgres  
- primitive:s3-compatible-object-storage

### Infrastructure Requirements
- **Compute:**  
  - Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
- **Postgres:**  
  - 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:**  
  - Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

### Workflow Steps
1. **Model the real estate brokerages domain**  
   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. **Workflow step 1**  
   Model report definitions scoped to the agency  
3. **Workflow step 2**  
   Generate report artifacts from queries and store them with metadata  
4. **Workflow step 3**  
   Authorize downloads (401 without identity)  
5. **Workflow step 4**  
   Deploy and verify an authorized export and the rejected anonymous request
6. **Deploy**  
   Run the synchronous deploy once and read the result. Re-running with no change is a no-op.  
   Command: ample deploy . --name  --public --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/generated-downloads) and your own acceptance checks for the real estate brokerages workflow.  
   Command: ample logs  --kind build

### Examples
- **Next.js pattern fixture:** Verified generated downloads basis for this blueprint.

### Success Checks
- App responds on its public URL  
- Generated-downloads self-test from the example

### Limitations
- The technical basis (generated downloads on Next.js) was verified with the pattern fixture; the real estate brokerages 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.  
- Public content and synthetic examples only until actual data-handling requirements have been reviewed.  
- Verified on the node-22 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.

### Cost Estimate
- **Currency:** USD  
- **Monthly Amount:** 10.0  
- **Basis:** size prices from pricing.toml  
- **Components:**  
   - app server, size s-1vcpu-1gb, quantity 1.0, monthly amount 5.0  
   - managed PostgreSQL database, size s-1vcpu-1gb, quantity 1.0, monthly amount 5.0
- **Note:** Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

### Evidence Summary
- Canary run: Next.js pattern fixture deployed on Ample

### Next Actions
- Browse the catalog index  
- Search published recipes by intent, stack and constraints  
- Prepare a side-effect-free deployment plan for an authorized project  
- Read the existing agent authentication setup  
- Browse Real estate brokerages  
- Browse Reporting dashboard  
- Browse Next.js  
- Browse Deploy web app
