安全Security
边界在企业手里，
不在厂商手里Your boundary stays with you, not with the vendor
ECode 只做私有部署。身份、密钥、额度和日志都存放在企业自己的机器上，由企业自己的管理员掌握。
ECode is private deployment only. Identity, keys, quotas and logs live on your own machines, held by your own admins.
设计原则Design principles
-
私有部署Private by design
控制台和模型网关由企业自己部署，在本地主机或企业自己的云上。
You deploy the Console and the model gateway, on a local box or in your own cloud.
-
不向厂商回传No vendor egress
客户端的模型请求只发往企业自己的网关。安装包在打包时做出站扫描。
The client sends model requests only to your own gateway. Every installer is scanned for outbound addresses when it is built.
-
每人独立密钥An individual key for everyone
每位员工一把只属于自己的网关密钥。停用员工后，网关立即封禁这把密钥。
Each employee has a gateway key of their own. Disable the employee and the gateway blocks it at once.
-
凭据按企业隔离Credentials isolated per enterprise
每个企业的凭据相互隔离。一个登录会话只属于一个控制台，切换企业前客户端先退出登录。
Each enterprise's credentials stay apart. A session belongs to one Console, and the client signs out before it switches.
-
官方内容签名Signed official content
官方内容使用 Ed25519 签名。
Official content is signed with Ed25519.
-
企业单点登录Enterprise single sign-on
员工只能用企业账号登录，经企业身份源认证。邮箱域名白名单控制谁能进入。
Employees sign in only with enterprise accounts, through your identity provider. An email domain allowlist decides who gets in.
数据在哪里Where your data lives
| 数据Data | 存放位置Where it is kept |
|---|---|
| 员工、管理员、SSO 设置、下载密钥、审计日志Employees, admins, SSO settings, download keys, audit log | 控制台数据库，在企业自己的机器上The Console database, on your machine |
| 员工网关账号、密钥、额度、调用记录Gateway accounts, keys, quotas, call records | 网关数据库，在企业自己的机器上。调用记录不含对话内容。The gateway database, on your machine. Call records hold no message content. |
| 本地模型的推理Local model inference | 企业自己的 GPU 主机。代码和对话不出企业网络。Your own GPU box. Code and conversations stay inside your network. |
| 云端模型的请求Cloud model requests | 经企业网关，发往企业自己配置的云端供应商。供应商密钥只存在网关里，不再显示。Through your gateway to the cloud provider you configured. Provider keys live only in the gateway and are never shown again. |
| 员工电脑上的数据Data on employee computers | ~/.ecode 和项目里的 .ecode/~/.ecode and the project's .ecode/ |
企业码查找是唯一会访问 ECode 公共服务的连接步骤：客户端用企业码在 ECode 企业目录里查到控制台地址，记录里只有企业码、企业名称、控制台地址和更新时间。员工直接输入控制台地址或使用一键连接链接时，不访问企业目录。
Looking up an enterprise code is the one connect step that touches a public ECode service: the client reads the Console address from the ECode enterprise directory, whose records hold only the code, the enterprise name, the Console address and an update time. Employees who enter the Console URL or use a one-click link skip the directory entirely.
可追溯的管理Accountable administration
- 审计日志Audit log登录、SSO 变更、密钥签发、员工停用、额度修改（含前后值）、模型启停都有记录。Sign-ins, SSO changes, key issuance, disabled employees, quota changes with before and after values, and model starts and stops are all recorded.
- 请求日志不含内容A request log without content只记录时间、员工、模型、token、花费、状态和耗时。控制台不开启内容记录。It records time, employee, model, tokens, spend, status and latency. The Console never turns on content logging.
- 定期对账Regular reconciliation控制台每 300 秒与网关对账，网关恢复后补上停用操作。The Console reconciles with the gateway every 300 seconds and applies pending disables when the gateway is back.
1.0 的已知限制Known limits in 1.0
我们如实列出和安全相关的限制，以及当前的做法。
Here are the security-related limits, stated plainly, with what to do today.
| 限制Limit | 当前做法What to do |
|---|---|
| 安装包还没有代码签名，首次打开会被系统拦截Installers are not code-signed yet, so the system blocks the first launch | 先核对 SHA256，再按步骤放行一次。见首次打开。Check the SHA256, then allow the app once. See First launch. |
| 插件和技能随客户端内置，新增或更新要发新客户端Plugins and skills ship inside the client; adding or updating one needs a new client | 1.1 起，插件和技能经签名通道更新。From 1.1, plugins and skills update through a signed channel. |
| 一台电脑的一个系统账户只应给一名员工用One OS account on a computer should serve one employee | 每名员工使用自己的系统账户。Give every employee their own OS account. |
需要安全评审材料？Need material for a security review?
发布说明和管理员手册列出了组件、数据和限制。也可以直接联系我们。
The release notes and admin guide cover components, data and limits. Or talk to us directly.