page:blueprints:real estate brokerages:public directory:next js
Real Estate Brokerages: Public Directory Using Next.js
Summary
A public directory 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;
- state_transitions (record_type, from_state, to_state): the allowed state machine.
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 Next.js: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true).
Representative Queries
- Real estate brokerages: public directory using Next.js
- Where can I host Real estate brokerages: Public directory built with Next.js?
- I need a genuinely specialized public directory workflow covering property listings, publishing status and agency-scoped reporting.
Workflow Steps
- Model the real estate brokerages domain: Create the tables listings, agencies, listing_media, reports, state_transitions. Keep sensitive classes (vendor and buyer identity, offers and negotiations, unpublished listings) out of this schema.
- Workflow step 1: Model listings with a publishing_status state machine scoped to the agency.
- Workflow step 2: Serve only published listings, with media from the CDN bucket.
- Workflow step 3: Enforce the agency scope on every query.
- Workflow step 4: Deploy and verify a published listing and that unpublished listings are absent.
- Deploy: Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
ample deploy . --name --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=... --env CDN_PUBLIC_URL=... - Verify: Run the pattern self-test(s) from the example (/p/relational-records) and your own acceptance checks for the real estate brokerages workflow.
ample logs --kind build
Cost Estimate
- Currency: USD
- Monthly Amount: 10.0
- 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
- App server: size
- Components:
Limitations
- The technical basis (relational records 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.
- Only listings with
publishing_status = publishedappear publicly; offers and identities are out of scope.
Example
- Next.js pattern fixture: Verified relational records basis for this blueprint. (Source: tests/deploy-canaries/next-js-patterns)
Success Checks
- App responds on its public URL
- Path:
/ - Expect: ample canary next js patterns
- Path:
- Relational-records self-test from the example
- Path:
/p/relational-records - Expect: see the pattern fixture checks.
- Path:
Next Actions
- Browse the catalog index: GET /v1/catalog
- Search published recipes by intent, stack and constraints: POST /v1/catalog/search
- Prepare a side-effect-free deployment plan for an authorized project: POST /v1/catalog/plan
- Read the existing agent authentication setup: GET /mcp/setup
- Browse Real estate brokerages: GET /v1/catalog/nodes/industry%3Areal-estate-brokerages
- Browse Public directory: GET /v1/catalog/nodes/workload%3Apublic-directory
- Browse Next.js: GET /v1/catalog/nodes/stack%3Aframework-next-js
- Browse Deploy web app: GET /v1/catalog/nodes/intent%3Adeploy-web-app
Evidence Summary
- Kind: canary_run
- Summary: Next.js pattern fixture deployed on Ample. The relational records checks passed: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true).
- Observed At: 2026-09-21T02:34:39Z
- Implementation Revision: 1d28ae0-dirty (CLI 0.1.21)
- Expires At: 2027-03-20T02:34:39Z
- Last Verified At: 2026-09-21T02:34:39Z