### Real estate brokerages: reporting dashboard using Laravel

A reporting dashboard blueprint for real estate brokerages built with Laravel on Ample.  
**Domain schema:**  
- **Listings**: property listings with publishing status  
  - Fields: reference, address, price, listing_type, publishing_status, agency_id  
- **Agencies**: agencies or branches  
  - Fields: name, license_number, region  
- **Listing Media**: public media per listing  
  - Fields: listing_id, object_key, cdn_key, sort_order  
- **Reports**: agency-scoped reports  
  - Fields: agency_id, period, object_key, generated_at  
- **Exports**: generated artifacts and who may download them  
  - Fields: id, definition, object_key, row_count, generated_at, authorized_role

**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 Laravel:** 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  
1. Real estate brokerages: reporting dashboard using Laravel  
2. Where can I host Real estate brokerages: Reporting dashboard built with Laravel?  
3. I need a genuinely specialized reporting dashboard workflow covering property listings, publishing status and agency-scoped reporting.

---

### Prerequisites  
- A Laravel project (composer install --no-dev from composer.lock, then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 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

---

### Workflow Steps  
1. **Model the real estate brokerages domain**: Create the tables listings, agencies, listing_media, reports, exports.  
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.  
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.

---

### Cost Estimate  
- **Currency**: USD  
- **Monthly Amount**: $10.00  
- **Basis**: Size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty  
**Components:**  
- App server: size s-1vcpu-1gb - $5.00  
- Managed PostgreSQL database: size s-1vcpu-1gb - $5.00

> Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.
