CloudAlt App Foundry Business Unit Architecture

Organizational Hierarchy

CloudAlt Company
├── 5 Business Units (BUs) - Self-Contained (Modular) Units
│   ├── BU #1: Stays (32 apps)
│   ├── BU #2: Friendly (4 apps)
│   ├── BU #3: Services (4 apps)
│   ├── BU #4: Lingua (5 apps)
│   └── BU #5: Life (3 apps)
│
├── 10 Divisions
│   ├── D1: Stay Overnight → Stays → Network hospitality
│   ├── D2: Twinship → Stays → Double occupancy travel partner matching
│   ├── D3: Roommate → Stays → Long-term roommate matching
│   ├── D4: altFriendly, TANDUP, Tapear → Friendly → Platonic friend & activity partner discovery
│   ├── D5: Pride City → Services → Community Marketplace
│   ├── D6: Bonjour → Services → Digital privacy and concierge service marketplace
│   ├── D7: Speech Therapy → Lingua → Speech Tree: Exercise-based rehab for stroke/TBI recovery & kids
│   ├── D8: Field Linguistics → Lingua → LingKit: Kiosk-in-hand for documenting endangered languages
│   ├── D9: Language Learning → Lingua → LingKit IPA Listen & Learn: Phonetics training & language tool
│   └── D10: Life Scheduler → Life → AI-powered task management
│
├── 47 Branded Apps
│   ├── 19 Stay Overnight apps (D1)
│   ├── 7 Twinship apps (D2: pairaway, twinship, cabinmate, vegasbuddy, resortbuddy, skibuddy, travelpairing)
│   ├── 6 Roommate apps (D3)
│   ├── 3 Friending apps (D4: altFriendly, TANDUP, Tapear)
│   ├── 1 Pride City app (D5)
│   ├── 3 Bonjour apps (D6)
│   ├── 2 Speech Therapy apps (D7)
│   ├── 1 Field Linguistics app (D8)
│   ├── 2 Language Learning apps (D9)
│   └── 3 Life Scheduler apps (D10)
│
└── 5 Django Projects - Backend Infrastructure
    ├── stays/ (port 8001) → BU1 Stays (D1, D2, D3)
    ├── friendly/ (port 8002) → BU2 Friendly (D4)
    ├── services/ (port 8003) → BU3 Services (D5, D6)
    ├── lingua/ (port 8004) → BU4 Lingua (D7, D8, D9)
    └── life/ (port 8005) → BU5 Life (D10)
        

Business Units (Strategic Layer)

Purpose:

• Group by business logic and shared capabilities
• Designed as self-contained (modular) units (each BU operates independently)
• Django Project = Business Unit = Self-Contained Unit

BU #1: Stays (stays/ Django project)

Port: 8001
Database: Supabase (redacted)
Membership ID: STAY-XXXXXX

Divisions:

• D1: Stay Overnight (19 apps) - Flagship: stayovernight.app
• D2: Twinship (7 apps) - Flagship: pairaway.app + twinship, cabinmate, vegasbuddy, resortbuddy, skibuddy, travelpairing
• D3: Roommate (6 apps) - Flagship: roommate.works

Total Apps: 32 branded applications

Shared Business Logic:

• People-matching algorithms
• Compatibility scoring (hosts/guests, roommates, travel companions)
• Profile management
• Booking workflows
• Payment processing
• Review systems
• Messaging infrastructure

Why Together:

• All involve lodging/housing
• Same regulatory requirements
• Shared matching engine (different contexts)
• Cross-selling opportunities (Roommate user → Stay Overnight)

BU #2: Friendly (friendly/ Django project)

Port: 8002
Database: Supabase (redacted)
Membership ID: FREN-XXXXXX

Divisions:

• D4: altFriendly, TANDUP, Tapear (3 apps) - Flagship: altfriendly.app

Total Apps: 2 branded applications

Shared Business Logic:

• Activity-based friend matching
• Interest & hobby profiling
• Community-verified ratings
• Location-based matching

Strategic Note:

