Multi tenant real estate SaaS

MaklerFlow

A platform where property page, listing document, document access and applicant flow build on the same source of truth. Its technical core is a consistently multi tenant architecture.

Role: Product, system design and full stack implementation
Context: Independent product
Ownership: Sole owner, with implementation and reviews orchestrated across specialised agents
Delivery state: Active development
Evidenced: Architecture, real listing renderer and tenant boundaries evidenced
Next proof: Typecheck, lint and production build verified, pilot impact not yet measured
Period: Since June 2026

System viewMaklerFlow / 2026

01One property sourceproperty_id

02Property page

03Listing document

04Application

Tenant boundarySupabase RLS and regression tests

✓

Context

Property data is often maintained repeatedly across PDFs, portals and separate tools. At the same time, tenants, applicants and public visitors must only see the exact data intended for them.

My contribution

Built the tenant model with Supabase RLS and Drizzle

Modelled the property as the shared source for public and internal workflows

Implemented listing editor, energy certificate review and demo property

Translated security reviews into concrete RLS regression tests

Mobile MaklerFlow development capture of a synthetic property listing

Real listing components in an isolated local harness with synthetic data

Decisions that shaped the product

One property, multiple states

Public page, listing document and applicant flow are not separate data silos. They project controlled views of the same property.

Isolation at database level

Tenant boundaries are not checked only in the interface. RLS policies, claims and regression tests form an additional protection layer below the application.

Real database before merge

Seven delivery waves each passed five quality gates. Integration tests against real Postgres caught two tenant boundary defects that a locally green run with skipped database tests would not have exposed.

Technical evidence

Quality gate

Typecheck, lint and build passed

Source: local repository verification
Verified: 2026-07-16

Internal evidence, available during a technical interview

Delivery process

13 issues / 7 waves

Source: docs/handoffs/2026-07-10-expose-usp-w1-w7.md
Verified: 2026-07-10

Internal evidence, available during a technical interview

Verified revision

15bc4bb

Source: local Git HEAD
Verified: 2026-07-16

Internal evidence, available during a technical interview

Honest boundary

Not every production interface is visually final. The development capture therefore shows the real listing renderer in an isolated local harness with fully synthetic data rather than a production customer property.