Real estate platform architecture and integrations: a reference map and a build order

This technical article is for CTOs, architects and product owners planning a real estate platform or consolidating an existing patchwork of listing, CRM and payment connections. It assumes you already know you need a platform; for the business case and capability modules, start at the real estate platform solution and real estate sector page. This article covers the architecture underneath both.

In this guide

• Which systems does a real estate platform actually connect?
• Reference architecture
• Should integrations run point to point or through a gateway?
• Build order: listings and leads first
• Security, compliance and data ownership
• Where AI fits, and one hard constraint
• What delivery record exists, and what does not
• Alternatives: who builds this integration layer
• When not to build a gateway layer yet
• Limits of this guide
• Frequently asked questions
• Next step

Which systems does a real estate platform actually connect?

A real estate platform rarely stands alone. Map what each surrounding system owns before deciding how to connect it.

The RESO Data Dictionary is the real estate industry's shared standard for listing fields; feeds that support it need less field-mapping per connection, and feeds that do not still need a mapping layer regardless of architecture choice.

Reference architecture

A lead's path through this architecture: an enquiry reaches the lead and CRM layer with its source attached; a routing rule assigns it to an agent with a response deadline; a viewing and an offer move it into the deal engine; a signed offer triggers e-signature and, for a deposit, the trust ledger; a closed deal calculates commission splits from rules on the deal, not typed in afterwards.

Should integrations run point to point or through a gateway?

This is the architecture decision that matters most once a platform grows past its first two connections.

The tipping point is the number of external systems, not the size of the business: one CRM and one MLS feed can stay point to point; several portals plus a CRM, a payment processor and an e-signature provider on the same listing and deal records accumulate enough direct links that one format change becomes a multi-system bug hunt. A gateway does not remove the work of each integration; it stops that work from multiplying every time a system joins.

Security, compliance and data ownership

Netbase security practices apply the same way here as to any system it builds: secure code review, TLS in transit and encryption at rest, role-based access, vulnerability scanning, penetration testing and disaster recovery. Card data and trust/escrow funds carry extra weight: PCI DSS sets baseline requirements for any system that stores, processes or transmits cardholder data, and a trust or escrow account typically needs its own ledger, reconciled separately from the operating account, a rule a generic payment processor does not enforce on its own. GDPR Article 6 requires a lawful basis for processing lead data, recorded at capture, not added later. Listing, lead, tenant and deal records stay in systems you own; integration contracts define what leaves your platform. This is general information, not legal advice.

What delivery record exists, and what does not

Beyond printing and packaging and retail and e-commerce, Netbase has delivered projects for clients in real estate, and these clients are not named. Netbase also builds and runs Poslor, a real estate operating system and Netbase Business Division, which reaches beyond its own site through WordPress, Wix and widget integrations plus a public API, and keeps private workspace data separate from the public listing records it publishes. The anonymous real estate listing platform record describes a listing and lead platform Netbase built for a real estate client as consultant, custom developer and integrator; it names no client, system list, dates or figures.

What does not exist. No published Netbase record names the specific MLS, IDX, payment or e-signature providers connected on either project, and no integration count, migration duration, cost or uptime figure is published for either. The reference architecture and the point-to-point-versus-gateway decision come from Netbase's general integration-architecture delivery practice (see the ERP, CRM and e-commerce integration architecture guide for the same pattern on a different system mix) and the cited standards, not from a measured real-estate integration count.

Alternatives: who builds this integration layer

Netbase leads with consulting, custom development and digital transformation; most projects are delivered on fixed-price contracts, scope agreed after a workflow review, with milestone-based, monthly team retainer and KPI-linked models also offered. In custom development, you own the IP Netbase creates for you; Poslor and other productized modules are licensed, not transferred. The team works remote-first from Hanoi in English, and reusing a module such as the real estate digital toolkit can cut development time by up to 60% where it fits.

When not to build a gateway layer yet

• One or two integrations today, no concrete plan to add more. A gateway adds a component to run and secure before it has removed any real pain.
• The MLS or portal relationship is still being negotiated. Architecture decisions are cheaper after the data-sharing terms are set, not before.
• No capacity to own the gateway's uptime. A badly maintained integration layer is worse than a few direct connections someone actually watches.

Limits of this guide

• It describes a reference architecture and a general decision rule; every MLS, portal and payment provider's API and licensing terms differ.
• PCI DSS, GDPR Article 6, the RESO Data Dictionary and the Fair Housing Act are cited for what they define or require, not as a claim that a Netbase project has been certified or audited against them.
• No integration count, build duration, cost or uptime figure is claimed for a Netbase real estate project.
• The point-to-point-versus-gateway tipping point is a planning heuristic, not a measured threshold from a published real estate case.

Next step

Tell us which MLS or portal feeds, CRM and payment or trust-accounting systems you run today, and we will book a solution review to map the integration architecture and the first build order. You can also see the real estate platform solution, the real estate sector page, or browse more Netbase insights.

Related services and solutions