Launching today
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
Dapp.com
I’ve known the team for a few years. They’ve always been one of the scrappiest teams building in this space. When they told me they built Clawdi on top of OpenClaw, my first question was simple: What can it actually do?
I actually tried OpenClaw briefly when it came out because I heard a lot of AI savvy people had already been using agents to build their "team.” But I gave up after 30 minutes. Well, it was because I didn’t want to spend my time setting things up, not because it wasn’t powerful. Hermes is powerful too, but setup is still the hard part.
Clawdi is where it clicked for me. It took me about 2 minutes to get started, and now I use it for running parts of my Instagram workflow and a bunch of other things. Nothing fancy, just small things that save time every day.
And before anyone asks, yes, your data stays yours. API keys are encrypted and only accessible by you.
These days I’d go to Clawdi just to see what new agents or integrations they’ve shipped, and what else I can offload to my little lobster assistant.
Would love to see how others are using it and what workflows you try on Clawdi.
RiteKit Company Logo API
That's a legitimate concern—abstraction layers only work if they reduce complexity, not add to it. Have you looked into their uptime SLA and whether they offer fallback mechanisms or local-first options for critical agents? Understanding their infrastructure resilience would probably be the first thing I'd validate before committing.
Phala Cloud
Hey Product Hunt 👋 — Marvin here, co-founder of Clawdi.
The honest origin story: I spent three weeks configuring an OpenClaw agent. Skills, cron jobs, 20+ app connections, memory, the whole thing. It was finally working exactly how I wanted. Then a new agent framework dropped that looked genuinely better. I switched.
Everything was gone. Three weeks of work, starting from scratch.
That's the problem we built Clawdi to solve. Every time you switch agent frameworks — and you will switch, because this space is moving insanely fast — you lose everything. Your API keys, your skills, your cron schedules, your agent's memory of how you work. It's not just annoying. It's the reason most people give up on personal agents after a few weeks.
We realized the issue is that your environment — your connections, memory, and config — is trapped inside the framework. So we decoupled them. Clawdi is the environment layer that lives above the framework. Your Gmail, Slack, GitHub, cron jobs, and agent memory live in Clawdi. The agent framework is just the engine you swap in and out.
Switch from OpenClaw to Hermes? Your entire setup carries over. When the next great framework ships next month, you won't start over again.
We also run every workspace inside an Intel TDX hardware-encrypted VM — because a personal AI agent has the keys to your entire digital life, and that deserved real security, not just a promise.
We built this because we needed it. 5,000+ people have tried it since February. Would love to hear what you think — especially if you've felt this pain yourself.
Try it free: https://clawdi.ai
Clawdi
My name is Maggie. I’m the marketing manager at Phala, the TEE infrastructure that Clawdi runs on. So I’ve been close to this project from the start.
My job involves running GTM, social, lifecycle campaigns, content, and a bunch of other things at once. So it's fair to say I am constantly bouncing between tabs, juggling multiple workflows, trying to pulling info from different sources and keep things moving. Also I’m not a developer. I don't have a technical background, so when OpenClaw blew up and because I was actively looking for something to automate my workflows, I tried setting it up locally twice, got lost in the Docker setup both times, and eventually gave up.
Being at Phala meant I knew early on what the team was building with Clawdi. I also knew what it was supposed to solve. But I didn’t actually use it until it was ready enough to just work. I logged in with Google, connected Gmail and Telegram, hit deploy. All under three minutes. My agent said hi to me on Telegram.
First thing I asked Clawdi to do: wiped my Promotions folder. I'd been receiving alerts that my inbox storage is running low but I’d been putting that off for months. 25,500 emails gone in two minutes. Then I set Clawdi up for work. I asked it to pull KPIs from Analytics, the CRM, and our social dashboards every Monday morning and drop a summary in Notion. That used to take me at least 1 hour and a half. With Clawdi all I need to do is to connect it to my work apps with literally just one click and a 1-line prompt “Drop me a clean weekly KPI summary from Analytics, CRM, and socials every Monday morning at 10:00AM EST.”
The part that shaped how we positioned the product: I kept telling the team that the setup was the wall. Not the concept, not the price but the setup. Every non-technical person I showed OpenClaw to bounced at the same point. Clawdi is the answer to that. The 3-minute deployment is NOT a marketing line, it’s the actual fix. With Clawdi integration, the deployment of Hermes agent got even sweeter: Now it doesn’t just do tasks across apps, it learns from every run and gets better over time.
If you work in marketing, ops, or anything that involves a lot of tabs and repetitive tasks, and you’ve already tried OpenClaw and given up, Clawdi is worth another look.
Dapp.com
@maggie_liu8 ngl, it's really helpful for marketing/socials. congrats on the launch!
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. 🙌
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. 🙏
HeyForm
Hey, do you have plans for team or org accounts? I'd love to let my team access shared environments without sharing personal API keys.