Managed agents
Managed agents are Alphaus-built agents that use Jennah to store their configuration, approval requests, and audit logs within your enterprise under the standard access control model. Available managed agents are listed under Managed agents in the console for all enterprise members.
AWS Spend Guardrail
AWS Spend Guardrail runs in an AWS payer (management) account and enforces spend caps per account or organizational unit (OU) by attaching a service control policy (SCP) that blocks new spend without stopping or deleting existing resources. It can also monitor the organization's CloudTrail trail and revoke an account's Amazon Bedrock access within minutes when estimated AI spend exceeds configured limits.
Each payer organization uses two datasets in your enterprise:
guardrail.<msp>.<payer>.config: Versioned configuration published by operators. Changes that loosen caps or lift restrictions require human approval via Approvals.guardrail.<msp>.<payer>.inbox: Event log recording freezes, lifts, AI cutoffs, configuration updates, and daily heartbeats written by the guard.
The enterprise also shares a single guardrail.prices dataset containing the AI pricing table. Price updates can only tighten effective thresholds.
To deploy a guard, use the guardrail CLI from the repository along with jnh to initialize the payer datasets, create the guard's reader and writer API keys, and generate the CloudFormation launch URL. The AWS Spend Guardrail page in the console provides the setup commands.
Pricing
The self-managed guard has no license fee, but requires a Pro plan or higher for the application datastore used by its datasets. The managed agent is coming soon and is included at no extra cost with an active Ripple contract. When bundled with Ripple, the entitlement and its expiration date appear under Billing in the console, in jnh billing, and on the AWS Spend Guardrail page.
Installed view
The AWS Spend Guardrail page in the console provides a read-only view of all payer organizations whose guardrail datasets your role can access. Selecting a payer organization displays its reporting status, active and pending configuration versions, currently frozen scopes, active AI cutoffs, and recent events. Status values are derived from the events recorded in Jennah rather than queried directly from AWS. Viewing an installation requires datastore.datasets:read, datastore.data:read, and a dataset selector matching its datasets, such as guardrail.* (see Access control).