Governance for the agents you already run
Autonomy without overreach.
Define what agents can do. Enforce the limits. Show what happened. HyperShell works with the identity provider, runtime and gateways you already have.
- read test-logsALLOWED
- write prod-configBLOCKED
- request billing-apiAPPROVAL SENT
- call claude-sonnetALLOWED
Sample data.
The problem
Personal AI assistants took off. Autonomous agents stall on access control.
- Authority
- Who granted permission, and for which task?
- Every new workflow waits on a manual access review.
- Limits
- What can the agent read, change or delegate?
- Broad credentials expose critical data. Retries run up model spend.
- Evidence
- Did the agent stay within those limits?
- Logs show what was called, not whether the agent stayed in scope.
How it works
An Envelope defines what an agent can do.
One Envelope per task, tied to the person who granted it. Here is one: an engineering team authorizes an agent to review pull requests on one repository.
A repository owner grants a reviewer agent one repository: read pull requests and write reviews, with approved AI models and a spending limit. Each grant carries an expiry and a delegation depth.
Granted byA repository owner, identity from your enterprise IdP
Agent Envelope
- Tools and data
- One repository and its pull requests
- Actions
- Read diffs, write reviews
- Delegation
- Helpers get the same or narrower limits
- Models and spend
- Approved models, defined spending limit
Why HyperShell
Gateways see tool calls. HyperShell governs the whole task.
IdP tokens and agent gateways
- Person (not covered)
- Agent (not covered)
- Runtime and IAM (not covered)
- Tool gateway (covered)
- Model gateway (covered)
- Tools (not covered)
- Granted to
- A user or an agent identity
- Enforced
- At one point: the API or the gateway
- Evidence
- What was called
HyperShell
- Person (covered)
- Agent (covered)
- Runtime and IAM (covered)
- Tool gateway (covered)
- Model gateway (covered)
- Tools (covered)
- Granted to
- A task, tied to the person who granted it
- Enforced
- At every layer: your runtime, IAM and gateways
- Evidence
- Whether the agent stayed inside the grant
HyperShell works with your existing identity provider, gateways and runtimes rather than replacing them. Category comparison based on vendor documentation.
Deployment
Governance on the platforms you already run.
Your enterprise IdP
Workforce logins stay with your IdP.

Runs in your environment. Compiles each Envelope into your platform's own policy and IAM, extends it where the platform falls short, and records run evidence.
On-premises
NVIDIA OpenShell
Runs on Mirantis Enterprise AI. Aligned with NVIDIA AI Enterprise.
Your AWS account
Amazon Bedrock AgentCore
Uses AgentCore Policy, Gateway and IAM, following AWS best practices.
Planned: SUSE AI Factory certification, Canonical ISV validation, Azure and GCP.
- Extends your platform, does not replace it.
- HyperShell adds the controls an Envelope needs and your platform lacks.
- Agents never hold downstream credentials.
- Credentials for the systems an agent acts on stay outside the agent.
- Adopt without a rebuild.
- Existing agents keep their runtime, harness and model. Each control can start in observe mode, then enforce.
- Designed around NIST's ten proposed tenets for agent identity
- Who does what: you, HyperShell and your platform vendor
HyperShell is not affiliated with NVIDIA or AWS.
Customer example
Helium Mobile cut dashboard data work by about 60%
"HyperShell gave our agents safe, governed access to the data warehouse. Employees stopped waiting days for answers."
Agents queried Helium Mobile's existing Trino warehouse, using business definitions owned by the data team.
Read the customer story- ~60%
- Less dashboard data-ops work
- Under 2 months
- From kickoff to handoff
Start with one workflow and one success metric.
How we start
Three steps to your first governed agent.
01 Scope
No costScoping session
Pick an agent you already run, or a workflow to build. Agree on its access and spending limits and a success criterion.
02 Deploy
Services optionalIn your environment
HyperShell is deployed in your environment and connected to your runtime and systems, by your team or with our engineers.
03 Run and expand
See plansAnnual subscription
HyperShell software subscription and support. Bring more agents and teams under governance as you grow.
Want our engineers alongside your team?
Services are optional and scoped separately. Where are you starting from?
What we do
- Install in your environment
- Write your first Envelopes
- Observe first, then enforce
You get
Your first governed agent.
HyperShell governs your agents whether you build them or we do.
Team
A team that has built and sold open source infrastructure companies, and operated inside large enterprises.

Boris Renski
CEO
Serial open source infrastructure founder. Co-founded Mirantis (acquired by IREN) and FreedomFi (acquired by Nova Labs).

Leo Beliaev
CTO
Engineering leader from Cisco and Dell, and former CEO of Okko, a leading European video streaming platform.

Chris Clason
CRO
AI and infrastructure executive with 22+ years, including leadership roles at Mirantis, Digital Asset and AMD.

Alex Gelf
VP, Customer Engineering
Delivery leader across Silicon Valley and Europe, most recently General Manager at Inventra, a European HR-tech company.
Bring your first agent under governance.
Schedule a scoping session. Bring an agent or workflow owner and a security or platform lead. Leave with a proposed scope, access and spending limits, and a measurable success criterion.