Domora
Domora is a multi-tenant operating system for real-estate brokerages, connecting a branded property portal with a private workspace.
This platform is an operating system for real-estate brokerages. Each brokerage is one organization on the platform and gets two connected surfaces.
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.
- Property inventory and media (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)
- Outbound portal publication
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.
- Demands and saved searches
- Deterministic matching
- Opportunity pipeline (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)
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.
- Owner participation
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.
- Commissions (Fixed or percentage commission rules with one beneficiary allocation per closed operation)
- Comparable valuation
- Brokerage analytics/reports
Each portal connection counts against the organization's plan limit. Some portals require a commercial contract before any connection can be made; those show a contract-required state rather than pretending to be available.
Valuation produces an orientative price range for a property from the brokerage's own eligible closed operations. It is deliberately narrow:
Everything counted here comes from the organization's own records. Nothing is benchmarked against other brokerages on the platform, because their data is not visible.
The platform underneath the product — counted in this product's own source, not claimed from a template. Where a row carries a list, open it to read the names behind the number.
Coinbase
dLocal
Flutterwave
Komoju
Mollie
NOWPayments
Opn
Paystack
ActiveCampaign
Customer.io
Segment
Canny
Amplitude
Custom Head Scripts
Pushover
Twilio SMS
Crisp
Tawk.to
Monday.com
fal.ai
Axiom
hCaptcha
Freshsales
Pipedrive
Pabbly Connect
AWS S3
MuxHover a table to isolate what it touches; click one to read its relationships. The big nodes are what everything else hangs off. organizations is referenced by 69 tables because every single record in this product belongs to an organization, and that is what makes tenant isolation a property of the database rather than something the application has to remember on every query.
all 83 tables, as text
active_boosts · activities · admin_notifications · agent_availability · analytics_daily · analytics_events · analytics_funnels · announcement_dismissals · announcements · api_key_logs · api_keys · assistant_actions · assistant_conversations · assistant_messages · assistant_usage · audit_logs · automation_log · automation_templates · brokerage_profiles · commission_allocations · commission_rules · contacts · country_profiles · credit_balances · credit_transactions · currencies · custom_domains · data_exports · data_imports · delivery_attempts · demands · faq_categories · faq_items · favorites · feature_flags · inbound_webhook_events · inbound_webhooks · inquiries · languages · marketing_audience_members · marketing_audiences · match_runs · matches · notification_log · notification_rules · notifications · opportunities · organization_limit_overrides · organizations · pipeline_stages · plans · platform_secrets · platform_settings · portal_connections · product_purchases · products · properties · property_media · property_owners · property_publications · provider_prices · publication_attempts · push_devices · report_deliveries · report_templates · roles · scheduled_tasks · seo_meta · subscriptions · theme_page_sections · theme_section_library · theme_sections · translations · user_sessions · users · valuation_comparables · valuation_runs · visitor_accounts · visitor_auth_tokens · visitor_sessions · visits · webhook_logs · webhooks
The chassis, and anything particular to this product. 2 required, 2 optional.
A Node host for Next 16.2.10 and a Supabase project; `package.json` does not pin a Node release.
Three jobs are declared in `vercel.json`; reproduce those schedules when hosting outside Vercel.
Choose one of the shipped Brevo, Mailgun, Resend, SendGrid or SMTP adapters when email delivery is enabled.
The environment template exposes optional Upstash and Sentry integrations.
Already built — plug and play
Every provider integration in this list ships wired into the product. You bring your own keys, connect them in the admin, and go live — there is no integration code to write. Nothing is resold through us: the ongoing cost is whatever these providers charge you. Capabilities marked plan-gated elsewhere on this page unlock by plan, not by extra code.
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.