面向 AI 与机器控制的可信执行层

执行、审批与控制,打造 更安全的 AI 运营。

Anvil 是 Membara 面向受控 AI 与机器操作的安全产品品牌。Membara Commander 仍是独立服务边界中的核心工具,负责 identity、policy、approval、execution、device sessions、audit 与 evidence。

基于身份的访问
策略与审批
可追溯证据

Commander

运营控制

Illustrative UI

128

Policies

3

Pending approval

8

Device sessions

248

Evidence records

最近执行

Sample

Inspect staging health

Identity-bound action

Approved

Apply controlled change

Identity-bound action

Completed

Production mutation request

Identity-bound action

Held

Execution evidence

Execute safely.

With control and evidence.

Commander trust boundary stays separate from the public website

OIDC identityAuthorityPolicyApprovalEvidence

Anvil principle

“AI should never gain more authority than the identity, policy, approval, and environment allow.”

Anvil 承载安全产品品牌身份;Identity、enrollment、OIDC、MCP、device grants、execution、audit、evidence、privacy 与 service terms 仍由 Commander Core 管理。

Core capabilities

控制 eksekusi, bukan sekadar koneksi ke server.

Commander 将 identity、authority、policy、approval、execution 与 evidence 绑定在一个可审计的 control plane 中。

Policy Engine

为每条命令、每台设备与每个环境应用灵活的执行规则与策略。

  • 基于角色的策略
  • 灵活的规则构建器
  • 访问与权限控制

Approval Flow

在执行前管理审批流程,并支持可配置的工作流。

  • 多级审批
  • 手动或自动审批
  • 实时通知

Audit Trail

完整记录每项活动,并以防篡改方式支持合规与调查。

  • 防篡改日志
  • 强大的搜索与筛选
  • 导出用于审计与合规

Device Sessions

安全管理服务器、IoT 设备与本地系统连接。

  • 受控且加密的访问
  • 实时会话管理
  • 支持多种协议

Task Execution

可靠执行命令与自动化任务,并保持可监控。

  • 计划执行或按需执行
  • 重试与错误处理
  • 实时状态监控

Evidence & Logs

收集执行证据,包括输出、文件、截图与系统日志。

  • 集中式证据存储
  • 可配置的数据保留
  • 与外部系统集成
How Commander works

从 identity 到可证明的 execution。

Commander 确定 principal 身份、拥有的 authority、允许触达的 environment、是否需要 approval,并记录执行结果与 evidence。

01Identity
02Authority
03Policy
04Approval
05Execution
06Evidence

Commander

运营控制

Illustrative UI

128

Policies

3

Pending approval

8

Device sessions

248

Evidence records

最近执行

Sample

Inspect staging health

Identity-bound action

Approved

Apply controlled change

Identity-bound action

Completed

Production mutation request

Identity-bound action

Held

Authority boundaries

Execution authority is explicit, scoped, and tied to authenticated identity and target context.

Fail-closed control

When identity, policy, approval, target binding, or evidence requirements are not satisfied, execution does not silently continue.

Separate service boundary

Commander keeps its own app, database, OIDC, MCP, operational data, privacy policy, and terms separate from the corporate website.

Membara Anvil Commander

Execute with authority. Prove what happened.

Use Anvil to understand the product. Use Commander to authenticate, enroll, connect devices, call MCP tools, approve actions, execute work, and inspect evidence.