Clawdi lets you run AI agents like OpenClaw and Hermes in cloud without setup, stop losing your agent setup every time you switch frameworks. The open-source environment that decouples your memory, API keys, and skills from the agent engine.
Free Options
Launch Team / Built With
Hey Product Hunt! 👋 I'm Xiaolu, part of the team at Clawdi, specifically focusing on product research and agent development. It's incredibly exciting to finally share what we've been building with this community.
The honest origin of Clawdi: I kept losing my agent setup. Every time I switched from one framework to another, or picked up a new device, I'd spend the first hour just reconstructing context, re-entering API keys, and re-teaching the agent how I work. It felt like the AI was getting smarter, but the infrastructure around it was still completely fragile.
So we built the layer that was missing. Not another agent, not another framework, just a persistent environment that travels with you. Your memory, skills, secrets, and connected tools live in Clawdi. Every agent you run connects to it. Switch frameworks, add a device, spin up a new agent , your entire setup is already there.
What I'm most proud of: it's MIT-licensed and self-hostable from day one. We didn't want anyone to have to trust a black box with their API keys.
Would love to hear from anyone who's felt this pain, especially if you're running multiple agents in parallel or switching between Claude Code and Codex regularly. That's exactly the use case we've been obsessing over.
Happy to answer any questions below. 🙌
Congrats on launch⭐. How does persistence work for memory and API keys between agents?
Phala Cloud
Ada.im
Been waiting for something like this. I've rebuilt my agent setup from scratch 3 times this year switching between frameworks. The "iCloud for AI agents" framing really clicks. Upvoted and sharing this with my team.
Phala Cloud
@s_cen Three rebuilds this year — that's exactly the pain that made us build this. The iCloud analogy is one we use internally too: your agents should be able to "wake up" on any framework the same way your iPhone wakes up from iCloud after a reset. Nothing lost, nothing to reconfigure.
Really appreciate you sharing it with your team. Would love to hear what frameworks they're running — always curious which combinations people are juggling. 🙏
Decoupling memory and API keys from the agent engine is the right architecture , switching frameworks shouldn't mean starting over. I'm curious how Clawdi handles key rotation, since encrypted keys that never change are still a single point of failure if the vault is compromised.
Kollab
Installed in 5 minutes, synced my OpenClaw config to the hub, then spun up Hermes pointing at the same environment. Actually worked. This is the boring-but-essential infrastructure the space has been missing.
Genuine q as a builder, when an agent has persistent memory + cron + app connections all running in your cloud, what does the off ramp look like if I want to pull my setup out 6 months in ? Memory state is usually the part that locks you in hardest, hard to replicate elsewhere once its built up context.
Phala Cloud
forcing people to share personal API keys or personal agent memory. In other words: team-level vaults, team-level environments, and permissioned access instead of one giant shared account.
We started with personal AI environments first because that pain was immediate, but multi-user / org workflows are one of the next big things we want to support.