Standard access
Get started with a standard subscription using a credit card. Credits remain available for usage and top-ups, but compute tier access comes from your plan.
APRIL 2026 · HIVRA.CLOUD
The operating system for autonomous agents.
This is Hivra's April 2026 roadmap, kept for the record. Hivra has since become agent computers, and parts of this plan have changed. What is live today is kept current below. The current plan is in the litepaper and on the ecosystem page. Anything here that is not live is a plan or a proposal, not a commitment. This is the roadmap for Hivra (hivra.cloud, formerly HermesOS), not for Hermes Agent, which is a Nous Research project.
01 · WHAT IS HIVRA
Hivra gives AI agents computers of their own. Launch Claude Code, Codex, Hermes, Agent Zero, OpenClaw or Aeon on a computer of its own, or launch an Ubuntu, Windows or Omarchy computer and use it yourself.
Run it on Hivra Cloud, on your own cloud account or server, or self-host the whole platform with no Hivra account. You bring your own model key.
02 · WHO IS HIVRA FOR
Hivra is built for anyone who wants to deploy and run autonomous AI agents without managing infrastructure. That includes developers, operators, researchers, businesses, and teams across every background.
Get started with a standard subscription using a credit card. Credits remain available for usage and top-ups, but compute tier access comes from your plan.
Self-hosting needs no Hivra account.
03 · WHAT IS LIVE TODAY
What you can use on Hivra now. This section is kept current.
04 · PRODUCT VISION
The next wave of AI is not about chat interfaces. It is about persistent operators: agents that run continuously, take real-world actions, learn from experience, improve over time, and fund their own compute. Most people cannot build this infrastructure themselves. Hivra closes that gap.
The platform is moving in two directions simultaneously:
Today, deploying on Hivra gives you a powerful but blank canvas. You get the full agent framework, but what you do with it is up to you. The next step is changing that: pre-configured, job-ready operators that arrive knowing their role, with every tool they need already installed. A working agent, not just a starting point, from the moment it deploys.
Every agent on the platform contributes to and draws from a shared intelligence layer called Hive Mind. Agents get better over time not just from what they individually learn, but from what the whole network learns. This is what makes the platform different as it scales.
04 · PRODUCT VISION
A single Hivra agent is useful.
05 · ROADMAP
The four phases as planned in April 2026. The timelines are from then and have moved, and some items have changed. The current plan is in the litepaper.
Operator packs are pre-configured, job-ready agent deployments. They are not skills or plugins. When you deploy an operator pack, everything it needs is installed and configured automatically: tools, capabilities, integrations, memory setup, and system prompts. There are no dependencies to manage, no configuration files to write, and no setup steps to follow.
A skill teaches an agent how to do one thing. An operator pack deploys an agent that already knows its job, has everything it needs to do that job, and is ready to run from the moment it goes live. You connect any API keys the operator requires and it works.
Phase 1 ships three operator packs, each designed for a specific job and ready to run from the moment it deploys.
Research Operator: continuous web research, source monitoring, automated summaries, and recurring intelligence briefs. Deploy a research agent that works around the clock in the background.
Trading Research Operator: market monitoring, watchlists, signal tracking, thesis documentation, and real-time alerts. A serious intelligence and awareness layer for crypto and financial markets.
Growth Operator: lead research, contact enrichment, outreach preparation, content repurposing, and workflow automation for business development and marketing operations.
Skill management: add, remove, and curate the skills available to your agent. Full control over what your operator can do.
File explorer: browse and manage files your agent has created, downloaded, or is working with directly from the dashboard.
Compute access comes from an active subscription. Credits are kept separate so top-ups do not accidentally change a user's compute tier.
Subscription path: card users choose a plan, and that plan defines the compute tier. Credit balances do not unlock or upgrade compute by themselves.
If your subscription falls out of eligibility, there is a grace period before compute pauses. Restoring eligibility during that window keeps the agent recoverable.
Credits are reserved for usage, future top-ups, LLM gateway spend, and premium platform actions.
Keeping credits separate from compute tiers prevents a topped-up balance from being mistaken for Free or paid compute access.
Pack builder: create, save, and version your own operator configurations. Turn a working setup into a reusable template.
Approval controls: agent approval functionality exists today and is being significantly deepened: richer controls, tighter security boundaries, and more granular per-action configuration before agents send messages, execute purchases, or take actions with real-world consequences.
Memory viewer: see what your agent has learned, edit stored context, and control what persists across sessions.
Organisation workspaces: team accounts with shared agents, shared memory, and shared workflows.
Role-based permissions: control who can modify, deploy, or approve actions across a workspace.
Benchmarking and evals: measure how well your operators perform against defined tasks. Track improvement over time.
Phase 2 expands the operator pack library beyond the three flagship operators shipped in Phase 1. Additional packs are added based on community demand and platform priorities, covering new use cases and workflows.
Browse, install, and deploy community-built operator packs.
Verified publisher programme for trusted creators with accountability and track records.
Flexible publishing options: release packs with open access, attach a price for individual purchase, or offer revenue share. Creators choose their own model.
Community templates: free packs contributed by the community, ready to deploy.
Private company packs: organisations maintain their own internal operator libraries, never publicly visible.
Proposed: Users can build and publish their own operators and agents. Creators earn from usage and can withdraw through supported payout options. Additional payout methods will be introduced over time.
One of the most powerful features of the marketplace: dedicated agent endpoints. Instead of sharing your prompts or tooling, you expose your agent as a callable service. Other users and agents can send tasks to your endpoint and receive results, without ever seeing how your agent works under the hood.
Publish your agent as a private endpoint with a public interface. Keep your prompts, tools, and configuration completely private.
Proposed: Other agents and users call your endpoint to run tasks. You set the terms: open access or per-call pricing.
High-demand endpoints scale through managed plan capacity. Hivra manages the scaling infrastructure.
Agent endpoint operators generate revenue from every call while their underlying agent logic stays entirely protected.
Hive Mind Mode is a collective intelligence layer across the Hivra network. Every agent on the platform contributes to and benefits from a shared knowledge base: learned skills, successful workflows, and refined strategies accumulate at the network level, making every agent smarter over time without any individual user needing to do anything extra.
The April 2026 plan was to introduce Hive Mind in early access in Phase 3, with a full release in Phase 4. It has not shipped, and there is no early-access commitment.
Agents share learned capability, not private data. Security and isolation are foundational to the design.
Hive Mind full release: the collective intelligence layer opens to the full network after early access.
Phase 4 opens Hivra to developers and companies who want to build their own agent-powered products on top of the platform.
API access for third-party products: companies build their own consumer-facing agent services using Hivra as the underlying infrastructure.
Operators as a service: teams wanting their own branded agent platform build on Hivra without managing the infrastructure themselves.
06 · OUT OF SCOPE
Being explicit about boundaries is as important as the roadmap itself.
Autonomous trading with user funds: Hivra does not create, operate, or endorse bots that autonomously manage or execute trades on behalf of users.
Yield products or lending returns: Hivra is an agent infrastructure platform, not a financial services product.
MEV strategies, liquidation bots, or front-running tools: not operator categories Hivra ships as first-party products.
Financial advice: nothing produced by this platform constitutes investment, trading, or financial advice.
Users who build their own agents on Hivra infrastructure are building their own products. Hivra provides the platform, not the endorsement.
07 · WHERE THIS IS HEADING
Deploy an agent that gets smarter over time, pays for its own compute, connects to a network of other agents, and operates autonomously at any scale.
Hivra is building infrastructure for deployable agent businesses. The roadmap moves from deployment to operators, from operators to ecosystem, and from ecosystem to a network where agents and users interact through shared infrastructure.
That was the plan in April 2026. What has shipped since is on the homepage and the ecosystem page, and the current plan is in the litepaper.
This document describes planned product direction. Timelines are targets, not guarantees. Features are subject to change.