ZYNC ⚡

The Intelligent All-in-One Workspace for Teams and Developers.

ZYNC is a production-grade collaboration platform designed to unify project management, real-time communication, and developer workflows. It distinguishes itself by integrating AI agents for project planning and automated git operations for task tracking, bridging the gap between planning (Jira/Linear) and execution (GitHub).

---

📚 Internal Documentation

For deep-dives into specific systems, refer to our internal specs:

• API Reference (API.md): Detailed endpoint documentation (Auth, Payloads, Responses).
• System Architecture (ARCHITECTURE.md): Data flows, View-Controller mappings, and Meeting Logic diagrams.
• Database Schema (ERD.md): Reverse-engineered Entity Relationship Diagram (Mongoose & Prisma).
• System Audit (AUDIT.md): A technical audit of the hybrid database architecture and AI logic.
• Design Setup (DRIBBBLE_SETUP.md): Configuration guide for Unsplash, Pinterest, and Behance integrations.

---

🛠️ Deep-Dive Tech Stack

Frontend Architecture (src/)

• Core Framework: React 18 with TypeScript and built via Vite for high-performance HMR.
• State Management:
  • TanStack Query (v5): For server state management, caching, and optimistic updates.
  • Context API: For global UI state (Theme, Auth User).
• Real-Time & Collaboration:
  • Socket.io Client: For instant signaling and live updates.
  • Firebase Firestore: Used as the backing store for the Chat system to ensure message persistence and offline support.
  • YJS: Integrated with BlockNote for eventually consistent collaborative rich-text editing.
• UI System: Tailwind CSS combined with Radix UI primitives for accessible, unstyled components.

Backend Architecture (backend/)

• Runtime: Node.js with Express.js.
• Databases (Hybrid Approach):
  • MongoDB (via Mongoose): Primary document store for unstructured data like Users, Project Plans, and Notes.
  • PostgreSQL (via Prisma): Used specifically for the GitHub Sync Engine to handle structured relational data (Repositories, Task mappings) efficiently.
  • Redis: High-speed session store and caching layer for frequent read operations.
• Authentication:
  • Firebase Admin SDK: Handles ID token verification. We offload identity management to Firebase but sync user profiles to our MongoDB users collection.
• Background Processing:
  • Webhooks: Dedicated endpoints for GitHub App events (push, pull_request).
  • Nodemailer: Custom OAuth2 transport for sending transactional emails via Gmail API.

---

�️ System Architecture & Schema

Data Relationships (Text-based ERD)

