Corral AI (identified as 'Corral Sovereign AI')by Corral.
Verified October 13, 2026
This profile was compiled by Beag Labs, which makes a competing product (Papyrus). It is built from public documentation, not hands-on testing, and every statement links to its source.
At a glance
- Evidence coverage
- 7 / 8
attributes with a sourced answer, 1 only partially supported
- Cited claims
- 7
records in the Claim Ledger
- Documentation gaps
- 1
attributes not documented in sources checked
- Deployment
- Customer cloud tenant
- Licensing
- Not categorised
- Azure Marketplace
- Azure managed app
- Last verified
- October 13, 2026
Profile, attribute by attribute.
What it does
Deploy into your cloud, connect data, build agents via Agent Builder; per-user Hub assistant, embeddable widgets.
Source: BL-CLM-26 ↗Does not establish: Vendor marketing; no independent test of functionality.
Deployment model
Deploys into the customer's own Azure tenant and subscription; AWS and GCP listed as coming 2026.
Source: BL-CLM-27 ↗Does not establish: Vendor says Corral manages updates/monitoring (launch post); AWS/GCP not yet available per page.
Azure Marketplace offer
Vendor site links a 'Corral AI managed app' Azure Marketplace listing (azure-application URL path).
Source: BL-CLM-28 ↗Does not establish: Marketplace page itself returned HTTP 403 to fetch, so the listing content was not independently read.
Human approval
Admin approval gates the agent publish flow, and high-risk actions need a human after untrusted content; other actions are not described.
Source: BL-CLM-29 ↗Does not establish: Vendor description; configurability of gates not verified.
Licensing
Not found in checked official pages.
2 sources checked
Does not establish: Pages mention a platform subscription via marketplace but state no license model.
Security controls
Documented: on-tenant residency, private endpoints/VNet, immutable audit trail, content filtering/PII detection, identity-provider governance.
Source: BL-CLM-30 ↗Does not establish: Security page names no SSO/RBAC/encryption; home page claims Entra ID SSO/RBAC. Says it inherits Azure certifications; Corral's own certifications not stated.
Intended buyer
Lists Ops & Product Teams, IT & Security Teams, Developers, Service Providers/SIs, Product Companies.
Source: BL-CLM-31 ↗Does not establish: Vendor segmentation.
Public pricing
No prices listed; platform subscription plus Azure infra costs via Marketplace, counting toward MACC; Enterprise plan via 'Talk to us'.
Source: BL-CLM-32 ↗Does not establish: No amounts published; Marketplace plan prices not read.
May fit well when
- Buyers who need the AI runtime inside their own Azure tenantBasis:Deployment model (BL-CLM-27)
- Buyers wanting Azure Marketplace procurement against existing Azure commitmentsBasis:Public pricing (BL-CLM-32)
May fit less well when
- Buyers needing AWS or GCP deployment todayBasis:Deployment model (BL-CLM-27)
Compared in
- Self-Hosted AI Agent Platforms Compared (2026)Six customer-controlled platforms compared on deployment model, Azure Marketplace offer, human approval, licensing, security and intended buyer. Every cell links to its source.
- Papyrus vs Corral AIA sourced head-to-head, including where Corral AI may be the better fit.
Other platforms
Papyrus
Beag Labs
Customer-hosted agentic workspace for document automation, internal app creation and legacy system enablement.
- Self-hosted
- Customer cloud tenant
- Commercial
HeartBeatAgents
Mosaic Singularity
HeartBeatAgents is a self-hosted platform for building and running autonomous AI agents that work on standing orders with local memory.
- Self-hosted
- Commercial
OpenClaw
OpenClaw Foundation (independent nonprofit, per repo README)
OpenClaw is an open-source assistant/gateway that runs on your own machine or server and connects chat apps to AI agents (repo README; docs.openclaw.ai).
- Self-hosted
- Open source
Methodology and disclosure
How these comparisons are built and checked.
We disclose our interest
Beag Labs makes Papyrus, one of the platforms compared here. Papyrus cells cite our own pages and are labelled first-party. Read every comparison with that in mind.
Every statement is cited
Each Verified or Not supported cell links to a record in the Claim Ledger with the source URL, where on the page it appears, the date we checked it, approved wording, and what it does not prove.
Documentation, not hands-on testing
These comparisons are built from vendor documentation, official listings and repositories. Beag Labs has not run hands-on tests of the compared products. We classify what is documented; we do not score or rank quality, and nothing here is a benchmark.
Missing documentation is not a missing feature
If we cannot find a capability in official sources we say Not documented and list what we checked. We only say Not supported or Partially supported when a source itself says so.
- Verified
- An official source we fetched states it. The cell links to the claim record.
- Partially supported
- An official source documents the capability but states a limit: one surface, a subset of actions, or an explicit exclusion. The cell says what the limit is.
- Not documented
- We checked official sources and found nothing either way. This is not evidence the capability is absent.
- Not supported
- An official source explicitly says the capability is absent or unsupported.