• The friendly alternative to dating apps: altFriendly for everyone, TANDUP for men
• Loneliness is real: The U.S. Surgeon General's 2023 advisory declared loneliness an epidemic—1 in 2 U.S. adults report measurable levels of loneliness, with health risks comparable to smoking 15 cigarettes daily(2023)
• Gen-Z is hooking up less opening an opportunity for friending apps: Studies show Gen-Z has fewer sexual partners and dates less frequently than Millennials or Gen-X did at the same age—yet they're lonelier than ever(Cigna, 2020; 2025)
• Third places are disappearing: UK lost over 15,000 or a third of its pubs since 2000 (British Beer and Pub Association, 2025); U.S. sees declining attendance at the casual spaces where friendships once formed organically are disappearing (1989; 2020)
• Not everyone wants to date: Dating apps dominate virtual spaces for "meeting people" and do not serve those who seek platonic connection

BU #3: Services (services/ Django project)

Port: 8003
Database: Supabase (redacted)
Membership ID: SERV-XXXXXX

Divisions:

• D5: Pride City (1 app) - Flagship: pride.city
• D6: Bonjour (3 apps) - Flagship: bonjour.locker

Total Apps: 4 branded applications

Shared Business Logic:

• Community platforms
• Service marketplace
• Provider networks
• Event management (Pride City)

BU #4: Lingua (lingua/ Django project)

Port: 8004
Database: Supabase (TBD)
Membership ID: LING-XXXXXX

Divisions:

• D7: Speech Therapy (2 apps) - Flagship: speechtree.app + junior.speechtree.app
• D8: Field Linguistics (1 app) - Flagship: lingkit.app
• D9: Language Learning (2 apps) - ipa.lingkit.app, learn.lingkit.app

Total Apps: 5 branded applications

Shared Business Logic:

• Language processing and analysis
• Audio/speech recording and playback
• Progress tracking and learning paths
• IPA (International Phonetic Alphabet) tools

BU #5: Life (life/ Django project)

Port: 8005
Database: Supabase (TBD)
Membership ID: LIFE-XXXXXX

Divisions:

• D10: Life Scheduler (3 apps) - Flagship: lifescheduler.app, Life Push, Life Raise

Total Apps: 3 branded applications

Shared Business Logic:

• AI-powered task management
• Time blocking and scheduling
• Wellness and productivity tracking
• Smart notifications

Divisions (Customer-Facing Layer)

Purpose:

• Customer-facing brands with distinct value propositions
• Group apps with similar use cases
• Each division maps to one Business Unit

Division Breakdown:

Click on any division name to see all apps and domains

Branded Apps (Marketing & Delivery Layer)

Purpose:

• Marketing segmentation via color-themed branding
• User choice and personalization
• Delivery channel (web + mobile per brand)
• A/B testing of brand positioning with minimal development cost

Brand Strategy:

Multiple apps per division with:

• ✓ Same functionality (shared codebase)
• ✓ Same backend (same Django project + database)
• ✓ Different colors/themes (brand-level tokens)
• ✓ Different marketing positioning

Complete App Inventory by Division:

Stay Overnight Division (19 apps):

Flagship: stayovernight.app - Direct descriptor branding

stayovernight.app        → Blue #3B82F6           → General market flagship
hostguest.app            → Teal #14B8A6           → Official Stay Overnight brand (hostguest_app)
hostguest.com            → Companion domain       → Brand protection & alt TLD
pinkguest                → Pink #F90772           → LGBTQ+ focused
purpleguest              → Purple #8A2BE2         → Alternative branding
orangeguest              → Orange #FF8C00         → Alternative branding
rainbowhost              → Rainbow gradient       → LGBTQ+ host focus
greenhost_app            → Green #228B22          → Eco-friendly angle
guestroom_city           → Urban palette          → City focus
guestroom_help           → Service colors         → Service angle
guestroom_host           → Host-centric           → Host-focused
guestroom_lgbt           → Pride colors           → LGBTQ+ focus
guestroom_pink           → Pink variant           → Pink branding
guestroom_travel         → Travel blue            → Travel TLD
homestay_international   → Global colors          → International market
homestay_lgbt            → Pride focus            → LGBTQ+ homestay
        

Roommate Works Division (5 apps):

Flagship: roommate.works - Professional/functional branding

roommate.works           → Burgundy + Slate      → General market flagship
roommate.guru            → Burgundy + Gold       → Expert positioning
roommate.help            → Burgundy + Sky Blue   → Service angle
rooms_gay                → Pride colors          → LGBTQ+ roommate focus
room_lgbt                → Pride branding        → LGBTQ+ rooms
        

