3 种数据库 · 4 个川序交付包3 Databases · 4 Chuanxu Packages

同一功能核心,选择适合企业环境的数据库One Functional Core, Your Choice of Enterprise Database

川序社区版用一个整合包选择 Oracle、PostgreSQL 或 YashanDB;企业版按三库分别交付。每次部署只选择一个底座。One unified Chuanxu Community package selects Oracle, PostgreSQL or YashanDB. Enterprise remains three database-specific deliveries. Each deployment selects one backend.

v5.0.0

一套数据库实体能力,清晰的产品选择Shared Database Entities, Clear Product Choices

川序社区版与企业版共享基于数据库的身份、任务、协作关卡、属性图、DB4A2A、知识和记忆能力,按部署和治理需求选择交付方式。Chuanxu Community and Enterprise share database-backed Identity, Tasks, collaboration gates, property graphs, DB4A2A, Knowledge and Memory. Choose a delivery that fits your deployment and governance needs.

川序 Chuanxu Community

一个整合包,部署时选择 Oracle、PostgreSQL 或 YashanDB,Apache-2.0。One unified Apache-2.0 package; select Oracle, PostgreSQL or YashanDB at deployment.

川序 Chuanxu Enterprise

Oracle、PostgreSQL、YashanDB 三个独立企业包,BSL-1.1,按商业许可交付。Three separate Oracle, PostgreSQL and YashanDB Enterprise packages under BSL-1.1 and commercial delivery terms.

每个进程固定使用一个底座;切换需重启和独立数据库准备,不会自动迁移数据。产品名不同不代表升级包可以互换。Each process uses one backend. Switching requires restart and a separately prepared database; it does not move data. Different product identities do not make upgrade packages interchangeable.

能力成熟度Capability Maturity

先选择成熟度,再选择数据库和版本Choose Maturity Before Database and Edition

生产配置PRODUCTION PROFILE

当前生产建议Current Production Recommendation

v5.0.1 生产基线在安全域、Embedding Contract、授权知识查询和 Graph Runtime 核心之上,增加可选模型网关、Token 与成本事实以及登录后只读管理大屏,适合生产评估、POC 和受控部署。The v5.0.1 production baseline adds an optional model gateway, Token and cost evidence, and an authenticated read-only executive wallboard to Security Domain governance, Embedding Contracts, authorization-scoped Knowledge queries, and Graph Runtime core for production evaluation, POCs, and controlled deployment.

GRAPH CAPABILITY MATRIX

受控与禁用能力Controlled and Disabled Capabilities

Graph Runtime 核心与授权检查属于稳定生产基线。草稿导入、SLO 只读检查与检查点分叉独立受控;已登记 MCP、A2A、仅元数据遥测和固定隔离框架按各自授权启用。离线回放与迁移预检只分析持久事实,真实副作用回放、运行中迁移、任意框架执行与全局自治保持关闭。Graph Runtime core and authorized inspection remain available. Draft import, read-only SLO views and checkpoint forks are independently controlled. Registered MCP, bounded A2A, metadata-only telemetry and one pinned isolated framework use separate authorization. Offline replay and migration preflight inspect persisted facts; live effect replay, live migration, arbitrary frameworks and global autonomy remain disabled.

社区版与企业版Community vs Enterprise

免费验证核心能力,企业版增加治理控制Validate the Core for Free; Add Governance With Enterprise

能力Capability社区版Community企业版Enterprise
记忆、知识、任务、工作区、技能、分支、协作、LoopMemory, knowledge, tasks, workspaces, Skills, branches, collaboration, Loops✓✓
用户、组织架构与 Agent 注册、归属、数据库会话User, organization, and Agent registration, ownership, and database sessions✓✓
权限驱动 UI、Production Profile、Graph capability matrixPermission-driven UI, Production Profile, Graph capability matrix✓✓
细粒度策略、多方审批、职责分离Fine-grained policy, multi-party approval, separation of duties—✓
风险审计、留存、法律保全、应急控制Risk audit, retention, legal hold, emergency control—✓
企业许可和技术支持Enterprise license and support有限尽力支持Limited best effort按合同By contract

公开 GitHub 仓库仅发布社区版;企业版在客户需求和商业许可确认后提供,当前倾向不公开源码。Only Community editions are published in public GitHub repositories. Enterprise is provided after customer need and commercial licensing are confirmed and is currently intended to remain source-private.

数据库适配Database Adapters

原生能力不同,共同产品契约一致Different Native Capabilities, One Product Contract

Oracle AI Database 26ai

Vector、Oracle Text、Property Graph / SQL PGQ、DBMS_SCHEDULER、数据库原生多租户及成熟高可用与备份生态。Vector, Oracle Text, Property Graph / SQL PGQ, DBMS_SCHEDULER, native multitenancy, and mature HA and backup options.

PostgreSQL 18 + AGE + pgvector

PostgreSQL 18;pgvector、tsvector、Apache AGE、pg_cron 与 RLS 的版本及部署前提需按目标环境核验。当前以关系运行时为权威、AGE 为图投影。其他 PostgreSQL 生态数据库须独立验收。PostgreSQL 18; verify pgvector, tsvector, Apache AGE, pg_cron and RLS versions and deployment prerequisites in the target environment. The relational runtime is authoritative and AGE is the graph projection. Other PostgreSQL ecosystem databases require independent acceptance.

YashanDB 23.5.4+

VECTOR + HNSW、SEARCH INDEX、原生 Property Graph、DBMS_SCHEDULER、LIST 分区、原生 JSON 转换与数据库加密包。VECTOR + HNSW, SEARCH INDEX, native Property Graph, DBMS_SCHEDULER, LIST partitioning, native JSON conversion, and database crypto packages.

PostgreSQL Ecosystem

更多 PostgreSQL 生态数据库选择More Database Choices in the PostgreSQL Ecosystem

IvorySQL、OpenTenBase、Halo DB(羲和数据库)和 PolarDB(PostgreSQL 兼容版)属于 PostgreSQL 生态。生态关联不代表与已验证底座能力相同,也不构成这些产品的部署或升级验收。Oracle、PostgreSQL 与 YashanDB 仍按各自适配器、版本、向量、图、全文检索及部署前提分别验证。IvorySQL, OpenTenBase, Halo DB and PolarDB (PostgreSQL-compatible edition) belong to the PostgreSQL ecosystem. This does not establish equivalent capabilities or deployment/upgrade acceptance. Oracle, PostgreSQL and YashanDB remain separately verified for their adapters, versions, vector, graph, full-text and deployment prerequisites.

选择建议Selection Guide

以现有技术栈、合规与运维能力为先Start With Existing Technology, Compliance, and Operations

Oracle

适合已有 Oracle 技术体系、需要原生多租户与成熟企业运维能力的组织。For organizations with Oracle expertise, native multitenancy, and mature enterprise operations.

PostgreSQL

适合重视开放生态、可控许可成本和灵活组件组合的团队。For teams prioritizing an open ecosystem, controllable licensing cost, and flexible components.

YashanDB

适合国产数据库采购要求和需要本地企业数据库支持的环境。For domestic-database procurement requirements and local enterprise database support.