Tiledesk-server provides the backend API for Tiledesk, an open-source live chat and customer service platform. It enables the creation of advanced LLM-powered conversational agents with optional human-in-the-loop capabilities, targeting developers and businesses seeking a customizable customer support solution.

How It Works

Built with Node.js and Express, Tiledesk-server acts as the core engine for managing multi-channel customer interactions. It supports a native chatbot technology that allows for channel-agnostic response design, automatically adapting rich content like images and buttons to platforms such as WhatsApp, Facebook Messenger, and Telegram. The platform facilitates integration with external applications via APIs and webhooks, enabling the deployment of visual applications within conversations.

Quick Start & Requirements

• Docker Compose: docker-compose up (after configuring .env from .env.sample)
• Local Install: npm install -g @tiledesk/tiledesk-server, mongodb-runner start, tiledesk-server (requires Node.js 12.20.2+, npm 6.14.11+, MongoDB)
• Source Install: git clone, npm install, npm start
• Documentation: https://developer.tiledesk.com

Highlighted Details

• Open-source alternative to platforms like Voiceflow for building LLM agents.
• Multi-channel support with adaptive rich content rendering.
• Extensible via REST APIs and webhooks for custom integrations.
• Includes native chatbot technology for automated conversations.

Maintenance & Community

• Active development with community support available via Discord.
• REST API documentation is accessible.
• Guidance provided for upgrading the server.

Licensing & Compatibility

• The README does not explicitly state a license. Compatibility for commercial use or closed-source linking is not specified.

Limitations & Caveats

The project requires specific, older versions of Node.js (12.20.2) and npm (6.14.11) for local installation, which may pose compatibility challenges with modern development environments. The license is not clearly stated in the README, potentially impacting commercial adoption.