iraed/pm-os

Purpose and Runtime

PM-OS is a Laravel 11 modular-monolith SaaS for property-management companies, covering property onboarding, leasing, resident management, billing, and maintenance. It uses Vue 3/Inertia for the authenticated UI and PostgreSQL tenant databases. Docker Compose provides the local runtime: Dockerfile, docker-compose.yml, docker/nginx/conf.d/default.conf.

Application Entry Points

HTTP starts at Laravel route layers: central/web routes in routes/web.php and tenant-scoped routes in routes/tenant.php. Module APIs are independently registered, e.g. app/Modules/Foundation/Routes/api.php, app/Modules/PropertyOnboarding/Routes/api.php, and app/Modules/Collection/Routes/api.php. The browser shell and Inertia client begin at resources/views/app.blade.php and resources/js/app.js.

Tenant Isolation and Bootstrap

The system is database-per-tenant, with central plan/tenant records in app/Core/MultiTenancy/Models/Plan.php and app/Core/MultiTenancy/Models/Tenant.php. Tenancy behavior is configured in config/tenancy.php; tenant schema is separated from central migrations in database/migrations/tenant/. app/Core/ModuleServiceProvider.php is the central integration point for modular application bootstrapping.

Foundation Domain

Foundation owns the portfolio graph and authorization boundary: users, owners, properties, and units. Its HTTP controllers validate requests, apply policy checks, and return resource representations around app/Modules/Foundation/Models/Property.php, app/Modules/Foundation/Http/Controllers/PropertyController.php, and app/Modules/Foundation/Policies/PropertyPolicy.php. Other operational modules attach their records to this property/unit base.

Guided Property Onboarding

Onboarding is a workflow layer over Foundation that creates a property, adds units, gathers documents, inspections, and risk information, and emits lifecycle events. Requests enter app/Modules/PropertyOnboarding/Http/Controllers/OnboardingController.php; orchestration belongs in app/Modules/PropertyOnboarding/Services/PropertyOnboardingService.php; completion is signaled through app/Modules/PropertyOnboarding/Events/PropertyOnboarded.php. This separates multi-step workflow control from core property persistence.

Operational Lifecycle Modules

Leasing records tenancy contracts in app/Modules/Leasing/Models/Lease.php; resident identity/lifecycle is represented by app/Modules/TenantManagement/Models/Resident.php. Financial collection centers on invoices, schedules, and payments at app/Modules/Collection/Models/Invoice.php, app/Modules/Collection/Models/PaymentSchedule.php, and app/Modules/Collection/Models/Payment.php. Maintenance tracks reactive and preventive work via app/Modules/Maintenance/Models/WorkOrder.php, app/Modules/Maintenance/Models/PmPlan.php, and app/Modules/Maintenance/Models/Inspection.php.

Automation and AI Boundary

Scheduled/background jobs drive cross-domain exceptions and recurring work: app/Jobs/Tenant/CheckLeaseExpirations.php, app/Jobs/Tenant/CheckOverdueInvoices.php, and app/Jobs/Tenant/TriggerPreventiveMaintenance.php. Redis/Horizon is the intended queue runtime. AI remains provider-abstracted: app/Modules/AIEngine/Contracts/AIProviderInterface.php isolates callers from OpenAI-specific behavior in app/Modules/AIEngine/Providers/OpenAIProvider.php, with reporting orchestration in app/Modules/AIEngine/Services/AIReportGenerator.php. External Saudi integrations (Ejar, ZATCA, Sadad) are stated as readiness targets, not represented by implementation paths here.