PropLane

Property operations, connected from the first application to everyday resident support.

Co-Founder & CTO

Visit project Source unavailable publicly
PropLane property operations dashboard from its public marketing site
Actual PropLane interface · public marketing screenshot.
Open full image

Leasing, rent collection, maintenance and communication belong to the same property workflow, but are often managed in separate tools.

Built the multi-tenant platform, permission-scoped assistant, Stripe Connect flows and Capacitor mobile delivery, as documented in my résumé.

A shared home for property work

  • Role-specific web portals for property operations and resident self-service.
  • Applications, leases, payments, inspections, work orders and communication in one product.
  • Native iOS and Android shells around the web experience.

Roles, payments and delivery

  • Next.js and TypeScript provide the shared application; Supabase provides authentication and PostgreSQL storage.
  • Stripe Connect handles resident payments, while separate subscription flows support manager plans.
  • A typed tool layer connects the assistant to permission-scoped product actions.

Boundaries built into the product

  • Tenant isolation and permissions are part of the data and tool boundaries.
  • Capacitor keeps web and native delivery on a shared product foundation.
  • Payment reminders and scheduled communication run as background workflows.

Context and limits

Active product. Source is private; the image is the real interface published on the public marketing site.