Colanode

Key features

• Local-first sync with CRDT editing Work stays usable offline and converges across editors: changes save to the local device first, sync in the background, and multi-player edits are coordinated with CRDTs.[1]

• Real-time chat with individuals and channels Coordinate without leaving the workspace: message individuals or channels in real time next to the pages and databases the conversation is about.[1]

• Rich-text pages, wikis, and notes Write documents, wikis, and notes in an editor the vendor presents as similar to Notion, keeping team knowledge beside chat instead of in a second product.[1]

• Databases with table, kanban, and calendar views Track structured work with custom fields and dynamic table, kanban, and calendar views, covering lightweight project tracking inside the same workspace.[1]

• File management inside shared workspaces Keep attachments with the work they belong to: store, share, and manage files inside secure workspaces rather than a separate drive.[1]

• Managed cloud with flat-rate tiers Start free on the Seed tier with 10 GB storage, then move through Forge, Scale, and Titan at $20, $100, and $500 per month with larger storage and file limits; every tier includes all features and unlimited users.[1]

• Self-hosting on your own infrastructure Host anywhere on Docker Compose or Kubernetes with Postgres plus pgvector, Redis or Valkey, and filesystem, S3-compatible, Google Cloud, or Azure Blob storage, from single-server to distributed setups.[1]

• Desktop and web clients Work from installed apps or the browser: the company ships desktop and web clients with published downloads and a hosted app.[1]

Who will love it

• Privacy-conscious small and mid-size teams: one workspace covers chat, docs, databases, and files with a self-host option and flat-rate cloud tiers that do not charge per seat.[1][2]

• Self-hosters consolidating tools: teams currently paying for both a chat app and a docs-and-database app can run those substitutable workflows in one system they control.[1][2]

• Teams that value offline-capable work: local-first saves and background sync suit people who work across flaky networks or want their data on their own devices first.[1]

Who should avoid it

• Adopters needing evidence of active maintenance should check current activity first: repository metadata observed October 9, 2026 shows the last push in April 2026, about six months before this review, with 47 open issues.[1]

• Enterprises needing compliance controls: no SSO support, support SLA, or data-residency documentation was observed in the researched official pages, and enterprise deployments are quote-based without published terms.[1][2]

• Teams needing a public API or native mobile apps: no documented public API was observed in the researched sources, and the shipped clients are desktop and web.[1][2]

Alternatives and compatibility