At a Glance:
Colanode is an open-source, local-first collaboration workspace with self-hostable server support, combining real-time messaging, rich-text pages, customizable databases with table, kanban, and calendar views, and file management into a single platform.
Overview:
Colanode is an all-in-one collaboration workspace designed with a local-first architecture for data privacy and control. The platform combines real-time chat, rich-text pages similar to Notion, customizable databases with dynamic views, and file management. It consists of a client app (web or desktop) that connects to a self-hosted server where data is stored. All changes are saved to a local SQLite database first and then synced to the server, enabling offline work with a background synchronization process. The system handles real-time concurrent editing on pages and database records using Conflict-free Replicated Data Types (CRDTs) powered by Yjs, while messaging and file operations use simpler database tables. Users can connect to multiple servers from a single client, each containing separate workspaces for different projects or teams. Self-hosting requires Postgres with pgvector, Redis, and a storage backend configurable for local filesystem, S3-compatible, Google Cloud Storage, or Azure Blob Storage.
Key Decision Points:
Local-first with offline support: All edits are committed to a local SQLite database before syncing to the server via a background process, allowing continued work during connectivity interruptions.
Self-hosting infrastructure requirements: Deployment requires a Postgres database with the pgvector extension, a Redis-compatible service, a storage backend, and the Colanode server API Docker image.
Concurrent editing scope: Collaborative real-time editing using CRDTs is available for pages and database records, but not for messages or file operations.
Multi-server connectivity: A single client app can connect to and switch between multiple self-hosted or cloud servers, each containing independent workspaces.
Beta web app status: The hosted web app is described as an early preview under testing, with potential bugs or browser compatibility issues.
Core Features:
Real-time chat: Instant messaging within workspaces, using database tables that do not support concurrent edits.
Rich-text pages: Document, wiki, and note creation through an editor similar to Notion, supporting CRDT-based concurrent editing.
Customizable databases: Structured data with custom fields displayed in table, kanban, and calendar views, with collaborative editing via CRDTs.
Local-first data persistence: All changes are written to a local SQLite database first and synchronized to the server in the background.
File management: Store, share, and manage files within workspaces through configurable storage backends.
Use Cases:
Teams seeking a self-hostable collaboration workspace that can operate offline without disrupting local work.
Users who want to combine document editing, structured databases, and team chat within a single platform rather than using separate tools.
Developers or system administrators capable of deploying and maintaining a server stack including Postgres, Redis, and Docker-based services.
Individuals or projects that need to switch between multiple team workspaces across different servers from one client application.
Open-Source Alternative Value:
Colanode provides a self-hostable alternative to centralized collaboration platforms by combining messaging, documentation, and database tools with a local-first synchronization model. The architecture stores all changes locally in SQLite before syncing to the server, which supports offline workflows without depending on continuous connectivity. Source code availability allows teams to deploy the server on their own infrastructure using Docker or Kubernetes, with storage options configurable for local filesystem, S3-compatible, Google Cloud Storage, or Azure Blob Storage backends. Concurrent editing on pages and database records is implemented through open CRDT technology rather than proprietary synchronization mechanisms.
