Conversation Console
Conversations
Review complete conversations by employee and customer, with historical message loading and automatic refresh.
Open demo →PRODUCT SHOWCASE
A working archive and review system
Conversation review, global search, media management and audit logs have shipped. Explore them in a static demo using fictional data.
Conversation Console
Message Search
Search
Combine employee, customer, keyword, time and message-type filters, then return to the original conversation context.
Open demo →Media Management
Media management
Controlled access to images, voice, video and files, usage measurement and approval for full exports.
Open demo →Audit Logs
Audit logs
Trace who viewed or exported what, and when.
Open demo →FEATURES
From data ingestion to everyday review
Every capability listed here is backed by shipped code and documentation. Planned features are not included.
Conversation archiving
Conversation Archiving
Continuously retrieve and decrypt WeCom messages within the archive scope lawfully enabled and authorized by the organization: text, images, voice, video, files, composite messages and recalled messages.
Search and review
Search & Review
Combine employee, customer, keyword, time and message-type filters and return to the full chat context. Chinese and English interfaces and message reachability diagnostics are supported.
Media management
Media Management
A unified media storage abstraction, including Qiniu Kodo, with controlled signed-URL access. Text exports and full media ZIP exports require a second confirmation by the Owner.
Access control
Access Control
The server resolves the signed-in identity and tenant, rather than trusting browser-supplied fields. Includes RBAC, multi-organization management and account lifecycle controls.
Audit and governance
Audit & Governance
Tenant-level audit logs, export approvals and retention policies. Regular employees cannot delete corporate archives; retention and cleanup follow Owner-controlled workflows.
Operational visibility
Operational Visibility
Sync health, diagnostics, usage and storage measurement, and health-check endpoints. Capacity limits explicitly block new writes rather than silently deleting existing records.
Explore conversations, search, contacts, media, capacity and audit logs in the static demo →
HOW IT WORKS
From WeCom to searchable conversations
Data flows only within the archive scope lawfully enabled and authorized by the organization, with explicit boundaries and states at each step.
WeCom API
Enable and authorize the WeCom conversation archive API under the official rules.
Sync & Decryption
Event-driven retrieval with reconciliation fallback; Tencent's proprietary SDK decrypts and normalizes messages.
Secure Storage
PostgreSQL persists messages and metadata; a unified storage abstraction stores media.
Search & Review
Combined search, conversation review, controlled media access and export approval.
Audit & Governance
Role permissions, audit logs, retention and health diagnostics operate throughout.
Dependency: retrieving and decrypting archive messages requires Tencent's proprietary WeCom archive SDK, obtained under Tencent's official rules. API activation and official fees are separate. 本产品为第三方独立产品，与腾讯公司及其企业微信无隶属、合作或授权关系。
OPEN SOURCE
A complete open-source version
Self-hosted. Transparent. Community-driven.
- AGPL-3.0 license — Use, modify and redistribute; modified network services must also make their source available.
- Complete self-hosted version — All shipped capabilities, rather than a feature-limited demo.
- One codebase — Cloud hosting and self-hosting share the same source, with no closed-source enterprise branch.
- Independent deployment — Your data stays on your infrastructure, without depending on Crowntime servers.
- Architecture documentation — Architecture, deployment documentation and architecture decision records (ADRs) are public alongside the source.
- Community contributions — Report issues and contribute changes through GitHub Issues and Pull Requests.
Release status (2026-10):WeCom Archive is publicly released; the first public release is v1.1.0 (2026-10-09). The source, deployment documentation, architecture and contribution guide linked here are directly accessible on GitHub.
Explore on GitHub
Source, documentation, issues and release records are in the repository.
Explore on GitHub ↗DEPLOYMENT OPTIONS
Choose your deployment
Both options share the same code. Start with self-hosting and migrate when needed, or let us handle operations.
Option A · Self-hosted
Self-hosted · Open source
AGPL-3.0 · No software subscription fee
- Complete self-hosted version with all shipped capabilities
- Independent deployment on infrastructure you control
- You provide and operate the infrastructure
- Official WeCom API fees are separate, under Tencent's rules
Option B · Cloud Hosted
Cloud hosted · Operated by us
CNY 99 / year · 5 GiB storage · Unlimited seats
- Managed deployment and operations for easier onboarding
- 15-day free software trial
- Unlimited seats, chat records and searches
- Official WeCom API fees are separate; no permanent free plan
AI ENGINEERING
Built with AI. Engineered for Reliability.
AI-assisted development, with engineering quality backed by evidence. Crowntime is a real example of organizing AI agents through product decisions, architecture constraints, task decomposition, automated tests and human review.
Product visionPRODUCT VISION
The human product owner defines direction, priorities and acceptance criteria.
Architecture and constraintsARCHITECTURE & CONSTRAINTS
ADRs and guard tests enforce layer boundaries, dependency direction and trust boundaries.
Issues and acceptance criteriaISSUES & ACCEPTANCE CRITERIA
Each issue has a defined scope, boundaries and acceptance criteria, with one implementation session and one final commit.
AI agent implementationAGENT IMPLEMENTATION
Development agents work in isolated worktrees under binding engineering rules.
Automated testing and CITESTING & CI
Architecture guards, contract tests and the complete regression suite form the automated gate.
Human reviewHUMAN REVIEW
Humans decide merges, releases and production changes; green CI does not authorize a merge.
Release and feedbackRELEASE & FEEDBACK
Release notes, operations documentation and user feedback inform the next product decisions.
commits
calendar days (35 active development days)
distinct issue IDs
development phases completed by v1.0.0
Historical scope: 2026-06-26 (project creation) to 2026-08-07 (v1.0.0 completion), from the v1.0.0 release notes. These figures do not describe current or future development pace.
Agent Orchestration
Development, QA, operations and research roles have explicit permissions and boundaries in binding rules.
Architecture Governance
Architecture guard tests reject invalid dependencies; ADRs come first.
Quality Gates
Lint, type checks, builds, tests and contract tests are required CI checks.
Production Engineering
Migration gates, health checks, backup and rollback, and upgrade rehearsals support production operations.
FAQ
Frequently asked questions
Is Crowntime open source?
Yes. WeCom Archive is publicly released under AGPL-3.0 as a complete self-hosted version. Source, deployment documentation and the contribution guide are available in the GitHub repository.
Does self-hosting require payment?
No software fee is paid to Crowntime. AGPL-3.0 permits self-hosting and use. You cover servers, databases, operations and official WeCom archive API fees. Cloud hosting is an optional paid service.
Is Tencent's SDK required?
Yes. Retrieving and decrypting archive messages requires Tencent's proprietary SDK, obtained under its official rules. API activation and official fees are separate.
How do self-hosting and cloud hosting differ?
Self-hosting: AGPL-3.0, independent deployment and data on your own infrastructure, operated by you. Cloud hosting: operated by Crowntime, with a 15-day free software trial and an annual CNY 99 plan including 5 GiB and unlimited seats. Both share the same code.
Is multi-tenancy supported?
Yes. Data is isolated by organization, with multi-organization management, RBAC and platform administration. The server resolves identity and tenant rather than trusting browser-supplied fields.
Which message and media types are supported?
Text, images, voice, video, files, composite messages, recalled messages, WeCom group chats and Channels messages. Media supports controlled access and full export, with a second confirmation by the Owner.
How do I start a deployment?
Read the GitHub README and deployment guide, then prepare a server, PostgreSQL, Tencent's archive SDK and WeCom administrator authorization. You can explore the static demo first.
How can I contribute?
Read the contribution guide, report issues and submit Pull Requests. Contributions follow AGPL-3.0 and the repository's issue ownership, branch and required-CI rules.
Can an employer read employee–customer chats?
Authorized users can review communications lawfully enabled and authorized for WeCom archiving. The product cannot read conversations outside that scope or monitor employees' personal WeChat accounts.
Can employees delete archived chats themselves?
Regular employees cannot delete corporate archives in this system. The organization's Owner controls retention and cleanup through configuration and governed workflows.
Get started with Crowntime
Read the source and self-host, or try cloud hosting free for 15 days. Official WeCom API fees are separate.
本产品为第三方独立产品，与腾讯公司及其企业微信无隶属、合作或授权关系。