Know the state of your rent. Always.
EstateIQ v1 is an internal multi-company SaaS for real estate companies to track rent status, coordinate follow-ups, and keep leadership informed.
- In scope: orgs + roles, portfolio records, rent schedules and periods, manual payment confirmation, operational follow-ups, reporting, and tracked email reminders.
- Out of scope: payment processing, tenant portal, SMS/WhatsApp automation, accounting, and mobile apps. Maintenance remains outside the agreed v1 scope until its workflows are defined.
- Every domain row is owned by exactly one
organization_id. - Access is granted via
memberships(role-based). - All queries/writes must be org-scoped (and enforced via Supabase RLS).
See docs/saas-multi-tenancy.md.
- Next.js (App Router)
- Supabase (Auth + Postgres + RLS)
- Tailwind CSS + Framer Motion
From estate-iq/:
npm run devOpen http://localhost:3000.
Create .env.local with your Supabase project values (see Supabase dashboard):
NEXT_PUBLIC_SUPABASE_URLNEXT_PUBLIC_SUPABASE_ANON_KEYSUPABASE_SERVICE_ROLE_KEY(server-only)RESEND_API_KEY(server-only)RESEND_FROM_EMAIL(verified sender address)
Migrations live in supabase/migrations/.
Supabase → SQL Editor → run the numbered migration files in ascending order.
Notes:
004_units.sql,006_occupancies.sql,007_rent_configs.sql,008_rent_periods.sql,009_payments.sqlinclude validation triggers to prevent cross-org references.
- Landing:
/ - Auth:
/signin,/signup - App entry:
/app(redirects to onboarding or the first org) - Onboarding:
/app/onboarding - Org dashboard:
/app/org/[slug] - Reminder history:
/app/org/[slug]/reminders
docs/DESIGN_GUIDELINES.mddocs/DATABASE_SCHEMA.mddocs/saas-multi-tenancy.mddocs/DEVELOPMENT_PHASES.mddocs/END_TO_END_FLOW.mddocs/EMAIL_TEMPLATES.md