An AI-powered social interaction platform designed to bridge the gap between busy schedules and meaningful connections.
Everything you need to discover, coordinate, and join real-world events — powered by AI, validated by 27 test suites.
Contrastive-trained neural architecture with GRU history encoder and multi-head self-attention (4 heads) over 52 interest tags. Produces user & event embeddings via pgvector for millisecond-latency One-Tap Suggestions.
User availability is encoded as a 168-dimensional boolean matrix (7 days × 24 hours). Vectorized conflict scanning at O(168) per user detects double-booking instantly before it touches the database.
Uploads any university timetable image. AI OCR extracts courses, days, and hour ranges into Busy Blocks via a Human-in-the-Loop review screen. Source image is permanently purged from the server after parsing — KVKK compliant.
Computes a 52-dim Group Composite Vector (element-wise mean of all participants' interest vectors) and resolves a spatial centroid for fair meeting-point selection. Under-capacity events are autonomously merged via Supabase pg_cron + pgvector similarity.
Live map clusters 1,000+ event pins at <97 ms average latency. Region analysis queries historical event frequency to surface "the spirit of a location." Precise GPS is transient and never persisted.
Event-scoped WebSocket channels powered by Supabase Realtime. Messages are isolated to confirmed participants only — RLS policies enforced at the database engine level, not the app layer.
Sign-up is restricted to verified .edu.tr and whitelisted corporate domains via a live database lookup. Admins can update the Trusted Circle in real-time without a code deploy; under-18 registration is hard-blocked.
Attendance, moderation contributions, and social milestones unlock badges and XP. Each badge awards 10 XP automatically. Busy Mode suspends all AI-generated invitations while active, preventing notification fatigue.
Web-based admin panel for real-time user metrics, ban workflow, and report management. All privileged queries require the Supabase Service Role — standard clients are mathematically blocked by RLS.