Papyrusby Beag Labs.
Verified October 13, 2026
Beag Labs makes Papyrus and compiled this profile. Every statement cites our own pages and is labelled first-party, not independently verified. For the full product story, see the Papyrus product page.
At a glance
- Evidence coverage
- 7 / 8
attributes with a sourced answer
- Cited claims
- 7
records in the Claim Ledger
- Documentation gaps
- 1
attributes not documented in sources checked
- Deployment
- Self-hosted
- Customer cloud tenant
- Licensing
- Commercial
- Azure Marketplace
- Azure VM
- Last verified
- October 13, 2026
Profile, attribute by attribute.
What it does
Document automation, internal app creation and legacy system enablement with governed agent execution.
Source: BL-CLM-18 ↗Does not establish: Describes intended scope in Beag Labs' own words; it is not an independent test of output quality.
Deployment model
Customer-hosted: a Papyrus VM in the customer's Azure subscription, or on-premises, restricted or disconnected environments.
Source: BL-CLM-19 ↗Does not establish: Supported environments and versions should be confirmed against the current agreement and documentation.
Azure Marketplace offer
Azure Marketplace private offer that deploys the Papyrus VM into the customer's subscription.
Source: BL-CLM-20 ↗Does not establish: Private offer, not a public self-serve listing; the signed entitlement remains customer-specific.
Human approval
Governed execution: consequential actions are reviewed and work stays visible as it progresses.
Source: BL-CLM-21 ↗Does not establish: The page does not enumerate which actions require approval or the approval workflow; confirm details before relying on it for a specific control.
Licensing
Commercial: a signed organization license (offline) or a customer-specific Azure private offer.
Source: BL-CLM-22 ↗Does not establish: Papyrus is not offered under an open-source license on this page. Third-party component licenses are listed separately in the Trust Center SBOM.
Security controls
Does not establish: The Papyrus trust page that published the control mapping was retired on October 22, 2026.
Intended buyer
Organizations that need back office automation on their own infrastructure, in business and government settings.
Source: BL-CLM-24 ↗Does not establish: Positioning statement by the vendor.
Public pricing
Does not establish: Establishes that no public price is published, not what a deployment costs.
May fit well when
- Teams that must keep agent execution inside their own Azure subscription or a disconnected environment.Basis:Deployment model (BL-CLM-19)
- Buyers who need a published, machine-readable control mapping to review during procurement.Basis:Security controls
May fit less well when
- Teams that want a free, open-source licence or public per-seat pricing to evaluate without talking to sales.Basis:Licensing (BL-CLM-22)
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.
- Papyrus vs HeartBeatAgentsA sourced head-to-head, including where HeartBeatAgents may be the better fit.
- Papyrus vs OpenClawA sourced head-to-head, including where OpenClaw may be the better fit.
Other platforms
Corral AI (identified as 'Corral Sovereign AI')
Corral
Corral AI is described by its vendor as an AI foundation deployed from Azure Marketplace into the customer's own Azure tenant, where agents are built and governed.
- Customer cloud tenant
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.