Chat
Channels and direct messages for the conversations that move work along.
- Threads and reactions
- Typing indicators over WebSockets
- Edit and delete your messages
Self-hosted team workspace
Keep the work in view.
Cohesa puts team chat, issues, collaborative documents and search in one application, backed by one database. Mention #COH-142 in a channel and the issue shows up right there, status and all.
Modules
The everyday tools,
The everyday tools,
in one place.
Each module is a working part of the same application: one sign-in, one workspace, one search across everything.
Issues
Projects with keyed issues, from backlog to done, in a list or on a board.
- Status, priority and labels
- Parent issues and relations
- Filters that stay out of the way
Documents
A rich-text editor where several people write at once, organised in a nested tree.
- Real-time co-editing (Yjs)
- Live collaborator cursors
- Breadcrumbs and document tree
Search
One command palette for messages, issues, documents, channels and people.
- Opens from anywhere with ⌘K
- Results keep their source and context
- Powered by Meilisearch
Handbook
Team docs rendered inside the app, each one showing how fresh it is.
- Freshness badges per document
- Live blocks with board and commit data
- Safe link handling
Identity
Sign-in through a bundled OpenID Connect provider, with workspaces and invitations.
- OIDC via Zitadel
- Invite members, switch workspaces
- Notifications in one inbox
Connected work
One database.
One database.
Fewer lost decisions.
A conversation, an issue and a document usually tell parts of the same story. In Cohesa they live in the same PostgreSQL database, so a reference is a real link, not a pasted URL.
Write #COH-142, issue:COH-142 or a document reference in a message and Cohesa resolves it to a chip with the current title and status. References you can't access, or that no longer exist, show up as broken instead of leaking.
Self-host
Your machine.
Your machine.
Your data.
Cohesa runs as a Docker Compose stack you control: a SvelteKit web app, a TypeScript API layer and a Rust service over PostgreSQL, with Meilisearch, MinIO and Zitadel alongside.
- Bootstrap the stack
make bootstrapstarts the services, migrates and seeds the database, and provisions sign-in. Safe to re-run. - Check it
make doctorverifies tools, configuration, containers and migrations in one pass. - Start the apps
pnpm dev, then openlocalhost:5173and sign in as a seeded demo user.
$ make bootstrap $ make doctor Cohesa doctor ── Prerequisites ─────────────────── ✓ docker found ✓ pnpm found ✓ node found ── Infra containers ──────────────── ✓ postgres running (healthy) ✓ meilisearch running (healthy) ✓ minio running (healthy) ✓ zitadel running (healthy) ── Database ──────────────────────── ✓ migrations applied ──────────────────────────────────── ✓ All checks passed $ pnpm dev # web on :5173
Status
Where Cohesa
Where Cohesa
stands today.
Cohesa is in active development. It runs well as a local self-hosted stack; there is no hosted sign-up, and the source is not yet public.
The core workspace
Chat, issues, documents, search, the handbook and notifications, with OIDC sign-in, on a local Compose stack with backup and restore.
Selected-project view
A native suite mode can show one project's context from explicitly granted sources. In that mode the chat, issues and documents routes are not available yet.
Mail, calendar and calls
Email, calendar and video are on the roadmap for a later phase. They are not part of Cohesa today.
A clearer place
to follow the work.
Follow along on the project page for the changelog and release notes while Cohesa moves toward a public release.