Browse / Support and bookkeeping
Tiledesk
MIT live chat plus chatbot design studio, deployed from a docker-compose env file, driven by a REST API.
Tiledesk is an open-source conversational support platform: web widget, agent dashboard, a visual chatbot Design Studio with LLM and knowledge-base steps, and channels for WhatsApp, Messenger, and Telegram. This repo is the deployment bundle (docker-compose and Helm) that wires server, dashboard, design studio, chat21 messaging, and MongoDB together. The Builder publishes a REST API for requests, messages, leads, departments, chatbots, and knowledge bases, and sells hosted and enterprise editions.
- we want a self-hosted chat widget with an AI bot that answers from our docs and escalates to a human, under an MIT license
- we want our agent to open, tag, route, and close conversations through an API while humans work in the dashboard
- Nine services plus MongoDB and Redis; the README says Helm charts are not production-ready as is
- Stars are split across many repos (server, dashboard, design studio); this bundle repo shows 316
- Enterprise Docker images need credentials from info@tiledesk.com
- Hosted plan pricing page returned 404 during analysis
Last activity Sep 1, 2026. Fit: adaptable 3, operable 2.
Editions
Community (self-hosted) · Free open source
- Clone
git clone https://github.com/Tiledesk/tiledesk - ImageContainer
Hosted (tiledesk.com) · Free closed source
- HostedOpen the hosted app
Enterprise (private images) · Free closed source
- ImageContainer
Adaptable: what is yours to change
Make it yours
Config only18 things to edit
docker-compose/docker-compose.yml sets 60+ environment variables per service. An SMB edits JWT_SECRET_KEY, SERVER_BASE_URL, DASHBOARD_URL, WIDGET_LOCATION, REDIS_URL, GPTKEY (LLM key name), VECTOR_STORE_HOST, WEBHOOK_ENABLED, EMAIL_SECTION, SUPPORT_MODE, and PUSH_ENGINE. Chatbot behavior and prompts are authored in Design Studio, not files. Helm charts are a starting template the README says to modify for production.
- Env vars
JWT_SECRET_KEYJWT_KEYSERVER_BASE_URLDASHBOARD_URLWIDGET_LOCATIONREDIS_URLGPTKEYVECTOR_STORE_HOSTVECTOR_STORE_NAMEWEBHOOK_ENABLEDRESTHOOK_ENABLEDEMAIL_SECTIONSUPPORT_MODEPUSH_ENGINEAPPS_ACCESS_TOKEN_SECRETMQTT_APIENDPOINT- Config files
docker-compose/docker-compose.ymlhelm/values.yaml- Prompt files
- none
- Accounts you need
- OpenAI or another LLM provider (for AI steps)Meta or Telegram developer accounts for channels (optional)Tiledesk account for hosted and enterprise editions
Source
- github.com/Tiledesk/tiledesk
- MIT license
- Last commit Sep 1, 2026
- 316 stars
Operable: what an agent can drive
Interface
OfficialAPIpublished by the builderremote or local
How an agent can drive an Operable Listing, in five levels: native (built for the agent as the primary interface), official (the Builder ships an agent interface), wrapped (a third party wraps the software's API), config (an agent can only drive it by editing files), gui (screen control only). An interface is official only when it is published by the same organization that ships the software. GUI-level Listings are allowed and sorted last.
Reach
Partial coverage. 6 of 10 jobs reachable through the stated interface.
| Job | Through the interface | Evidence |
|---|---|---|
| Create and list support requests (conversations) | Reachable | Requests API: POST create with first text, language, source page; list with filters by status, department, lead, channel, tags |
| Route, assign, and follow requests | Reachable | Requests API: route to department, add/set/remove participants and followers |
| Close and reopen requests | Reachable | Requests API: close (status 1000), reopen (status 100) |
| Send messages into a conversation | Reachable | Messages section in the REST API index; Requests API returns participants and messages |
| Tag requests and add internal notes | Reachable | Requests API: tags, custom attributes, notes add/update/delete |
| Manage leads and departments | Reachable | Leads and Departments sections in the REST API index |
| Design chatbot flows | Undetermined | Chatbots section exists in the API index; whether flows can be authored through API versus imported JSON not verified |
| Load knowledge bases for AI answers | Undetermined | Knowledge Bases section in the API index; operations not verified |
| Connect WhatsApp, Messenger, Telegram | Not reachable | channel apps are configured through the dashboard Apps panel |
| Analytics and CSAT reporting | Not reachable | ratings are on requests; no analytics section in the API index |
Code stack
- Languages
- JavaScriptTypeScript
- Frameworks
- Node.jsExpressAngular (dashboard)Ionic (chat21)
- Package manager
- npm
- Database
- MongoDBRedis
- Hosting target
- Docker ComposeKubernetes (Helm)
- Built
- Human-written (recorded, never ranked)
Model stack
- Providers
- OpenAI (GPTKEY)other LLMs through tilellm
- Models
- none
- Keys you need
GPTKEY- Prompts live in
Design Studio (UI)
Evidence and confidence
| Field | Where it was seen | Confidence |
|---|---|---|
| formFactor | README: Docker Compose or Kubernetes deployment of server, dashboard, design studio, chat21, MongoDB | 95% |
| executionModel | GPTKEY and vector store variables in docker-compose.yml; Design Studio LLM steps | 85% |
| operability | developer.tiledesk.com REST API index: Requests, Messages, Leads, Departments, Chatbots, Knowledge Bases, JWT | 90% |
| effort | docker-compose/docker-compose.yml environment blocks list named variables | 85% |
| editions | README: Enterprise credentials for private images; tiledesk.com hosted | 60% |
| active | gh api: pushed 2026-09-01; dashboard repo pushed 2026-09-02 | – |
| reach | 75% |
Open questions
- Hosted and enterprise pricing
- Whether chatbot flows and knowledge bases can be created through the API
Sources
- github.com/Tiledesk/tiledesk sourcing:support-bookkeeping:curated
- developer.tiledesk.com/ sourcing:support-bookkeeping:curated
- developer.tiledesk.com/apis/rest-api/requests.md analysis