Estate demo interface showing a villa listing with property details
Public demo interface · Estate Book

Context

Real estate offices need to keep properties, customer requirements, and follow-ups together. A shared deployment also needs firm boundaries between independent companies.

Engineering decisions

Tenant scope belongs on the server
The API derives company scope from the authenticated user and applies that scope to company-owned records. The browser supplies business inputs while the server decides which company can access them.
Subscription and data access are separate decisions
Paid-through status controls writes. Expired companies retain read access under applicable permissions.
Offline actions need visible limits
The app uses a service worker and a client queue to support selected offline workflows. Server permissions and subscription rules still apply when queued operations are submitted.

What shipped

The existing product combines listing and matching workflows with company-scoped storage and access checks. The public link opens the demo, where the workflow can be reviewed independently of customer accounts.