AltairaLabs
GITHUB Run Omnia free
omnia vs bedrock agentcore

Already on AgentCore? Omnia adds the release process, and deploys there too.

Omnia is the release process AgentCore leaves to you: the suite gates the version, traffic moves in steps, and a version that slips rolls back. Updating an AgentCore runtime moves its default endpoint to the new version straight away, and all of it runs in AWS.

Someone updates the claims agent’s runtime.
on omnia

Before a real claimant reaches it, the new version meets simulated ones through the real tools: one inventing a second injury, one on a phone line talking over it. It passes and goes to a share of claims first. If its numbers slip there, the previous version comes back. docs

on bedrock agentcore

When you update an AgentCore Runtime, the DEFAULT endpoint is automatically updated to point to the new version. Rolling back means pointing the endpoint at an earlier one yourself. their docs

Promotion and rollback

A version that fails the suite doesn’t ship. One that passes takes traffic in steps, and a claim already under way stays on the version it started on. It’s promoted if the metrics hold and rolled back if they don’t. docs enterprise

Bedrock AgentCore: A/B tests split live traffic and report significance; you promote the winning variant and redeploy. Automatic rollback isn’t documented. source

Test the calls and the callers

Some simulated users act in good faith and some try to break the agent. Voice tests run full duplex and check barge-in, overlapping speech and dead air. docs

Bedrock AgentCore: An LLM-backed actor plays the end user over text. Adversarial suites and voice simulation aren’t documented. source

One pack, four places to run it

The same pack runs in your Kubernetes cluster and deploys to AgentCore, Google’s agent runtime or Azure AI Foundry with one command. Omnia’s scenarios and telemetry ingestion work wherever the agent is hosted. docs

Bedrock AgentCore: AgentCore runs in AWS, in fifteen regions. source

At a glance

Topic Omnia Bedrock AgentCore, per its docs
Argument-level tool policy yes A CEL rule on every call, before the tool runs. docs enterprise documented Cedar policies on tool input parameters, at the gateway. source
End-user identity to tools yes OIDC or edge trust, carried to every call. docs documented On-behalf-of token exchange. source
Simulated users yes Multi-turn, against real tools, adversarial included. docs partly Multi-turn, text. source
Voice testing yes Barge-in, overlapping speech and dead air. docs not documented Not documented. source
Eval-gated release yes The suite decides whether a version ships. docs not documented Not documented; DEFAULT moves on update. source
Automatic rollback yes On the metrics, during a stepped rollout. docs not documented Not documented. source
Runs outside AWS yes Your cluster, Google or Azure. docs not documented Not documented. source
Telemetry yes OpenTelemetry to your collector, Prometheus metrics. docs documented CloudWatch by default; OTEL-compatible. source

Common questions

Can I use Omnia with AgentCore?
Yes. Omnia deploys a pack to Bedrock AgentCore with one command, runs its scenarios against the deployed agent and ingests its telemetry over OTLP.
How do the pricing models differ?
AgentCore is priced per service on consumption: runtime compute, gateway invocations, policy requests, evaluations and CloudWatch. Omnia’s licencelicense is one price per environment per year from £30,000, free while you build, with nothing metered.

Put your own agent through the gate.

Install Omnia in your cluster and run it free while you build.

Bedrock AgentCore claims are from Amazon Web Services’s published documentation, checked 22 October 2026. Spot something out of date? Tell us.

Install it in your cluster Or walk through it with us →