Launched this week
ZooWork lets you build, deploy, and deliver AI agents to teams or clients — experts start in the Builder UI, developers ship with the Managed Agent API. Turn your expertise into AI solutions built for real business operations.
Free Options
Launch Team / Built With
Floot MCPBuild and ship web and mobile apps inside Claude or ChatGPT
Promoted
Hi Product Hunt! 👋
I'm Ning, founder & CEO of ZooWork. Some of you may remember us as ZooClaw from our launch here in April.
Since then, we've heard one thing over and over, and felt it ourselves: there are countless tools for building AI agents, but almost nothing for delivering them. Everyone has an agent that works beautifully on their laptop. Almost no one can hand it to a client, a team, or a paying user as a reliable service.
That gap changed what we build, and our name along with it. ZooWork is our answer: an agent delivery platform for forward-deployed engineers, developers, and domain experts, with the whole path from build to production in one place.
Build: Describe what you want in the no-code Builder, or stay in the coding agent you already use (Claude Code, Codex, and more) and ship through our Managed Agent API. Setup is one line:
Deploy: One click to the cloud, from a single agent to a multi-agent pipeline. Agents cold-start in 1–2 seconds, and you pay nothing while they're idle.
Deliver: Reach users where they already are: a shareable link, an API, or directly in WhatsApp, Slack, and more.
Under the hood, we handle the hardest part: the runtime. Every agent runs in its own managed, isolated sandbox, so what you ship keeps working without you babysitting servers. You own the interface, the customers, and the business. We run the agents.
A few of my favorite agents running on ZooWork today:
A proposal deck studio: drop in your notes, get back a client-ready deck. Built by a consultant, not an engineer.
A personal stylist: describe the occasion, get a complete look and the reasoning behind it.
A home layout designer: snap a photo of your room, get a new layout with an interior designer's eye.
If you've ever built an agent that died on your laptop because there was no good way to share it, I'd love to hear the story. And tell us which coding agent or channel you want next. Your answers go straight into our roadmap.
Thanks for being here on launch day! 🙏
@ninghu glad to see it plays nice with Claude Code and Codex straight out of the box. congrats
@ninghu @priya_kushwaha1 Thanks, Priya! 🙌 We wanted people to keep building with the tools they already love. Give it a spin with an agent you’ve built in Claude Code or Codex—once you can hand someone a working service instead of setup instructions, it’s hard to go back.
@ninghu If I build an agent in the Builder, can a dev pick it up later through the API and keep going? Or are those two separate things?
@mishaal_rashid We support that handoff for now, so a developer can pick up an Agent built in the Builder and continue through the API. Longer term, we'll separate the Builder and API as we see how they're used in practice. I'd try the handoff with a small Builder Agent first.
How does pricing work when you deliver to clients? Do they need a ZooWork seat?
I love how seamless and fast it was to integrate with my code. I thought I'd run into problems but I did not. Besides, the run time is impressive!
What does the handoff process look like when an expert delivers an agent to a business team?
@mikkellarsen Most of the handoff is the expert writing down how the work should be done. In the Agent Builder, they write the Skills and the Agent's job description: its role, the SOP it follows, and what a finished deliverable looks like. Then they connect it to Slack or another IM channel, and the business team uses it right where they already talk. Where does your business team work today, and what kind of Agent would they use there?
Zero idle cost is the detail that makes a weekend agent project feel less wasteful. I'd still check the running costs, but I don't want to pay simply because an experiment exists.
@felix_wang5 That's exactly the cost we didn't want experiments to carry. On the Managed Agent API, the sandbox is billed only for the time it actually runs, plus model tokens, and Agents start in a second or two when called, so a weekend project sitting idle between runs costs nothing. Run it a few times over a weekend and check the usage afterwards to see what a real week costs.
Giving domain experts a builder UI while developers get a managed API is a nice split, it usually means the people who know the work can actually ship without waiting on engineering. Turning expertise into a deliverable agent for clients is a solid framing. Do the experts own the agents after delivery or do they stay tied to your platform?
@karimbenkeroum You can move all your Agent code elsewhere or run it locally. What we bring is the models and tools working smoothly together, so you spend less time wiring everything up. Try the same Agent on ZooWork and with another setup; I think you'll feel the difference in how much easier it is to get things running.
Congrats on the launch, Ning, David and the ZooWork team. Reading the docs, config_version is a counter rather than a history and rollback is left to the app, while per-user agents each get their own copy of the template. For an FDE shipping one agent to 20 clients, is there a plan for staged rollout and one-click rollback when an SOP change makes things worse? That feels like the part that turns delivery into something you can actually maintain.
@genedai Thanks for digging into the docs, Gene. The original author can update an Agent's Skills and AGENT.md in bulk, and end users can update to the latest version with one click. With API delivery, you can have runs use the latest Agent automatically. I still need to check staged rollout and one-click rollback with the team. Try changing one SOP in a Skill and updating a test user's Agent to see how that works.