Repository navigation
en enterprise service scope
Enterprise Support focuses on LangBot Core itself. It provides triage and guidance through a single ticket channel, not managed operations or custom development.
| Included | Not included |
|---|---|
| LangBot Core defect assessment and triage | Deployment, operations, 24/7 coverage, on-site service |
| Official documentation guidance | Troubleshooting your network, database, Kubernetes or model providers |
| Upgrade compatibility advice | Maintenance of plugins, third-party adapters or private-protocol clients |
| Public release information and security advisories | Custom development, historical data migration |
| Ticket intake and triage | Recovery SLAs, fixed resolution deadlines, compliance certification |
Custom work is outside the subscription and generally not accepted. Requests with broad value can be proposed on the public roadmap.
Both plans commit to a first human response within 2 business days. A first response means a person has confirmed the scope, requested more information, or given an initial classification. Automated emails don't count.
Warning
A first response is not a fix or recovery. Resolution depends on severity, reproducibility, and whether the issue belongs to LangBot Core.
- Hours: 09:00–18:00 Beijing time on mainland China business days, including make-up working days; public holidays are skipped.
- Counting: requests submitted during hours are counted from submission; requests outside hours start at 09:00 on the next business day.
- Example: submitted Friday 14:00 → response by Tuesday 14:00. Submitted Friday 20:00 → response by Wednesday 09:00.
- Support covers the current stable release of LangBot Core. For older versions we first recommend upgrading, and confirming a defect may require reproducing it on the current release.
- No backports, LTS branches or private patches.
- Plugins and third-party components are outside Core maintenance.
| Enterprise Support | Enterprise Assurance | |
|---|---|---|
| Annual usage review (60 min) | 1 | 1 |
| Remote technical consultation (60 min, by appointment) | — | 4 |
Unused sessions don't roll over. Enterprise Support covers ticket triage, documentation guidance and defect confirmation, not ongoing remote troubleshooting of your environment.
- Assurance covers 1 registered production instance. Registration only defines support scope; it doesn't limit deployments permitted by Apache 2.0 and requires no license key or telemetry.
- We record version, deployment overview, purpose and contacts. Update the registration through a ticket when you replace the instance.
- Quarterly digests are based on public release and security information.
- Critical security notices are based on advisories confirmed by the maintainers; we don't determine whether your environment is affected.
- The annual status summary (Assurance) is based on your registered version and public information. It is not a security audit, penetration test or compliance certification.
- One ticket per issue; duplicates may be merged.
- The priority fix queue has no fixed deadline, and priority roadmap review is not a development or scheduling commitment.
- Support runs through tickets only, not one-to-one group chats.
Language, contacts, service dates and the applicable version of this document are set in the contract. After expiry no new requests are accepted; open tickets are triaged or handed over as agreed. You can keep using open-source LangBot after expiry.
Automatically synchronized from langbot-app/langbot-docs.
简体中文
指南
开发者
- 插件开发
- 插件 SDK API
- 核心开发
文章
- 浏览
- 产品动态
- 在线体验
- 技术解析
- 教程与集成
- 公告
API 参考
- Service API
English
Guides
- Quick Start
- Installation
-
Configure Bots
- Bots
- Discord
- Telegram
- Slack
- Mattermost
- LINE
- Web Page Bot
- HTTP Bot
- KOOK
- Feishu
- DingTalk
- WeChat Official Account
- QQ (OneBot v11)
- Satori (QQ & Multi-Platform)
- QQ Official Bot
- WeCom (Enterprise WeChat)
- AI Configuration
- Advanced Operations
- Using Plugins
- Enterprise support
Developers
-
Plugin Development
- Plugin Development Tutorial
- Completing Plugin Configuration Information
- Plugin Directory Structure
- Component Development
- Code Style Guide
- Certified plugins and shared runtime
- Publish Plugin
- Migration Guide
- Plugin SDK API
- Core Development
Articles
- Browse
- Product Updates
- Engineering
-
Tutorials & Integrations
- LangTARS: Open-Source AI Agent for Remote PC Control — Works with Dify, n8n & 10+ Messaging Platforms
- How to Connect DeepSeek R1 to WeChat, Discord & Telegram in 5 Minutes (FREE)
- Deploy Your Own AI Bot to Discord, Telegram & WeChat in 5 Minutes
- Finally Got My Dify Agent Working in Discord, Telegram and Slack
- How I Built a Multi-Platform AI Bot with Langflow's Drag-and-Drop Workflows
- How I Built a Multi-Platform AI Chatbot with n8n and LangBot
- LangBot 4.6.0 External Knowledge Base Tutorial: Integrating Dify with LangBot for RAG-powered Conversations
- Announcements
API Reference
- Service API
Other pages
日本語
ガイド
開発者
- プラグイン開発
- プラグイン SDK API
- コア開発
記事
- 一覧
- 製品アップデート
- エンジニアリング
-
チュートリアルと連携
- LangTARS:Dify・n8n と連携するオープンソース PC 操作 Agent
- DeepSeek R1 を WeChat・Discord・Telegram に5分で接続する方法
- AI Bot を Discord・Telegram・WeChat に5分でデプロイ
- Dify Agent を Discord・Telegram・Slack で動かす
- Langflow のドラッグ&ドロップでマルチプラットフォーム AI Bot を構築
- n8n と LangBot でマルチプラットフォーム AI Chatbot を構築
- LangBot 4.6.0 外部ナレッジベース入門:Dify と連携した RAG 会話
- お知らせ
API リファレンス
- Service API