Open-source · Apache-2.0

Multichannel support.
One workspace.

Receive channel messages, review history, reply and maintain visitor profiles in one workspace. DuDu is open source and self-hosted, for teams managing support across channels.

Interactive illustration · sample data
Unified inbox
WeChat

How can I check my order status?

Received in workspace · illustration
Select a channel to trace a message
Interactive product tour

Explore a complete support conversation.

Open a conversation, send a sample reply and review visitor details. No sign-in required; no connection to real channels.

Start the tour ↗

Support and administration,
with clear responsibilities.

Use Desk for daily support, Console for staff and channel setup, and Admin to provision organizations. MockPulse is optional and used only for development testing.

Focus, parallel and card layouts. Shared conversation history, drafts, visitor tags and internal notes. Browser access and desktop builds.

Explore DuduDesk ↗
Agent workspace: conversations, replies and visitor details
Interface preview with sample data.

Manage employees, groups and channel accounts. Assign conversation access through groups; channel secrets are write-only.

Explore DuduConsole ↗
Interface preview with sample data.

Provision organizations, manage their resources and review operational summaries and activity logs, independently of day-to-day support.

Explore DuduAdmin ↗
Interface preview with sample data.

MockPulse is a local channel callback simulator for validating event payloads, signatures and encryption. It is optional when running the support system.

Explore MockPulse ↗
Current MockPulse event editor: built-in templates, field descriptions and payload editing
Interface preview with sample data.

Conversation continuity

Receive messages in real time, load history on demand and maintain shared visitor profiles. Outbound workspace replies currently support text.

Scoped access

Organization data is isolated. Current group permissions govern access to employees, channels and conversation history.

Source available to inspect

The Java server and React clients are open source, with self-hosting and channel extensibility.

Channel integrations

Connect your channels. Bring conversations together.

13 implemented integrations cover specific messaging interfaces. Configure the accounts your team needs and handle conversations in one workspace.

WeChat ecosystem

WeChat Official AccountsWeChat Mini ProgramsWeCom

Domestic platforms

DingTalkFeishuQQWeiboDouyinXiaohongshuAlipayMeituan

International platforms

TelegramWhatsApp

Messaging capabilities

Plain-text replies are supported; attachment sending is unavailable. Incoming non-text messages and media depend on the channel.

Integration requirements

Obtain channel accounts, complete platform authorization and credential setup, then validate real messaging. Each platform retains its own permissions and rules.

Availability

DuDu is under active development and currently requires building from source and self-hosting. The website tour is simulated, not a live trial.

Channel configuration and integration guide ↗

Deployment, channel integration & testing guides ↗

How do you get started?

DuDu currently requires building from source and self-hosting, with development and operations knowledge. Run the server, configure your organization and channels, then sign in as an agent. Browser access does not require a desktop build.

Complete setup guide ↗
LOCAL DEVELOPMENT ~/dudu

$ git clone https://github.com/Buktal/dudu.git
$ cd dudu
$ docker compose -f dudu-server/compose.yaml up -d --wait
$ cd dudu-server
$ mvn spring-boot:run
  1. Provision an organization and initial administrator in Admin.
  2. Configure employees, groups and channel accounts in Console.
  3. Sign in to Desk and reply within each channel’s permissions.

This is a local development workflow. Replace development credentials and the JWT secret before public deployment.

Open by design.
Built together.

Use, modify, distribute and build commercially under Apache-2.0. Issues, code contributions and documentation improvements are welcome.