# Domora > Domora is a multi-tenant operating system for real-estate brokerages, connecting a branded property portal with a private workspace. Source page: https://saascode.ai/products/domora Machine-readable record: https://saascode.ai/products/domora.md One-time purchase · full source code · self-hosted by the buyer. Price: $199 (one-time) ## How to read this document Written for a model auditing this product on a buyer's behalf. Two labels appear throughout and they mean different things: - **measured** — produced by a script reading the product's own source tree or database at the stated date. The method is named beside each number. - **stated** — written by the seller. True or not, it is a claim, and this document does not ask you to treat it as evidence. The live demo is the strongest verification available from outside: it runs the same source a buyer receives. Nothing to sign up for — the public side is open, and the seeded credentials below get you into each role. ## What it is This platform is an operating system for real-estate brokerages. Each brokerage is one organization on the platform and gets two connected surfaces. ## Live demo Two doors into the same running instance, and the same source a buyer receives. There is no account to create; the public side is open, and the seeded credentials below sign you into each role. - **Guided (recommended):** https://saascode.ai/demo/domora — our shell, with a role switcher and the credentials in the menu. Best for a person. - **Direct:** https://domora.saascode.ai — the product on its own, no chrome. Best when you are relaying steps to someone, or fetching a page. 2 roles seeded on the demo (of the 7 the schema defines — the build data below counts them all). Credentials are published deliberately: these are demo accounts on a public demo instance, and a reviewer who cannot get in cannot verify anything. - **Brokerage administrator** (`org_admin`) — `org-admin@demo.com` / `demo123` Runs the brokerage team, inventory, pipeline, billing, and settings. - **Platform owner** (`super_admin`) — `admin@demo.com` / `demo123` Runs every brokerage, plan, integration, and platform control. Or open a role directly: https://saascode.ai/demo/domora?role={role} ## Measured build *measured — each number names the method that produced it.* - **roles: 7** — distinct roles accepted by the role CHECK constraint: admin, agent, assistant, member, org_admin, owner_client, super_admin - **tables: 83** — distinct CREATE TABLE statements across every applied migration - **migrations: 120** — .sql files in supabase/migrations - **page modules: 128** — files named page.tsx under src/app, excluding node_modules and .next - **source lines: 222,798** — lines of code (comments and blank lines excluded) across 1520 TypeScript files (197,215) and 143 SQL files (25,583); node_modules and .next excluded - **api route files: 337** — files named route.ts under src/app/api - **http operations: 459** — exported HTTP method handlers across those files, de-duplicated per file, OPTIONS excluded as CORS preflight - **schema graph: 83 tables, 162 relationships** — parsed from the applied migrations A large number here is scope, not quality. It says the product models a real domain rather than a CRUD skeleton; it says nothing about code quality, duplication, test coverage or maintainability, and should not be read as if it did. Release: v1.0.0 · built 2026-08-21 ## Complete capability inventory 12 capabilities. Each summary is *stated* — selected from the product's own buyer documentation, or written by the seller where marked. ### Property inventory, media and publishing to portals - **Property inventory and media (Property inventory and media with core listing fields and country-profile operation requirements)** *(seller-authored)* — Property inventory and media with core listing fields and country-profile operation requirements - **Public tenant portal and search (Public property search with text results and map-eligible listings)** *(seller-authored)* — Public property search with text results and map-eligible listings - **Outbound portal publication** — Publication is a lifecycle, not a button. For each connected portal you set a desired state for a listing; the app records the observed state reported back by the portal, together with validation errors, rejection reasons, retry attempts and removals. The two states being different is normal and visible, which is the point — you can see that a listing you asked to publish was rejected, and why. ### Contacts, demand, matching, opportunities and visits - **Contacts and activity CRM (Contact CRM with activity history, optional agent assignment and explicit inquiry linking)** *(seller-authored)* — Contact CRM with activity history, optional agent assignment and explicit inquiry linking - **Demands and saved searches** — A demand record is what a buyer or tenant is looking for: operation, area, budget range, rooms and other criteria. Visitors create the same shape of record themselves when they save a search on the portal, so brokerage-entered demand and visitor-entered demand feed one model. - **Deterministic matching** — Matching is deterministic. It compares demand criteria against the organization's own published inventory and records every result, so a match can be explained rather than guessed at. Nothing is inferred by a model and nothing crosses organizations. Each delivery attempt to a contact or visitor is recorded, so you can see what was sent, when, and whether it arrived. - **Opportunity pipeline (Opportunity pipeline with explicit property-close handoff to valuation comparables)** *(seller-authored)* — Opportunity pipeline with explicit property-close handoff to valuation comparables - **Visit agenda and atomic booking (Atomic visit booking with idempotent replay, rescheduling, cancellation and history)** *(seller-authored)* — Atomic visit booking with idempotent replay, rescheduling, cancellation and history - **Owner participation** *(seller-authored)* — Give property owners a restricted view of the properties they participate in and an approved projection of activity. Internal notes, unrelated contacts, and other owners' records stay outside that surface, so the brokerage can share progress without opening its private workspace. ### Commissions, valuations and portfolio analytics - **Commissions (Fixed or percentage commission rules with one beneficiary allocation per closed operation)** *(seller-authored)* — Fixed or percentage commission rules with one beneficiary allocation per closed operation - **Comparable valuation** — There is no model estimating the price. The method is deterministic and the inputs are listed, so a figure can be defended to a seller. - **Brokerage analytics/reports** — Analytics are organization-scoped and cover days on market, inquiries per property, visits, conversion through the opportunity stages, agent performance and publication health. Report templates ship for inventory health, opportunity conversion, visit outcomes, publication health and commission forecasting; reports can be scheduled and delivered by email. ## What each system gives the operator *stated.* - **Property inventory, media and publishing to portals** — Keep each brokerage's inventory searchable, presentable, and ready for controlled distribution. - **Contacts, demand, matching, opportunities and visits** — Move buyer demand from first contact through matching, visits, and a closed opportunity. - **Commissions, valuations and portfolio analytics** — Turn completed work into defensible valuations, commission allocations, and operating reports. ## The problems it was built to solve *stated — the seller's argument, given in full so you can judge it.* ### Every brokerage presents one dependable inventory wherever prospects discover it. Real-estate teams lose momentum when the listing a seller approved, the version agents work from, and the version prospects discover become three different stories. Staff spend time reconciling photos, availability, and publication status instead of moving a property forward. Leads arrive against stale context, sellers ask why a listing is missing, and nobody can say where distribution broke. A brokerage needs one commercial source of truth that remains recognizable wherever the property is presented. Without it, every extra channel increases coordination cost and turns ordinary listing changes into preventable follow-up work. ### Buyer demand reaches the right property before the opportunity goes cold. When demand lives in notes, inboxes, and individual memory, the best opportunity depends on who happens to remember the right buyer first. Follow-up slows, viable matches are missed, and the same questions are asked again before every viewing. As the team grows, the problem compounds: prospects receive irrelevant options while suitable inventory waits unnoticed. The commercial cost appears as ageing opportunities, wasted agent time, and visits that never become serious conversations. A brokerage needs demand to remain visible and actionable from the first inquiry until the deal reaches a clear outcome. ### Owners stay informed without seeing the brokerage's private working record. Property owners want evidence that their listing is moving, but a brokerage cannot answer that need by opening its internal workspace. When updates depend on manual summaries, clients wait for callbacks, agents repeat the same explanation, and internal notes are more likely to be shared too broadly. The absence of a trusted view turns ordinary status questions into a service burden and weakens confidence at the moment a seller is evaluating the relationship. The brokerage needs a clear boundary: enough progress to keep owners informed, without exposing contacts, negotiations, or work that belongs inside the team. ### Closed work becomes a clearer view of value, payout, and performance. Closing a transaction does not end the operational work. The team still needs to explain what the result says about future pricing, who earned each share, and whether performance is improving across the portfolio. When those answers live in separate spreadsheets, every valuation becomes harder to defend, every payout invites reconciliation, and management reviews arrive late. Small inconsistencies compound into distrust between agents, owners, and the brokerage. A durable business needs completed work to become a reliable record that supports the next pricing conversation, the next commission statement, and the next operating decision. ## What it takes to run it *stated — external services the buyer supplies and pays for directly.* - **Application runtime** (required) — A Node host for Next 16.2.10 and a Supabase project; `package.json` does not pin a Node release. - **Scheduled work** (required) — Three jobs are declared in `vercel.json`; reproduce those schedules when hosting outside Vercel. - **Outbound email** (optional) — Choose one of the shipped Brevo, Mailgun, Resend, SendGrid or SMTP adapters when email delivery is enabled. - **Optional service hooks** (optional) — The environment template exposes optional Upstash and Sentry integrations. ## FAQ **What exactly do I receive after purchase?** The complete source repository behind the live demo — 222,798 lines across the application and its database, 83 tables defined by 120 migrations that the shipped scripts apply for you, plus the seed data, the demo accounts and the setup documentation. Not a subset and not a scaffold: the same code that runs the demo you just used. **Is the live demo the same product whose source I receive?** Yes. The Domora demo runs the delivered release (v1.0.0), and the build figures on this page are measured from that same source — not from a showcase build kept separately. **Can I test every account role before buying?** Yes — all 2 of them: Brokerage administrator, Platform owner. Each one is seeded in the live demo and reachable from the role board above, so you can inspect the product from the customer's side, the agent's side and the administrator's side before you decide. **Is this a complete product or a starter template?** Complete. 128 page modules and 459 HTTP operations, with authentication, roles, billing, an administration panel, background jobs and seeded demo data all wired and running. A template gives you the shape of an application; this is one you can deploy and start operating. **Can I rebrand and modify it?** Yes, without asking. The name, identity, copy, styling and code are yours to change. Rebranding and operating it as your own service is exactly what the licence is for. **What does the licence allow?** A perpetual, worldwide, non-exclusive, non-transferable licence to the product you bought and to every update released for it. The Standard licence covers one business — yours. If you deploy for clients, the Client licence covers up to five. You can modify it, rebrand it, deploy it and charge your own customers. **Can I resell the source code?** No. Reselling, redistributing, sublicensing or giving away the source itself is not permitted under either licence. You build and deliver products with it — the code stays with you. **What services and ongoing costs are required?** You bring your own accounts, so we never mark anything up and there is no ongoing cost to us beyond the purchase. Required: Application runtime, Scheduled work. Optional: Outbound email, Optional service hooks. The table above says exactly what stops working without each one; most have usable free tiers at low volume. **How difficult is deployment?** Two ways, and most buyers use the first. The installer in your saascode dashboard walks it: you create free accounts at Vercel and Supabase, connect them, and it provisions the database, applies 120 migrations, seeds the data, deploys and verifies the result — you watch the steps go green. Or take the source and do it yourself with the shipped scripts and docs, which is the same sequence run by hand. **What updates and support are included?** Updates to that product for as long as we maintain it — no renewal fee and no expiry date on your access. Support covers download problems, defects in the code as shipped, questions about what the product does and how it is structured, and licence questions. It does not cover debugging your own modifications, building features for you, or setting up your hosting and third-party accounts. **Why does a complete codebase cost $199?** Because it was built once and is distributed many times. SaaSCode builds each product and ships the same finished release through the catalog, so the price reflects repeatable distribution — not a reduced codebase, an unfinished template, or what the same work would cost commissioned. **Do I need to be a developer?** No, for the normal path. You create free accounts at Vercel and Supabase, connect them to the installer in your saascode dashboard, and it does the deployment for you — provision, migrate, seed, deploy, verify. What it asks of you is creating two accounts and copying a token, not writing code. If you would rather deploy it yourself, or host it somewhere else, the full source and the scripts are yours to do that with. Running the product day to day needs no technical skill at all: that happens through its own interface, which is what the demo shows. ## Licence The buyer receives the complete source and may deploy, modify and operate it as their own SaaS, charging their own customers. The source itself is not resold or redistributed: you build and deliver **with** it, you do not sell **it**. ## What this document cannot tell you Stated plainly because a review that misses it is not a review: - code quality, duplication, or architectural consistency - test coverage - query performance under load - security posture beyond what the stack implies - how maintainable it will be in a year Scope is measurable from outside; implementation quality is not. Anyone evaluating this should say so rather than infer quality from size. ## Written about it - [Domora: a two-surface operating system for real-estate brokerages](https://saascode.ai/inside/domora-two-surface-brokerage-operating-system.md) - [Domora vs BoldTrail: source ownership or a managed brokerage ecosystem?](https://saascode.ai/inside/domora-vs-boldtrail.md) - [Six real-estate brokerage platforms for six different acquisition decisions](https://saascode.ai/inside/real-estate-brokerage-platforms.md) ## Links - Catalog page: https://saascode.ai/products/domora - Product record: https://saascode.ai/inside/products/domora - Live demo: https://domora.saascode.ai - Every product: https://saascode.ai/llms.txt