A look at how listings, seller tools, Jamie, and the rest of the site fit together.
Sunset Pulse runs as a Next.js app on Vercel. Pages render on the server where that helps, while interactive pieces run in the browser. Server routes handle data requests and keep provider credentials away from the page.
The listing repository gives pages one consistent way to read property records. PostgreSQL through Supabase is the canonical store; MongoDB still serves older property paths while that migration continues.
Jamie can use the current conversation and, when available, the selected listing or research context. The server gathers that information before sending the request to the configured AI provider. Jamie can suggest a reply or a next step; you review it before sharing.
Jamie’s answers depend on the material available to that workflow. Listing details come from the listing repository; other research tools can use their connected sources or local indexes. If a source is unavailable, the app can say so instead of treating a guess as a fact.
The map gives you a sense of where places sit and what is nearby. Open a listing when you need its full details.
The virtual map brings neighborhood context and available property signals into one view. It is a way to explore, not a replacement for checking the listing itself.
Switch between curated properties and the current MLS feed. Photos and details depend on what the listing provider has supplied.
Jamie’s reply can select one of a few visual modes. The VibeProvider applies that mode’s colors and supported effects to the page. It changes presentation only; listing details and your decisions stay the same.
Page accents and a few decorative effects can respond to the current mode.
In Studio, a chosen filter and its image settings produce a repeatable preview signature.