HN Showcase
Back to browse
GitHub Repository

OneCamp: self-hosted all-in-one workspace (chat, tasks, video calls, docs, calendar & AI)

54 starsTypeScript

OneCamp – Self-Hosted Slack/Asana/Zoom/Notion Alternative

by akashc777·Mar 1, 2026·2 points·2 comments
Visit ProjectView on HN

AI Analysis

●MidShip It

All-in-one collaboration stack, but backend's closed-source and launches in 6 days.

Strengths
  • •Hocuspocus+Yjs+Tiptap handles real-time edits over WebSockets with Redis caching
  • •LiveKit SFU + Deepgram auto-transcription pipes live captions into WebRTC calls
  • •Polyglot storage (Postgres+Dgraph+OpenSearch) addresses real architectural complexity
Weaknesses
  • •Backend remains closed-source despite open-source marketing; pay $9 for 'lifetime license'
  • •No proof of concept—frontend only, can't run without closed Go backend; vaporware until March 7
Target Audience

Self-hosting enthusiasts, small teams, DevOps engineers

Similar To

Slack · Notion · Asana

Post Description

Launching in 6 days (March 7)!

We wanted OneCamp to be a masterclass in modern architecture, so we open-sourced our entire Next.js frontend.

Here's the tech stack powering it:

1/ Collaboration & CRDTs Custom Node microservice with Hocuspocus + Yjs for real-time Tiptap edits over WebSockets. Redis caching + JSON/HTML transform to Go backend.

2/ WebRTC & Real-time AI Self-hosted LiveKit SFU + custom Python agent that pipes audio to Deepgram nova-2, rebases timestamps, and broadcasts live transcripts.

3/ Polyglot Persistence Postgres + Dgraph (graph relations) + OpenSearch (full-text search).

4/ Observability OpenTelemetry traces/logs to self-hosted HyperDX on ClickHouse.

The frontend (Next.js + React) is 100% open source (MIT). Dive in, star it, fork it: https://github.com/OneMana-Soft/OneCamp-fe

Backend remains closed-source for now (Go + paid managed option at launch).

Feedback, issues, PRs very welcome!

Similar Projects

Developer Tools●●Solid

CasperAI – A local MCP server for cross-platform engineering context

It stitches Slack threads, PRs, tickets and docs into a local "context lake" and can point a mention like handlePayment() straight to the file and related PRs — very practical for debugging and postmortems. The use of SQLite FTS5 for local full-text search plus MCP for a unified context layer is a smart, pragmatic combo; success will hinge on connector reliability and search/ranking quality, not the README.

Niche GemSolve My Problem
chose166
113mo ago