A high-level view of how Ray's modules connect, how data flows, and how rules engines govern the network.
Member
│
▼
┌─────────────┐ ┌────────────┐
│ Discovery │────────▶│ Messaging │
└─────────────┘ └────────────┘
│
▼
┌─────────────┐ ┌────────────┐
│ Events │◀───────▶│ Hosts │
└─────────────┘ └────────────┘
│ │
▼ ▼
┌─────────────┐ ┌────────────┐
│ Concierge │────────▶│ Trotter │
└─────────────┘ └────────────┘
│
▼
┌─────────────┐ ┌────────────┐
│ Perks │◀───────▶│ Partners │
└─────────────┘ └────────────┘Event tier
Members → all members; Partner Access → members + partner pass; Invite Only → admin-curated list.
RSVP
If capacity reached → auto-waitlist. Cancellation triggers waitlist promotion in order.
Guest approval
Member submits guest → host receives request → host approves/declines → guest receives access pass.
Introductions
Member A requests intro to B → B confirms/declines → upon accept, private thread is opened.
Membership
Application requires referral or admin sponsor → committee review → status: pending → in review → accepted/declined.
Concierge SLA
Pending → assigned within 2h → in progress → confirmed within SLA tier (Standard 24h, Priority 2h).
Client (Mobile-first PWA)
React + TanStack, optimistic UI, offline-friendly cache.
API Gateway
REST + WebSocket. Auth via OAuth, rate-limited per role.
Rules Engine
Event tiers, RSVP, intros, membership, concierge SLA.
Data Layer
PostgreSQL members + events; Redis cache; S3 media.
Trust & Safety
Profile verification, message moderation, guest screening.
Apply ─▶ Referral ─▶ Committee ─▶ Accept ─▶ Onboard ─▶ Active
│
▼
Decline© The Ray Group · Architecture overview