Aicura

First release of Aicura on AWS Marketplace.

What this version deploys

One CloudFormation root stack in your own AWS account, in one region across two Availability Zones: the Aicura application and its web app on Amazon ECS Fargate, Amazon RDS for PostgreSQL (Multi-AZ by default), the Evidence Vault on S3 with Object Lock and its verifiable log on Amazon EFS, Temporal for background workflows, an Amazon Cognito user pool for sign-in with optional SAML or OIDC single sign-on, an ACM Private CA for edge component certificates, and the Trust Centre on CloudFront. Everything is encrypted with your own customer managed KMS key, every secret is generated inside the account, and no template parameter carries a secret. The application is internal by default and reachable only from the network ranges you name; it can be opened to the internet behind CloudFront and your own AWS WAF web ACL. The hub-api endpoint your edge components connect to is internal by default as well, reachable from the same ranges, and can be opened to the internet on a public load balancer that accepts only the ranges you name, always behind mutual TLS.

Install kinds

The same template installs as an evaluation, a non-production environment or production, chosen by the first stack parameter, which sets the defaults for sizing, backups, the Evidence Vault lock and what a stack delete keeps; any of them can be overridden. Evaluation and non-production installs are ephemeral: their Evidence Vault bucket is versioned but not locked, and deleting the stack removes everything it created, unless a non-production install is told to keep its stores. Production keeps its data stores, keys and a final database snapshot on delete and locks evidence in compliance mode for seven years. A subscription has one seat, which every running install holds whatever its kind, and a deleted install frees it within an hour; production and a test install side by side take a subscription in each account.

Editions

The product is sold as a contract with one of two dimensions, one seat each. The deployment reads which one you bought from AWS License Manager every fifteen minutes, so changing edition is a Marketplace purchase, never a reinstall.

Aicura Standard: Dashboard and news, the AI Register of systems and agents, Shadow AI Discovery, the prefilled AI product and model catalogue, reports and the library, privacy policy scanning and fixes, model cards and decision disclosures, risk assessments, risks and controls, governance policies, guardrail and preflight rule authoring and deployment, the edge components (hub, gateway, collector and preflight engine), monitoring with KPIs, thresholds and alerts, budgets and spend, the Evidence Vault and evidence packs, AI use requests, impact assessments and incidents, training, single sign-on with directory group roles, and every framework: ADM under the Privacy Act, AI6, NSW AIAF, the AI Ethics Principles, DTA, ISO 42001, NIST AI RMF, NDB, and the EU, UK, Singapore and US frameworks.

Aicura Complete: everything in Standard plus the Guardian, boards and committees, vendors and contracts, security test runs with the security and drift engines, attestations, the Trust Centre, GRC and data provenance syncing, webhooks, and rating scales, categories and the control inventory.

Reference content

The AI product and model catalogues, the framework assessment sets and the news feed arrive as signed content releases an administrator fetches and applies from Content Updates inside the application; nothing is applied until its signature and hash are verified in your account. A fresh install carries none, so apply the current release after the first sign-in.

Before you launch

Enable Amazon Bedrock model access in the deployment account and region for the four models you will name in the stack parameters (a light, a standard and a heavy model tier, and a 1024-dimension embedding model). Have a Route 53 zone and ACM certificates for the application and hub hostnames and the Trust Centre suffix, a verified Amazon SES sending identity, and the network ranges and Transit Gateway that will reach the application. The usage instructions list every parameter and prerequisite.

Regions

Every commercial region where Amazon Bedrock offers the Anthropic Claude models. The China and GovCloud partitions are not offered.

Known findings in third-party components

Three published vulnerabilities remain in the third-party images this version ships, because the upstream projects have not yet released builds without them. CVE-2026-118264 is in the Echo HTTP framework inside the Temporal 1.32.1 command-line tool; CVE-2026-118333 and CVE-2026-118337 are in the Chromium that the Gotenberg 8.39.0 document converter renders documents with. Gotenberg answers only the application's own tasks inside the cluster, over mutually authenticated connections, and is reachable from nowhere else; the Temporal tool runs once during installation and upgrade to apply schemas and serves no traffic. All three clear when the next upstream builds are adopted.

Known constraints

Temporal is upgraded one minor version at a time, so a later version's release notes may name an intermediate version to deploy first. The drift engine's semantic layer is unavailable in this version: its runtime has no release for the engine's Python, so a drift run skips that layer and reports the other layers as usual. The organisation's country is fixed at install. The Evidence Vault signing keys are rotated only with Aicura's support, since a rotation is a re-anchor.