Scattered operational data
Property, tenant, lease and financial information needs to stay connected while supporting more than one organization.
Back to projectsVisit live product
Property management SaaS
Immo-Manager: a connected operating system for property teams.
A multi-organization platform that brings property operations, tenant workflows, financial activity, documents and communication into one connected web and mobile product.
- React
- TypeScript
- Laravel
- React Native + Expo
- MySQL
- Redis
- Docker
- Real-time events
The problem
Property operations need a shared source of truth.
Property teams often coordinate leases, documents, payments, resident communication and field activity across disconnected tools. The result is fragmented context, slow follow-up and inconsistent visibility across organizations.
Different people need different surfaces
Owners, agencies, field agents, tenants and home seekers need secure experiences designed around their work.
Time-sensitive actions cannot wait
Messages, payment events, documents and maintenance requests need dependable notifications and accountable follow-through.
The solution
One platform, tailored to each property workflow.
Immo-Manager combines a role-aware web back office, a mobile companion and public listing experiences around a common application and data layer.
Portfolio & tenancy
Organize properties, units, tenants, leases, financial activity and supporting records in connected workflows.
Role-aware operations
Give administrators, owners, agents and tenants access to the right information and actions for their role.
Mobile field work
Extend the platform beyond the desk with a connected mobile application for work that happens on-site.
Reliable communication
Use real-time updates, queued jobs, email delivery and push notifications for high-value operational events.
Architecture
A web, mobile and service architecture designed to evolve.
The platform connects React web clients, a React Native mobile application and public listing sites to a Laravel API and supporting operational services.
Public-safe architecture overview. Private infrastructure configuration, credentials and customer data are intentionally omitted.
How I approached the build
A deliberate path from workflow to operation.
The architecture is only useful when it supports a practical sequence of engineering decisions.
- 01
Model the operating domain
Start with organizations, role boundaries, properties, units, tenants, leases and financial records so each workflow has a reliable foundation.
- 02
Build connected user journeys
Create focused web, mobile and public experiences that use the same platform capabilities without forcing every user into the same interface.
- 03
Make work asynchronous where it matters
Use real-time events, background queues, scheduled work and notification delivery to keep operational actions responsive and traceable.
- 04
Operate as a product
Run the services with TLS entry points, containerized components, persistent data services and integrations that can be maintained over time.
Engineering focus
What this project demonstrates.
SaaS architecture
Multi-organization structure, role-aware access and business workflows designed for complex property operations.
End-to-end delivery
Web, mobile, API, data, real-time communication and background processing considered as one product system.
Integration & operations
Payment, media, identity, mapping, email and mobile push capabilities connected through maintainable service boundaries.
Property management SaaS