erDiagram
User ||--o{ Project : "owns/collaborates"
User ||--o{ Note : "creates"
User ||--o| Session : "tracks activity"
Project ||--o{ Step : "contains"
Step ||--o{ Task : "contains"
User {
string uid PK "Firebase UID"
string email
object integrations "Store Encrypted Tokens"
}
Project {
ObjectId _id PK
string name
string[] githubRepoIds "Linked Repos"
object architecture "AI Generated Docs"
}
Task {
string id PK
string status "Backlog | In Progress | Done"
string assignedTo "User UID"
object commitInfo "Auto-updated via Git"
}

Loading

Key Schemas

1. User (models/User.js): Acts as the central identity. Crucially, it stores encrypted OAuth tokens for GitHub (integrations.github.accessToken) and Google to allow API actions on behalf of the user.
2. Project (models/Project.js): Uses an Embedded Document Pattern for Steps and Tasks. This allows for atomic updates and ensures the entire project plan is loaded in a single query, which is efficient for the Dashboard view.

---

� Key Features Implementation

1. GitHub Bi-Directional Sync

The Problem: Developers hate manually moving Jira tickets. Our Solution: We listen to actual code changes.

• Auth: Users authenticate via OAuth2 (routes/github.js). We exchange the code for an Access Token, encrypt it using AES, and store it in MongoDB.
• Sync Engine:
  • We use a GitHub App Webhook (routes/githubAppWebhook.js) to listen for push events.
  • Signature Verification: Every payload is verified against GITHUB_WEBHOOK_SECRET using HMAC SHA-256 to prevent spoofing.
  • AI Analysis: The commit message is sent to Groq/Llama3, which parses it to find semantic matches to existing tasks (e.g., "fix login bug" -> matches Task "Fix Auth").
  • Auto-Complete: If a match is found, the system automatically marks the Task as Completed in the database and creates a real-time taskUpdated event via Socket.io.

2. Instant Google Meet

• Flow: User clicks "Create Meeting" -> Frontend calls API.
• Backend:
  1. Uses a pre-authorized GOOGLE_REFRESH_TOKEN (Server-side offline access).
  2. Refreshes the Access Token via googleapis Auth client.
  3. Calls calendar.events.insert with conferenceDataVersion: 1.
  4. Returns the generated hangoutLink immediately to the chat.

3. AI Project Generation

• Input: User types "I want a Netflix clone."
• Process:
  1. Prompt Engineering: We wrap this input in a "System Architect" persona prompt.
  2. LLM Call: Sent to Google Gemini 2.5 Flash.
  3. JSON Parsing: The AI returns a structured JSON object containing Phases (Frontend/Backend) and specific actionable Tasks.

4. Persistence: This JSON is hydrated into the Project Mongoose model and saved.

4. Design Inspiration Engine

• Sources: Aggregates creative work from Unsplash, Pinterest, and Behance.
• Mechanism: Uses official APIs (Pinterest/Unsplash) and RSS feeds (Behance) to create a unified searchable feed for localized design research without leaving the app.

---

⚙️ Environment Setup

Combine these variables into your .env files.

1. Backend (backend/.env)

Variable	Description
Core & Database
PORT	Server port (default: 5000)
FRONTEND_URL	URL of the frontend (e.g., http://localhost:5173)
MONGO_URI	Connection string for MongoDB Atlas/Local
REDIS_URL	Redis connection (default: redis://localhost:6379)
Security
ENCRYPTION_KEY	32-char string for token encryption
MASTER_ENCRYPTION_KEY	Master key for system-level encryption
GCP_SERVICE_ACCOUNT_KEY	Firebase Admin Service Account JSON string
Google & Email
GOOGLE_CLIENT_ID	OAuth2 Client ID
GOOGLE_CLIENT_SECRET	OAuth2 Client Secret
GOOGLE_REDIRECT_URI	OAuth2 Redirect URI (e.g., http://localhost:5000/auth/google/callback)
GOOGLE_REFRESH_TOKEN	User-scoped refresh token for Calendar/Mail
GOOGLE_CALENDAR_API_KEY	API Key for public calendar operations
GMAIL_USER	Email address for sending notifications
GMAIL_PASS	App Password (if using 2FA) or Password
GitHub Integration
GITHUB_APP_ID	App ID from GitHub App Settings
GITHUB_CLIENT_ID	Client ID for GitHub App
GITHUB_CLIENT_SECRET	Client Secret for GitHub App
GITHUB_PRIVATE_KEY	Private Key (PEM format, use \n for newlines)
GITHUB_WEBHOOK_SECRET	Secret for verifying webhook signatures
AI Services
GEMINI_API_KEY	Google AI Studio Key (Primary)
GEMINI_API_KEY_SECONDARY	Backup Key
GROQ_API_KEY	Groq Cloud Key (Llama 3)
Design Integrations
UNSPLASH_ACCESS_KEY	Access Key
UNSPLASH_SECRET_KEY	Secret Key
UNSPLASH_APP_ID	Application ID
PINTEREST_APP_ID	App ID
PINTEREST_APP_SECRET	App Secret
PINTEREST_TOKEN	Access Token
PINTEREST_BOARD_ID	Board ID to scrape
DRIBBBLE_CLIENT_ID	Client ID
DRIBBBLE_CLIENT_SECRET	Client Secret
DRIBBBLE_REDIRECT_URI	Redirect URI

2. Frontend (.env)

Variable	Description
VITE_API_URL	Backend URL (e.g. http://localhost:5000)
VITE_FIREBASE_API_KEY	Firebase API Key
VITE_FIREBASE_AUTH_DOMAIN	Firebase Auth Domain
VITE_FIREBASE_PROJECT_ID	Firebase Project ID
VITE_FIREBASE_STORAGE_BUCKET	Firebase Storage Bucket
VITE_FIREBASE_MESSAGING_SENDER_ID	Messaging Sender ID
VITE_FIREBASE_APP_ID	Firebase App ID

---

� Running the Project

1. Install Dependencies

   npm install # Frontendcd backend && npm install

2. Refresh Token Setup (First Run Only) To enable Calendar/Mail features, you must generate a user-scoped refresh token:

   cd backend
   node scripts/get-refresh-token.js
   # Follow on-screen instructions and update backend/.env

3. Start Dev Servers

   • Backend: cd backend && npm run dev
   • Frontend: npm run dev

---

📄 License

MIT License.

---

👥 Contributors

This project was architected and built by:

• Chitkul Lakshya (@ChitkulLakshya)
• Prem Sai Kota (@prem22k)
• Eeshitha Gone (@eesha264)