Twinship Division (7 apps):

Flagship: pairaway.app - Double occupancy travel companion pairing

pairaway.app             → Indigo #4B0082        → Division flagship - travel companion pairing
twinship.app             → Indigo #4B0082        → Alt flagship - single travelers seeking companions
cabinmate.app            → Cruise Blue           → Cruise cabin mate matching
vegasbuddy.app           → Vegas Gold            → Vegas trip companion matching
resortbuddy.app          → Resort Teal           → All-inclusive resort buddy matching
skibuddy.app             → Alpine White          → Ski trip companion matching
travelpairing.app        → Indigo #4B0082        → SEO/Marketing test - generic travel pairing
        

altFriendly Division (3 apps):

Flagship: altfriendly.app - Activity-based platonic friend matching

altfriendly.app          → Primary brand         → General market flagship
tandup.app               → TANDUP                → Gay men's friend-matching app
tapear.app               → Tapear                → Real-time after-work social coordination
        

Pride City Division (1 app):

Flagship: pride.city - LGBTQ+ community hub

pride.city               → Pride colors          → LGBTQ+ community events & services
        

Bonjour Division (3 apps):

Flagship: bonjour.locker - Service Marketplace and Digital Privacy Solutions

bonjour.locker           → Primary brand         → Service marketplace flagship
bonjour.services         → Service marketplace   → Digital concierge
bonjour.buzz             → Service discovery     → Alerts and notifications
        

Total: 47 branded applications across 10 divisions

Market Positioning:

• 31 apps: General market with inclusivity-positive approach
• 15 apps: Pride-niche (LGBTQ+ community-focused)

Complete App Inventory (48 Apps)

Django Projects (Backend Infrastructure)

Django

Our backend is organized into five Django projects—one per Business Unit. This structure was selected to optimize for three organizational priorities:

Strategic Flexibility
Each Business Unit operates as a self-contained service, enabling independent scaling, licensing, or divestiture without cross-BU dependencies.

Development Efficiency
Divisions within each BU share common business logic, authentication, and data models—reducing duplication while maintaining clear boundaries.

Operational Clarity
Each project runs on its own port with dedicated configuration, simplifying deployment, monitoring, and team ownership.

Project Structure:

cloudalt-django/
├── stays/                     # BU #1: Stays (port 8001)
│   ├── manage.py
│   ├── config/
│   ├── members/               # Universal membership (BU-level)
│   ├── stay_overnight/        # D1: Division-specific logic
│   ├── twinship/              # D2: Division-specific logic
│   └── roommate/              # D3: Division-specific logic
│
├── friendly/                 # BU #2: Friendly (port 8002)
│   ├── manage.py
│   ├── config/
│   ├── members/               # Universal membership (BU-level)
│   └── altfriendly/           # D4: Division-specific logic
│
├── services/                  # BU #3: Services (port 8003)
│   ├── manage.py
│   ├── config/
│   ├── members/               # Universal membership (BU-level)
│   ├── pride_city/            # D5: Division-specific logic
│   └── bonjour/               # D6: Division-specific logic
│
├── lingua/                    # BU #4: Lingua (port 8004)
│   ├── manage.py
│   ├── config/
│   ├── members/               # Universal membership (BU-level)
│   ├── speech_therapy/        # D7: Division-specific logic
│   ├── field_linguistics/     # D8: Division-specific logic
│   └── language_learning/     # D9: Division-specific logic
│
└── life/                      # BU #5: Life (port 8005)
    ├── manage.py
    ├── config/
    ├── members/               # Universal membership (BU-level)
    └── life_scheduler/        # D10: Division-specific logic
            

Key Architecture Principles

1. Membership Model: BU-Level, Not App-Level

Problem Solved: User signs up on pinkGuest → Should auto-login to orangeGuest, roommate_guru, etc.

Solution:

• ✓ One profile per Business Unit (not per app)
• ✓ Division tracking flags: joined_stay_overnight, joined_twinship, joined_roommate
• ✓ Single sign-on: Works across all apps in same BU
• ✓ Cross-division join: One-click enrollment without re-signup

2. Shared vs. Division-Specific Logic

Shared at BU Level:

• Authentication (Supabase Auth)
• Universal MemberProfile model
• API utilities (pagination, filtering)
• Middleware (CORS, logging, JWT validation)

