
Managed AI agent hosting. Live in 5 minutes. Persistent agents with memory, browser, and tool use. $HIVRA verified at https://nitter.cf/t.co/4qI8GpP4tx
Joined May 2026
- Tweets197
- Following26
- Followers2K
- Likes227
3/4 A major UI redesign
We've redesigned Hivra's interface to make launching and managing cloud agents simpler.
Less friction, easier navigation and a cleaner experience across the platform.
Whether you're deploying your first agent or managing several, we're working towards making the entire experience as straightforward as possible.
1
27
4/4 More agents, more control
We've expanded the list of agents you can launch through Hivra, including:
• @0penBot
• DeepSeek Harness
• @NuphosAI
Alongside that, we've added:
• Daily spending limits for individual agents
• The ability to connect your own computer to Hivra with a single command, allowing your cloud agents to run commands locally with your approval
And there's even more in the works!
Looking forward to showing you what's next. 😉
hivra.cloud
45
Dex Paid 😎
base:0x95ccfd2b81a9667b0cc979992632f98fc853eba3 Founder Holdings Update
As previously announced, I've begun the process of winding down my founder held base:0x95ccfd2b81a9667b0cc979992632f98fc853eba3 position following the migration to $HIVRA.
The plan remains to sell up to 500 million base:0x95ccfd2b81a9667b0cc979992632f98fc853eba3 per week for approximately three months, before burning the remaining founder-held tokens.
I'll be sharing the relevant on-chain transactions so everyone can independently verify the process.
First transaction:
basescan.org/tx/0x9aed84c843…
The proceeds from this sale will go towards covering the cost of Hivra's enhanced token profile on DEX Screener, helping improve the project's presentation and visibility.
My focus remains on building and growing Hivra, and I'll continue keeping the community updated as we move forward.
base:0x95ccfd2b81a9667b0cc979992632f98fc853eba3 Founder Holdings Update
As previously announced, I've begun the process of winding down my founder held base:0x95ccfd2b81a9667b0cc979992632f98fc853eba3 position following the migration to $HIVRA.
The plan remains to sell up to 500 million base:0x95ccfd2b81a9667b0cc979992632f98fc853eba3 per week for approximately three months, before burning the remaining founder-held tokens.
I'll be sharing the relevant on-chain transactions so everyone can independently verify the process.
First transaction:
basescan.org/tx/0x9aed84c843…
The proceeds from this sale will go towards covering the cost of Hivra's enhanced token profile on DEX Screener, helping improve the project's presentation and visibility.
My focus remains on building and growing Hivra, and I'll continue keeping the community updated as we move forward.
Hivra is now 100% open source! 🎉
What started as a platform for deploying AI agents has grown into something much bigger.
You can now launch full cloud computers, run your favourite AI agents, or even bring your own hardware.
Here's a look at what we've been building 👇🧵
5/6
And now, Hivra is completely open source:
You can inspect the code, contribute to development, self-host the platform or build on top of it.
I believe the infrastructure that increasingly capable AI agents run on should be something people can inspect, understand and improve together.
Source code:
github.com/ashneil12/hivra
1
65
6/6
And this is only the foundation.
There's a much bigger ecosystem we're working towards, including better controls for agent permissions, testing, security and collaboration. Soon you'll also be able to launch your favourite apps and repos through Hivra on your own cloud such as T3 Code, MonoCode, OpenShip and more all managed in one central place.
There's plenty more to come!
Explore Hivra:
hivra.cloud
Would love to hear what you think!
63
Hivra Security Update
Following the disclosure of CVE-2026-98432, we've patched our affected infrastructure to address the Linux kernel vulnerability.
The security update has been applied, and our infrastructure is protected against this vulnerability.
We'll continue monitoring security advisories and addressing vulnerabilities as they emerge.
More details:
ubuntu.com/security/CVE-2026…
What a disaster atlasum.net/blog/cve-2026-98…
Hivra retweeted
Now that $HIVRA is live and the latest @HivraOS update is out, I wanted to share what I'll be focusing on over the next 30 days.
My biggest priority now is getting Hivra into more people's hands
I've spent a lot of time building and expanding the platform, but there's still so much I haven't properly demonstrated
So here's what I'm working towards over the next month:
1. Product demonstrations and tutorials
Showing what you can actually do with Hivra, from deploying AI agents to launching full computers and giving agents their own environments to work in
I'll be experimenting with different workflows too, particularly around Claude Code, Codex and Hermes, and showing how they can be used in practice.
2. Improving and expanding the platform
There's still a lot to improve, especially around onboarding, reliability and making the overall experience easier to use
On top of that, there are some features I'm particularly interested in building, including self-hostable, on-demand cloud sandboxes that agents can spin up whenever they need an isolated environment.
3. Expanding Hivra's reach
I'll be more active here on X, while expanding onto Instagram, TikTok and other platforms, testing different content strategies and funnels along the way
A big part of that will be educational content, helping people understand what AI agents actually are, what they're capable of and how they can use them on the other platforms.
One experiment I'm particularly looking forward to is using Claude to create and direct much of this content, from the scripts and visuals to the motion design itself
I'm curious to see just how far I can push Opus 5.5 with motion design for short-form content. Once I've collected some real results, I'll share what I learned.
Beyond social media, there's developer outreach, communities and potential partnerships. Some of that work is already underway, so I'm looking forward to seeing where it leads.
Another area I've been thinking about is building agent-powered services on top of Hivra itself.
Hivra is a fairly technical product, but the businesses built on it don't necessarily have to be.
For example, imagine an SEO agent with access to everything it needs to handle an end-to-end SEO workflow, using tools like OpenSEO, DataForSEO & Specialised SEO skills but presented through a simple dashboard that anyone can use.
Behind the scenes, the agent and its tools run on Hivra's infrastructure. The customer simply uses the service without needing to understand or manage any of it.
That's the kind of thing I'm interested in experimenting with
It also means not every social media account or marketing funnel needs to bring people directly to Hivra. Some can promote services powered by Hivra instead
If this works, it could create another route for growth while demonstrating how other people can build their own products and businesses on top of the platform so there's quite a bit to explore here
Alongside all of this, I want to be more consistent about sharing progress, including what I'm building, the challenges I run into and the results of these experiments.
There are plenty of big initiatives on the roadmap, including Gate, Exchange, Arena, Signal and LaunchPad, but I want to make sure the foundation is solid.
I'll be sharing updates as things progress
Still plenty to build, and I'm excited to share the progress
$HermesOS → $HIVRA Migration Claims
The official $HIVRA migration claim process is now open!
Here's what existing holders need to know:
Snapshot: Base block 53,005,062
Allocation: 1:1 $HIVRA for eligible $HermesOS holdings
Claim platform: Sablier
Claim window: 90 days
Claim fees: Paid by the holder
Old tokens: No burn or surrender required
Official Sablier claim link:
app.sablier.com/airdrops/cam…
$HIVRA contract on Base:
0xe3a1F26440A9FDf5d17b6B3F12F5ebB290080871
Full migration information and verified links:
hivra.cloud/token
Please verify the claim link through the official Hivra website. Never use unsolicited claim links sent through DMs.
$HIVRA is now live on Base.
The new token contract has been deployed, marking the next chapter for Hivra.
Official contract address: 0xe3a1F26440A9FDf5d17b6B3F12F5ebB290080871
For existing $HermesOS holders:
• The migration snapshot was completed at Base block 53,005,062.
• Eligible holders can claim $HIVRA at a 1:1 ratio through Sablier once claims open.
• Holders will pay the applicable claim fee.
• You do not need to burn or surrender your original $HermesOS tokens.
Claims are not open yet. The official claim link and instructions will be published at:
hivra.cloud/token
Please only use links published through the official Hivra website. We will never send claim links through unsolicited DMs.
Further migration updates will follow once the claim campaign is ready.
A few more details on our upcoming transition from base:0x95ccfd2b81a9667b0cc979992632f98fc853eba3 to $HIVRA, including the planned fee structure, liquidity commitments and how existing holders will be able to claim.
Full migration instructions will follow once everything is ready.
I want to explain the decision to move from base:0x95ccfd2b81a9667b0cc979992632f98fc853eba3 to $HIVRA.
I'd previously said I wasn't planning to migrate the original token, and that genuinely was my intention at the time.
But as Hivra continued to evolve, I started reconsidering how the token should fit into the project.
The original token was launched when HermesOS was still a much smaller platform, with a different structure and direction.
With Hivra now open source, the expansion into full computer environments, and a much broader ecosystem in development, I wanted greater independence over how the token operates, particularly around its infrastructure, fees and treasury.
Ultimately, I decided a new token structure made more sense for the direction I'm taking Hivra.
I also wanted to share a few details about the new token.
I'm planning to launch $HIVRA independently through Doppler, without any founder token allocation.
The intended trading fee is approximately 1.58% in total, with 1.2% allocated to the founder, 0.3% dedicated to liquidity, and approximately 0.08% going to Doppler.
The liquidity allocation will be managed separately and used to add and lock liquidity over time. I'll share regular updates with the relevant on-chain transactions so everyone can follow how those funds are being used.
I think it's important to be transparent about how the token operates and where the fees go.
As for the migration, the snapshot has already been completed. Eligible base:0x95ccfd2b81a9667b0cc979992632f98fc853eba3 holders will be able to claim $HIVRA at a 1:1 ratio through Sablier, with a 90-day claim window.
Holders won't need to burn or surrender their original base:0x95ccfd2b81a9667b0cc979992632f98fc853eba3 tokens to claim. There will be a small claim fee payable by holders.
Regarding my remaining base:0x95ccfd2b81a9667b0cc979992632f98fc853eba3 holdings, after an initial two-week waiting period, I plan to sell 500 million tokens per week over approximately three months. Once that schedule is complete, I'll burn the remaining founder-held tokens.
I'll publish the relevant wallet addresses, transactions and final dates so the process is transparent.
The full migration instructions, verified contract addresses and claim dates will be published separately once everything is ready.
My focus remains on building Hivra into something people genuinely want to use, and I'm looking forward to sharing more of that work.
More information: hivra.cloud/token
1
3
416
A new chapter for Hivra.
Hivra is now 100% open source!
What began as a platform for deploying AI agents has evolved into something much bigger.
You can now launch full Windows, Linux and Omarchy computers, deploy your favourite AI agents, or connect and manage your own hardware through Hivra.
We've also completely redesigned the platform, making it easier to launch and manage your environments.
Alongside these changes, we're preparing the transition from $HermesOS to $HIVRA.
Our founder has shared a full update covering what's changed, why we're building Hivra and where the project is heading.
Read the full announcement 👇
2
3
451




