身份与访问控制
通过网关集中认证，支持用户令牌、服务令牌和用于集成场景的 API 密钥。
- JWT-based user sessions for portal access
- Service-to-service tokens with managed rotation
- API key support for external integrations
- Flexible guards for user, service, and mixed-access endpoints
工作区隔离
代理工作在隔离的云工作区中进行，与客户网络和生产系统分离。
作用域访问
代码库和服务凭据按项目进行作用域限定，并通过加密配置路径存储。
决策溯源
任务、评审、审批和 lane pull request 将对变更及原因保持持久记录。
运营基线
监控、镜像扫描、备份和灾难恢复运行手册构成生产运营模型的一部分。
受控执行环境
自治工作从贵地的本地机器和内部网络之外运行，运行时隔离是首要设计目标。
- Cloud workspaces isolate task execution from customer infrastructure
- Ephemeral execution architecture is the target for untrusted command isolation
- Runtime workspaces are separated by project and organisation boundaries
- Merge gates keep production changes behind explicit policy
数据保护
Coroid 以数据库为先，敏感配置默认加密，并符合公共云服务在 EU 的托管要求。
- Encryption for data in transit and at rest
- Encrypted storage for sensitive configuration values
- EU hosting profile for GDPR-sensitive teams
- Scoped repository access instead of broad organisation-wide credentials
生产运维
该平台以企业工程团队所期望的监控、扫描和灾难恢复实践进行运营。
- SBOM and container image scanning in CI
- HTTPS-only public endpoints with TLS termination
- Automated database snapshots and restore runbooks
- Prometheus, Grafana, Loki, and GlitchTip-backed observability
可审计的交付记录
Coroid 设计旨在向语言工程领导、评审和安全团队解释自治变更。
Specifications, agent activity, reviews, and approval decisions stay connected
Lane pull request history shows the final evidence before code is merged
Security, dependency, coverage, visual, E2E, and browser-test evidence can be attached to reviews
SOC 2 is a readiness target, not a current certification
企业级评审
将安全性带入首轮对话。
分享您的代码库、数据驻留及部署约束。Coroid 能将它们映射到正确的云、EU 或企业运营模型。