Skip to main content

Security architecture

Boundaries your team can inspect. Controls you can explain.

Moira Connect separates identity, ownership, credentials, entitlements, and runtime delivery so one broad token never stands in for the whole system.

Workspace isolation

Every control-plane action resolves explicit tenant and project ownership before touching provider or billing state.

Tenant + project scope

Encrypted credentials

Provider credentials remain server-side, encrypted, versioned, and limited to their declared operational purpose.

No browser credential storage

Scoped API keys

Project credentials carry explicit purpose and scope, with metadata for rotation, attribution, and last use.

Least-privilege access

One-time disclosure

Secret material is revealed once; retained metadata never recreates a plaintext credential.

Rotate instead of recover

Audit boundaries

Sensitive changes leave an actor, action, target, request identifier, and ownership trail for investigation.

Traceable mutations

Fail-closed entitlement

Provider and plan constraints block unsupported actions instead of silently degrading into misleading success.

Truth over optimistic fallback