Division-Specific:

• HostProfile, GuestProfile (Stay Overnight)
• RoommateProfile (Roommate)
• Listings, Bookings, Reviews
• Matching algorithms (tuned per division)
• Payment flows (Stay Overnight, Roommate only)

3. Frontend Organization

cloudalt-react/apps/
├── bu1/stays/
│   ├── stay-overnight/        # D1: 19 apps
│   │   ├── pinkguest/
│   │   │   ├── web/           # React web app
│   │   │   ├── mobile/        # React Native mobile
│   │   │   └── shared/        # Shared code
│   │   ├── stayovernight/
│   │   └── ... (17 more)
│   │
│   ├── twinship/              # D2: 7 apps
│   │   ├── pairaway/
│   │   ├── twinship/
│   │   ├── cabinmate/
│   │   ├── vegasbuddy/
│   │   ├── resortbuddy/
│   │   ├── skibuddy/
│   │   └── travelpairing/
│   │
│   └── roommate/              # D3: 6 apps
│       ├── roommate_works/
│       └── ... (5 more)
│
└── bu2/friendly/             # D4: 3 apps
│   └── altfriendly/
│       ├── altfriendly_app/
│       ├── tandup/
│       └── tapear/
│
├── bu3/services/              # D5-D6: 4 apps
│   ├── pride-city/
│   └── bonjour/
│
├── bu4/lingua/                # D7-D9: 5 apps
│   ├── speech-therapy/
│   ├── field-linguistics/
│   └── language-learning/
│
└── bu5/life/                  # D10: 3 apps
    └── life-scheduler/

cloudalt-flutter/apps/         # Same BU structure
└── (mirrors React structure)

packages/                      # Shared code
├── ui/                        # Cross-division UI components
├── ui-twinship/               # Division-level UI components
├── theme/                     # Brand color tokens (21 themes)
├── types/                     # TypeScript types
└── services/                  # API clients
            

4. Brand Theming System

Theme (T01-T22) → Colors only | UX Profile (R01-R15) → Typography, spacing, shapes, shadows, animations

// Theme Layer (colors) - 22 themes
theme['T01-pink'].colors.primary = '#F90772'     // pinkGuest
theme['T02-orange'].colors.primary = '#FF8C00'   // orangeGuest
theme['T03-purple'].colors.primary = '#9370DB'   // purpleGuest

// UX Profile Layer (non-color properties) - 15 profiles
uxProfile['R01-warm'].typography.scale = 1.2
uxProfile['R01-warm'].spacing.base = 8
uxProfile['R01-warm'].animation.duration = 'moderate'

// Note: Division is an organizational grouping, NOT a token layer
            

Brand Colors:

Delivery & Deployment

Backend Deployment:

GCP Cloud Run (containerized)
├── stays-api:8001        → BU1 Stays (D1, D2, D3)
├── friendly-api:8002    → BU2 Friendly (D4)
├── services-api:8003     → BU3 Services (D5, D6)
├── lingua-api:8004       → BU4 Lingua (D7, D8, D9)
└── life-api:8005         → BU5 Life (D10)

Each with:
- Auto-scaling
- Load balancing
- Supabase managed PostgreSQL
- Cloud Storage (GCP) for media
- Firestore for real-time chat
        

Frontend Deployment:

Cloudflare Pages (static sites)
├── pinkguest.com         → D1 Stay Overnight / pinkguest
├── stayovernight.app     → D1 Stay Overnight / flagship
├── pairaway.app          → D2 Twinship / flagship
├── twinship.app          → D2 Twinship / alt flagship
├── roommate.works        → D3 Roommate / flagship
├── altfriendly.app       → D4 altFriendly / flagship
├── pride.city            → D5 Pride City / flagship
├── bonjour.locker        → D6 Bonjour / flagship
├── lingkit.app           → D8 Field Linguistics / flagship
├── lifescheduler.app     → D10 Life Scheduler / flagship
└── ... (48 total apps)

Each with:
- Global CDN
- Cloudflare Access (GitHub OAuth)
- GitHub Actions auto-deploy
        

Summary

Workflow

Production Logic

• BL lives at BU level (Django projects)
• Marketing & user choice happens at app level (branded apps)
• Divisions bridge the two (customer-facing org)