Product / VaultCore

Authorization control for customer-owned key paths.

VaultCore is a control-plane authorization service for key lifecycle state, signer-binding intent, deployment boundaries, and signing receipts. Separate execution-routing services resolve governed backend profiles; VaultCore preserves authorization evidence and Alloy never holds customer private keys.

No custody blur: VaultCore coordinates authority, policy, and receipts around signing paths; customers and their approved providers retain key custody and final signing responsibility.
Product console

Built for customer-controlled environments.

VaultCore supports Alloy’s controlled-deployment story: cloud, private cloud, or bank infrastructure with explicit responsibility boundaries.

Operating boundary

Authority inputsTenantKeyOperationPolicy
VaultCore control layerLifecycleAuthorizationSigner bindingReceipts
Signing boundaryApproved providerCustomer-controlled pathDeployment profile
Evidence outputsSigning receiptPolicy resultAudit replay
Controls

Signing authority is a workflow, not just a key.

Lifecycle

Track key state and operational readiness.

Authorization

Check tenant, operation, and policy before signing.

Receipts

Preserve evidence for review and replay.

Provider profile

Keep backend responsibility explicit across customer-controlled or approved provider paths.

Authority model

The page should make key control inspectable.

Key lifecycle

Track creation, activation, rotation, suspension, and retirement state as customer-governed records.

Signer binding

Map which service, tenant, policy, and operation can request signing authority.

Fail-closed checks

Missing tenant, policy, provider, or key state stops the workflow with a reason-coded receipt.

Audit replay

Signing requests can be reviewed later with authority, policy, and provider boundary intact.

Evidence

Proof the buyer can inspect.

Every route keeps Alloy's public story grounded in operating records, custody boundaries, and right-sized modules.

Customer boundaryDeployment profile and provider responsibility are explicit.
Fail-closed postureAuthorization gaps stop the operation.
Receipt ledgerEach signing path produces audit evidence.
No key custody claimVaultCore frames authority and receipts; customers and approved providers retain final key responsibility.
Next step

Bring your current provider stack.

We will map the first workflow Alloy should stabilize, the custody boundary, and the modules that create evidence.