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
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
@fredrick_fabian can you share that tools
Is there a way to selectively share part of an environment with a collaborator without giving full access? Thinking about pair-programming-style AI workflows.
Phala Cloud
Walles.ai - Your AI Browser Sidekick
Solid concept, but "shared memory across agents" needs a strong access control story. If one compromised agent can write to the shared context, it could affect all others. How are you thinking about isolation?
Phala Cloud
GNGM
I like the vision, but I'm a bit wary of adding another abstraction layer on top of my already-complex agent stack. What happens to my workflow if Clawdi has downtime
Phala Cloud
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.
Phala Cloud