Business Units Detail
Business Units Detail
Section titled “Business Units Detail”CloudAlt is organized into three business units, each serving different hospitality needs.
Stay Overnight (Pink Guest)
Section titled “Stay Overnight (Pink Guest)”Overview
Section titled “Overview”Hospitality platform connecting travelers with LGBTQ+-friendly accommodations.
Divisions
Section titled “Divisions”- Stay Overnight - Short-term vacation rentals
- Roommate Works - Long-term roommate matching
- Stay Match - Hybrid stays (vacation + long-term)
Backend Service
Section titled “Backend Service”- Service:
stays - Location:
/cloudalt-backend/stays/ - Database: Supabase PostgreSQL
- Schemas:
stays_stayovernight,stays_roommate,stays_staymatch
API Endpoints
Section titled “API Endpoints”AltFinder (Discovery)
Section titled “AltFinder (Discovery)”Overview
Section titled “Overview”Discovery platform for finding LGBTQ+-friendly venues, events, and services.
Divisions
Section titled “Divisions”- AltFinder - Location-based discovery
Backend Service
Section titled “Backend Service”- Service:
discovery - Location:
/cloudalt-backend/discovery/ - Database: Supabase PostgreSQL
- Schema:
discovery_altfinder
API Endpoints
Section titled “API Endpoints”Pride City & Bonjour Locker (Services)
Section titled “Pride City & Bonjour Locker (Services)”Overview
Section titled “Overview”Services platform providing community amenities and storage solutions.
Divisions
Section titled “Divisions”- Pride City - Community services and resources
- Bonjour Locker - Secure storage and delivery services
Backend Service
Section titled “Backend Service”- Service:
services - Location:
/cloudalt-backend/services/ - Database: Supabase PostgreSQL
- Schemas:
services_pridecity,services_bonjour
API Endpoints
Section titled “API Endpoints”Membership Model
Section titled “Membership Model”Centralized per Business Unit
Section titled “Centralized per Business Unit”- Users have one membership per BU
- Membership grants access to all divisions within that BU
- Independent authentication per BU (for privacy)
Example
Section titled “Example”A user who signs up for Stay Overnight (Pink Guest) automatically has access to:
- ✅ Stay Overnight (vacation rentals)
- ✅ Roommate Works (long-term matching)
- ✅ Stay Match (hybrid stays)
But they would need a separate account for:
- ❌ AltFinder (Discovery BU)
- ❌ Pride City/Bonjour (Services BU)
Architecture Decision
Section titled “Architecture Decision”See ADR-001: Centralized Membership for the full rationale.
Database Isolation
Section titled “Database Isolation”Each division maintains its own PostgreSQL schema:
-- Stay Overnight Business Unitstays_stayovernight.*stays_roommate.*stays_staymatch.*
-- Discovery Business Unitdiscovery_altfinder.*
-- Services Business Unitservices_pridecity.*services_bonjour.*This allows for:
- Independent data modeling per division
- Clear boundaries for data privacy
- Easier horizontal scaling per division
- Schema migrations without cross-division impact