01 / 03
Your Azure subscription
Deploy the Papyrus VM into your own subscription, including Azure Government where supported, through an Azure Marketplace private offer.
State & Local Government
Self-Hosted AI Agents for State and LocalGovernment
Papyrus runs inside your environment, so permits, benefits files, public records requests, and case documents stay where your agency already controls them. Agents do the repetitive reading and assembly. Your staff review and approve the results.
Public buildingsPhoto: Photographer not credited · Future plc
The challenge
Agencies need AI that fits how government actually buys and runs software.
Document-heavy, understaffed
Intake, eligibility review, permitting, and records requests still depend on staff reading PDFs and re-keying data into legacy systems.
Hosted AI is hard to approve
Sending resident, case, or employee data to a third-party AI service raises procurement, privacy, and records-retention questions that slow or stop pilots.
Legacy systems stay put
Most agencies cannot replace core systems. Automation has to work around them, with a clear trail of what was done and who approved it.
What agents do
Agents prepare the work. Staff decide.
Document intake and extraction
Bring in PDFs, forms, spreadsheets, and office files. Extract fields and requirements into structured output with source evidence attached.
Reviewable agent workflows
Agents prepare work. Staff review source evidence and approve consequential actions before anything moves downstream.
Internal app factory
Create internal tools and service apps around a workflow, with a USWDS-style interface and Login.gov through OIDC, connected to your existing systems.
Your identity, your models
Use Microsoft Entra for access, and connect Azure OpenAI, OpenAI-compatible gateways, or customer-hosted inference inside your approved boundary.
Deployment
Self-hosted means inside your boundary.
02 / 03
On-premises
Run Papyrus on infrastructure your agency operates, with the same container image and onboarding.
03 / 03
Restricted or disconnected
For environments without outbound access, Beag Labs can issue a signed offline organization license tied to approved Entra tenants and optional hostnames.
Example workflows
Start where the paperwork piles up.
- ✓Permit and license application intake
- ✓Public records and FOIA request triage
- ✓Benefits and eligibility document review
- ✓Procurement and contract document analysis
- ✓Case file summarization with cited sources
- ✓Front-door apps for legacy line-of-business systems
Controls
Built for oversight.
✓Customer-hosted: agent execution and documents stay in your environment
✓Human review before consequential actions
✓Model endpoints you choose, inside the boundary you approve
✓Beag Labs supplies Papyrus component evidence for your own assessment and authorization work
Example workflows are patterns, not claims of completed deployments. Customer-hosted operation does not by itself establish compliance, authorization, or certification. Your agency determines applicable handling requirements and approvals.
FAQ
Common questions.
Where does Papyrus run?
Papyrus is customer-hosted. It runs as a VM in your Azure subscription, on-premises, or in a restricted or disconnected environment. Beag Labs does not host your documents or agent execution.
Which AI models can it use?
Papyrus connects to Azure OpenAI, OpenAI-compatible gateways, and customer-hosted inference. You decide which endpoints are allowed within your boundary.
Is Papyrus FedRAMP authorized or StateRAMP certified?
No. Papyrus is software you host, and Beag Labs makes no authorization or certification claim for it. We provide component evidence and documentation that can contribute to your own assessment and authorization process.
How is it purchased?
Through an Azure Marketplace private offer or a direct agreement. For disconnected environments we issue a signed offline organization license. There is no public price card, because terms follow the deployment you need.
Do staff stay in the loop?
Yes. Agents prepare extractions, drafts, and routing. Staff review source evidence and approve results before downstream action.
Get started
Scope a pilot inside your boundary.
Tell us about one document-heavy workflow and the environment you operate in. We will walk through how Papyrus would fit, what review looks like, and which licensing path matches your procurement.