EdgeChat is an open-source, self-hosted team chat system that runs on Cloudflare's serverless platform, built for teams, projects, and small communities that want their own chat space without operating a dedicated server.

What it is

EdgeChat is a team chat application built on Cloudflare. The frontend uses Vue 3, Vue Router, and Vite, and the backend runs on Cloudflare Workers with Hono. Realtime messaging is handled by Durable Objects with WebSocket Hibernation, the database is Cloudflare D1, session storage is Cloudflare KV, and file storage is Cloudflare R2. Build and deployment go through Wrangler and GitHub Actions. It is written in JavaScript and licensed under GPL-3.0.

The concrete problem it solves is the cost of ownership that usually comes with self-hosted chat. Instead of running and maintaining a dedicated always-on server, a database, and a runtime environment, EdgeChat deploys the application and its data resources inside the operator's own Cloudflare account, with GitHub Actions handling automatic deployment and updates. In that sense it replaces the conventional self-hosted chat stack with a serverless one, while still offering public and private groups, one-to-one direct messages, voice and file sharing, and an admin console.

Key capabilities

• Realtime group and direct messaging: public groups, private groups, and one-to-one private messages, with realtime delivery, history pagination, message replies, quote jump, @ mentions, and reply reminders.
• Telegram bidirectional bridge: an administrator binds an EdgeChat group to a Telegram group, and a Telegram Bot forwards messages in both directions, including voice messages, so each side keeps its own chat entry point.
• Server-side encryption at rest using AES-256-GCM for newly written message bodies and newly uploaded attachments, with key management and rotation handled through versioned Worker Secrets and the EDGECHAT_ENCRYPTION_KEYRING JSON keyring.
• Voice messages with recording, waveform progress, and variable-speed playback, plus file upload, avatar management, and basic accessibility support.
• Admin console covering a dashboard, user management, registration invites, and site settings, including permanent bans and temporary bans measured in days, hours, or minutes that restore automatically on expiry.
• WebMCP site tools that expose login, session query, and message read and send to compatible client environments.
• In-browser comparison against the source repository to check whether the current deployment is up to date, and scheduled hard deletion of expired messages.

Who uses it and how

• Teams, projects, and small communities that want an independent chat space but do not want to maintain an always-on server, deploying and updating through the Deploy Worker workflow or by pushing to master or main.
• Communities that already run a Telegram group and want a separate web chat entry point, binding the two through the Bot bridge so both entries carry the same discussion.
• Android users through the capacitor/ client, packaged as com.aozorae.edgechat.web, which embeds the Vue Web UI and uses Kotlin for system file selection, notifications, microphone permission, notification session jump, and external links.
• Operators who need invite-based registration, permanent and temporary bans, and a dashboard for user and site management.

Getting started

The recommended path is GitHub Actions auto deployment: run the Deploy Worker workflow manually or push code to the master or main branch, using .github/workflows/deploy-worker.yml. Manual deployment and Docker are documented in the deployment guide and DOCKER.md.

How it compares

The facts name no comparable chat products, paid or otherwise. EdgeChat stands alone in this registry, described only by its own README, topics, and homepage.

When to use it — and when not to

A self-hoster must operate Cloudflare Workers, Durable Objects, D1, KV, R2, Worker Secrets, and the GitHub Actions workflows that manage deployment and encryption keys. Teams that require end-to-end encryption should not pick it: encryption is server-side only, so the Worker decrypts content after session permission checks, and both the Cloudflare runtime and the deployer holding the keys must be trusted. Historical plaintext data is not encrypted retroactively, and enabling the Telegram bridge sends forwarded messages into the corresponding Telegram conversation, so data ownership is bounded by those two facts.

{"activeKeyId":"v1","keys":{"v1":"BASE64_ENCODED_32_BYTE_KEY"}}

# 获取源码
git clone https://github.com/aozorae/Edgechat.git
cd Edgechat

# 安装依赖
npm install

# 启动纯前端演示，无需先部署云端资源
npm run dev:demo

# 前端开发
npm run dev:frontend

# 本地构建
npm run build

# 本地手动发布
npm run deploy

# 独立构建演示站
npm run build:demo

# 部署独立演示 Worker
npm run deploy:demo

$env:CLOUDFLARE_API_TOKEN = "your-token"
npm run deploy

Edgechat/
├─ assets/previews/       # 界面预览
├─ frontend/             # Vue 前端与浏览器内演示
├─ worker/
│  ├─ schema.sql         # 数据库结构
│  ├─ migrations/        # 数据库迁移
│  └─ src/               # API、认证与 Durable Objects
├─ capacitor/            # 基于 Web UI 的 Android 客户端
├─ android/              # 暂时保留的原生 Android 客户端
├─ .github/workflows/    # 自动部署与 CI
├─ wrangler.toml
├─ wrangler.demo.toml
├─ package.json
├─ README.md
├─ README.en.md
├─ README.ja.md
└─ LICENSE