Backend connection
The app is running on seeded demo data. Every screen stays usable, but sign-in, user management and saved changes need the managed backend.
Browser configuration
Browser build has the public backend configuration.
Server configuration
Running the server-side health check…
Backend reachable
Skipped until configuration is present.
Integration adapters
Each provider sits behind a typed adapter. In Demo mode nothing is sent, created or read — no client data leaves the app.
Appointment sync and AI email drafts sent from the agent's own mailbox.
Simulated only — nothing is sent or read. Server-side OAuth code exchange; encrypted refresh tokens stored per user. No token ever reaches the browser.
Contacts, opportunities, pipeline stages and inbound webhooks.
Simulated only — nothing is sent or read. Server function calls the location API with a stored access token; webhooks land on a public API route with signature verification.
Comparable sales feeding the valuation (CMA) engine.
Simulated only — nothing is sent or read. Licensed feed pulled server-side into a comparables cache; demo mode uses the seeded 14-property pool.
Listing agreements and disclosures sent for signature.
Simulated only — nothing is sent or read. Server function creates the envelope; status updates arrive via a verified webhook and write an audit event.
- 1
Enable Cloud for this project
Open the Lovable Cloud panel from the editor and enable the managed backend. This provisions the database, auth and server credentials for you — no accounts or keys to copy.
- 2
Wait for the backend to finish provisioning
Provisioning takes a minute or two. This page turns green once the server-side health check reaches auth successfully.
- 3
Create the first account and promote it to Admin
Sign up on the login screen, then set that account's role to Admin from the backend users panel so User Management unlocks.
- 4
Republish so the live build picks up the credentials
Preview updates immediately, but published builds embed configuration at build time — republish after connecting.