Axis Housing
Property management software for listing units, screening applicants, signing leases, collecting rent, and running day-to-day operations. The product ships as a Next.js web app at prop-lane.space, plus iOS and Android native shells (Capacitor) that load the live site. The legacy axis-seattle-housing.com domain still resolves and is still treated as production.
Product surfaces
| Surface | Path | Who |
|---|
| Marketing | / (the one scroll page: how it works, software, service, pricing, contact), /partner | Prospective property managers |
| Property portal | /portal | Property managers and house owners (Free, Pro, Business tiers) |
| Resident portal | /resident | Tenants linked to a manager |
| Vendor portal | /vendor | Contractors a manager invites to services |
| Admin portal | /admin | Platform operators |
| Public apply & tour flows | /rent/browse, /rent/apply, /rent/tours, /rent/listings/[id] | Applicants (manager-shared links) |
| Phone-bound doors | /l/[token], /apply/[code], /tour/[code], /start/[token] | Anyone who texted the PropLane line (pay, unlock, finish setup) |
Property portal (/portal)
Properties, tour scheduling, rental applications, resident & lease management, move-in / move-out inspections, household charges, Stripe Connect payouts, services & vendors, inbox, documents & tax reporting, co-managers, and subscription billing (Free / Pro / Business).
In Settings → Workspaces, adding your first named workspace creates just
that workspace and marks it Default. Use the trash icon beside the pencil
to delete any workspace you own, including the default. Empty workspaces need
only confirmation; workspaces with houses ask for another workspace you own
and Move and delete moves the houses and removes the workspace together.
Ownership and permissions stay with the houses; destination capacity still
applies. If your only workspace has houses, add another workspace first.
Deleting the default passes its label to the oldest remaining workspace.
Deleting the last empty workspace returns to Create your first workspace;
adding a house with no workspace still creates My workspace automatically.
House owners
There is no separate owner portal: an owner opens the Property portal like everyone else, and the old /portal/owner/* URLs redirect into it. A house owner who should only look is invited as a Viewer from Settings → Workspaces (the Property owner role has left the invite picker; existing owner rows keep working). An owner of a PropLane-managed workspace sees the portal view-only — no create, edit, archive or delete — under a “Managed by PropLane · View only” strip, with their money in Finances → Owner payouts. Contracts: docs/agents/co-manager-access.md § Property owner and docs/agents/owner-management.md.
Resident portal (/resident)
Rent & utility payments (card incl. Apple Pay / Google Pay, or bank/ACH — captured by PropLane on Stripe and paid out to the manager), My home (house info & rules, opt-in housemate sharing, move-in / move-out inspections), services, inbox, lease & receipts, and Application — where a short stay is a row beside the lease applications (Sent | Approved | Denied, with Request again on one). Full workspace unlocks after lease approval.
Vendor portal (/vendor)
The contractor's side of services: the jobs a manager offered or assigned, bids, calendar, communication, Finances (balance & payouts, payments, statements, tax info), documents, reviews with replies, a free PropLane work email, and an optional PropLane Number ($5/month) for manager and resident contact. Contract: docs/agents/vendor-portal.md.
Platform capabilities
- Auth — Supabase (email/password, Google OAuth), role-based portals. Every sign-up door also
asks for a phone, and a manager can create the account entirely by text to the PropLane line
(a code texted back is the proof). Contract:
docs/agents/manager-account-creation.md.
- Payments — Stripe Checkout subscriptions for managers; Stripe Connect for resident rent & fees
- Comms — Resend email, Twilio SMS, Firebase push (native apps)
- Screening — Certn credit & background checks (optional)
- Cron jobs — Payment reminders, move-in reminders, scheduled inbox (Vercel Cron)
Tech stack
- Framework — Next.js 16, React 19, TypeScript
- Styling — Tailwind CSS v4, Radix UI
- Data — Supabase (Auth + Postgres), SQL migrations in
supabase/migrations/
- Payments — Stripe (subscriptions + Connect)
- Native — Capacitor 8 (
space.proplane.app)
- AI — Anthropic SDK + a thin custom agent loop, exposed through the typed
tool layer in
src/lib/tools/
- Observability — PostHog (product analytics, performance, session replay)
and Langfuse (agent traces + the thumbs-rating eval loop)
- Tests — Vitest (unit + integration), Playwright (e2e)
Requires Node 22.x and npm 10.x (see package.json engines).
Local development
1. Install dependencies
npm install
2. Environment
cp .env.example .env.local
Fill in the required values in .env.local — at minimum:
NEXT_PUBLIC_APP_URL, NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY, SUPABASE_SERVICE_ROLE_KEYSTRIPE_SECRET_KEY, NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY, STRIPE_WEBHOOK_SECRETSupabase_Database_Password (for applying migrations)
Optional integrations (email, SMS, push, screening) are documented in .env.example with comments.
3. Database
Apply Supabase migrations:
npm run db:apply-sql
Bootstrap an admin account (after Supabase vars are set):
npm run admin:sync-account -- [email protected] 'YourPassword'
Create or verify Stripe subscription prices:
node --env-file=.env.local scripts/setup-stripe-plan-prices.mjs
4. Run the dev server
npm run dev
Open http://localhost:3000.
For Stripe webhooks locally, use node scripts/stripe-listen.mjs (see docs/stripe-ach-local-test.md).
Scripts
| Command | Purpose |
|---|
npm run dev | Start Next.js dev server |
npm run build / npm start | Production build & serve |
npm run lint | ESLint |
npm run typecheck | next typegen (generates the route types tsc needs) then tsc --noEmit |
npm run check | Lint + unit tests + build |
npm run test:unit | Vitest unit tests |
npm run test:integration | Vitest API integration tests |
npm run test:e2e | Playwright browser tests (full 158-case suite) |
npm run test:e2e:smoke | Bounded 14-case public smoke — the browser gate CI runs on main |
npm run test:all | All Vitest + Playwright |
npm run db:apply-sql | Apply supabase/migrations/ to Postgres |
npm run cap:sync / cap:ios / cap:android | Capacitor sync & open native IDEs |
Admin utilities: admin:sync-account, admin:set-manager-plan, admin:ensure-demo-manager, admin:purge-managers.
Testing
Use a dedicated Supabase test project — never production credentials.
# Configure .env.test with a dedicated Supabase test project (see tests/README.md)
npm run test:unit
npm run test:integration
npm run test:e2e:smoke # bounded public smoke (same slice CI runs on main)
npm run test:e2e # full suite; requires running app + .env.test
Full details: tests/README.md.
Native apps (iOS + Android)
Capacitor shells load the production site in a WebView and add push notifications, camera capture, status bar, and splash screen. Web/UI changes deploy via Vercel with no app-store review; native-shell changes require rebuild and resubmission.
See docs/mobile-app.md and docs/firebase-push-setup.md.
Documentation
Deployment
The app is designed for Vercel. Set all production env vars from .env.example, configure Supabase redirect URLs for your domain, and set CRON_SECRET for /api/cron/* routes (see vercel.json).
