An open-source, AI-native collaborative workspace. Plan, design, and write together in real-time.
Live App • Discussions • Documentation • LinkedIn • Contact
Modern teams are forced to fragment their workflows across five different apps: one for whiteboarding, one for docs, one for tasks, and another for AI generation.
Zync is an open-source, all-in-one workspace. We merge real-time document editing, visual canvasing, and project management into a single, local-first platform. Unlike other tools, Zync is supercharged by multi-modal AI from the ground up to automate the busywork of project management.
Your data, your servers, your workflow. Zync is built to be a better, open-source alternative to tools like Notion, Miro, and Linear.
Many productivity apps claim to be a canvas, but Zync actually merges the doc and the whiteboard. Our flexible block-based architecture allows you to drop rich text, sticky notes, embedded web pages, multi-view databases, and shapes onto a limitless, edgeless canvas.
Zync integrates with Kilo Code Gateway (primary architecture agent) and Groq (fast task generation & commit analysis) as AI co-pilots.
- Architecture Agent: Natural-language chat → structured JSON architecture maps via Kilo Gateway (
kilo-auto/free). - Project Architect: Instant project scaffolding with tasks & deliverables via Groq ultra-low-latency inference.
- Commit Analysis: GitHub webhook integration uses Groq to summarize architectural impact of commits.
Zync utilizes Yjs (a high-performance CRDT implementation) and WebSockets to keep documents and boards in sync across collaborators in real time without merge conflicts.
Don't duplicate your work. Zync features a built-in Kanban board that bidirectionally syncs with GitHub Issues and Projects. Move a card in Zync, and watch the issue update on GitHub.
Stop context-switching to Slack or Discord. Zync features low-latency WebSockets communication embedded directly into your workspace, allowing teams to chat contextually right next to the canvas they are editing.
| Feature | Zync | Notion | Miro |
|---|---|---|---|
| Open Source | 🟢 Yes | 🔴 No | 🔴 No |
| Self-Hostable | 🟢 Yes | 🔴 No | 🔴 No |
| Local-First & Offline | 🟢 Yes | 🔴 No | 🟡 Limited |
| Native AI Workflows | 🟢 Deeply Integrated | 🟡 Paid Add-on | 🟡 Paid Add-on |
| Edgeless Canvas + Docs | 🟢 Fully Merged | 🔴 Docs Only | 🔴 Canvas Only |
| GitHub Bidirectional Sync | 🟢 Yes | 🟡 Third-party | 🔴 No |
Zync is built using enterprise-grade, modern open-source tools:
- Frontend: A blazing fast Single Page Application built with React, Vite, and TailwindCSS. State is managed via React Query and Jotai.
- Real-Time Engine: Built on Yjs for conflict-free replicated data types (CRDTs), ensuring all clients stay perfectly in sync. Socket.IO handles the bidirectional transport layer.
- Backend: A robust Node.js/Express API that handles authentication, REST endpoints, and orchestration.
- Database Layer: Prisma handles complex relational data, while MongoDB (Mongoose) manages unstructured document data. Redis acts as our high-performance pub/sub and caching layer.
- AI Engine: Kilo Code Gateway (architecture agent chat) + Groq SDK (project scaffolding & commit analysis).
Getting Zync running locally takes less than 30 seconds thanks to our automated workspace hooks.
Setting up Zync locally is completely frictionless. Our postinstall hooks handle the backend dependencies automatically.
# 1. Clone the repository
git clone https://github.com/zync-meet/Zync.git
cd Zync
# 2. Install ALL dependencies (Frontend & Backend via postinstall)
npm install
# 3. Setup Environment Variables
cp .env.example .env
cp backend/.env.example backend/.env
# 4. Start the Application
npm run devThe Frontend will be running at http://localhost:8081 | The Backend API will be running at http://localhost:5000
Take full control of your data. Zync is designed to be easily deployed on your own infrastructure.
Zync includes out-of-the-box configuration files for one-click deployments:
- Frontend: Deploy instantly via
vercel.jsonon Vercel. - Backend: Deploy as a Web Service via
render.yamlon Render.
For enterprise scale, we provide complete Terraform scripts to provision a highly-available Zync cluster on Oracle Cloud Infrastructure (OCI). See our Oracle VM Setup Guide.
Zync stands on the shoulders of open-source giants. We extend our deepest gratitude to:
- Yjs: The fundamental CRDT engine powering our real-time state management.
- React & Vite: For a blazing fast, component-driven frontend.
- Socket.IO: Enabling low-latency, bidirectional communication.
- Prisma & MongoDB: Our robust database ORM and storage layer.
Dive deeper into Zync's internals by exploring our comprehensive documentation in the docs/ folder:
Architecture & Design
- 🏛️ Master Architecture & System Design
- 🏗️ Tech Stack Overview
- 🧠 AI Project Architect
- 🔒 Security & Auth Architecture
- ⚡️ Performance Strategy
Guides & Audits
- Hyper-fused Markdown + Canvas Editor
- Real-time CRDT Sync
- Kilo Gateway Architecture Agent
- GitHub Kanban Bidirectional Sync
- Desktop App (Electron/Tauri)
- End-to-End Encryption (E2EE) for Workspaces
- Plugin System for Custom AI Agents
- Mobile App (React Native)
Zync is proudly built and maintained by:
 |
 |
 |
 |
|---|---|---|---|
| Lakshya Chitkul | Prem Sai Kota | Eeshitha Gone | Thanmayee Reddy Kotha |
We are building a vibrant, open-source community and we'd love for you to join us! Whether you are fixing a typo, optimizing a query, or building a massive new feature, all contributions are celebrated.
- Read our Contributing Guide to understand our workflow.
- Review our Contribution Workflow.
- Check out our Issues Board and look for issues labeled
good first issue. - Connect with us on LinkedIn, reach out via email at consolemaster.app@gmail.com, or start a GitHub Discussion to get help.
See also: Code of Conduct · Security Policy · Governance · Changelog
Zync is open-source software licensed under the GNU Affero General Public License v3.0 (AGPL-3.0).
What that means: AGPL is a strong copyleft license. If you run a modified Zync backend as a network service (even your own instance), you must make your modified source code available to the users of that service under AGPL. This protects the project from closed-source forks while still allowing self-hosting.