[{"data":1,"prerenderedAt":1216},["ShallowReactive",2],{"site-nav-content":3,"hiring-banner-content":177,"blog:\u002Fblog\u002Fnimbus-vs-openclaw":189,"blog-index-copy":537,"blog:\u002Fblog\u002Fnimbus-vs-openclaw:surround":558,"site-cta-content":1197},{"header":4,"productNav":9,"nav":42,"footer":61,"askAI":132,"id":161,"title":162,"archived":163,"authors":164,"badge":164,"body":165,"date":164,"definedTerm":164,"department":164,"description":169,"extension":172,"eyebrow":164,"faqHeader":164,"faqs":164,"footerBand":164,"headline":164,"image":164,"industry":164,"jobType":164,"listed":131,"location":164,"navigation":131,"openRoles":164,"pageLayout":164,"path":173,"relatedHeading":164,"seo":174,"series":164,"sitemap":163,"status":164,"stem":175,"subhead":164,"tags":164,"video":164,"whyJoin":164,"workplaceType":164,"__hash__":176},{"productLabel":5,"loginLabel":6,"contactLabel":7,"contactSalesLabel":8},"Product","Log in","Contact","Get started for free",[10,14,18,22,26,30,34,38],{"label":11,"to":12,"description":13},"Overview","\u002Foverview","Seven layers. One closed loop.",{"label":15,"to":16,"description":17},"Conflux","\u002Fproduct\u002Fconflux","Where your team, workstreams, and agents meet.",{"label":19,"to":20,"description":21},"Agent Teams","\u002Fproduct\u002Fagent-teams","Specialist teams - governed from day one.",{"label":23,"to":24,"description":25},"Lifecycle Graph","\u002Fproduct\u002Flifecycle-graph","Intelligence that compounds across every interaction.",{"label":27,"to":28,"description":29},"Company Wiki","\u002Fproduct\u002Fwiki","Playbooks and policies where expertise stays.",{"label":31,"to":32,"description":33},"Workstreams","\u002Fproduct\u002Fworkstreams","From brief to signed-off deliverable on one canvas.",{"label":35,"to":36,"description":37},"Perception Console","\u002Fproduct\u002Fperception","Ask your whole business in plain English.",{"label":39,"to":40,"description":41},"Governance","\u002Fproduct\u002Fgovernance","Frontier AI you can actually sign off on.",[43,46,49,52,55,58],{"label":44,"to":45},"Models","\u002Fmodels",{"label":47,"to":48},"Pricing","\u002Fpricing",{"label":50,"to":51},"Integrations","\u002Fintegrations",{"label":53,"to":54},"Security","\u002Fsecurity",{"label":56,"to":57},"Partners","\u002Fpartners",{"label":59,"to":60},"Insights","\u002Fblog",{"productHeading":5,"companyHeading":62,"resourcesHeading":63,"legalHeading":64,"docsLabel":65,"docsUrl":66,"statementLines":67,"copyright":70,"companyLinks":71,"resourcesLinks":86,"legalLinks":102,"socialLinks":109,"bottomLinks":119},"Company","Resources","Legal","Docs","https:\u002F\u002Fdocs.gonimbus.ai",[68,69],"Stop training someone else's model.","Control your AI.","© 2026 Nimbus Intelligence, Inc. All rights reserved.",[72,73,74,75,76,78,81,84],{"label":47,"to":48},{"label":50,"to":51},{"label":53,"to":54},{"label":59,"to":60},{"label":77,"to":57},"Partner Program",{"label":79,"to":80},"Careers","\u002Fcareers",{"label":82,"to":83},"System status","\u002Fstatus",{"label":7,"to":85},"\u002Fcontact",[87,90,93,96,99],{"label":88,"to":89},"Glossary","\u002Fglossary",{"label":91,"to":92},"Compare","\u002Fcompare",{"label":94,"to":95},"Evaluate","\u002Fevaluate",{"label":97,"to":98},"Problems","\u002Fproblems",{"label":100,"to":101},"Use cases","\u002Fuse-cases",[103,106],{"label":104,"to":105},"Terms of Service","\u002Fterms",{"label":107,"to":108},"Privacy Policy","\u002Fprivacy",[110,113,116],{"label":111,"href":112},"LinkedIn","https:\u002F\u002Fwww.linkedin.com\u002Fcompany\u002Fgonimbusai\u002F",{"label":114,"href":115},"X","https:\u002F\u002Fx.com\u002Fgonimbusai",{"label":117,"href":118},"Instagram","https:\u002F\u002Fwww.instagram.com\u002Fgonimbus_ai\u002F",[120,122,124,127,128],{"label":121,"to":105},"Terms",{"label":123,"to":108},"Privacy",{"label":125,"to":126},"Compliance","\u002Fcompliance",{"label":82,"to":83},{"label":129,"to":130,"external":131},"LLMs.txt","\u002Fllms.txt",true,{"text":133,"prompt":134,"platforms":135},"Ask AI about Nimbus","I'm researching enterprise intelligence platforms and want to know how Nimbus combines perception, collaboration, and autonomous agents to drive strategic decision-making. Summarize the highlights from Nimbus's website: https:\u002F\u002Fgonimbus.ai",[136,141,146,151,156],{"name":137,"label":138,"icon":139,"hrefPrefix":140},"chatgpt","ChatGPT","simple-icons:openai","https:\u002F\u002Fchatgpt.com\u002F?prompt=",{"name":142,"label":143,"icon":144,"hrefPrefix":145},"perplexity","Perplexity","mdi:magnify","https:\u002F\u002Fwww.perplexity.ai\u002Fsearch\u002Fnew?q=",{"name":147,"label":148,"icon":149,"hrefPrefix":150},"grok","Grok","simple-icons:x","https:\u002F\u002Fx.com\u002Fi\u002Fgrok?text=",{"name":152,"label":153,"icon":154,"hrefPrefix":155},"claude","Claude","simple-icons:anthropic","https:\u002F\u002Fclaude.ai\u002Fnew?q=",{"name":157,"label":158,"icon":159,"hrefPrefix":160},"google-ai","Google AI","simple-icons:google","https:\u002F\u002Fwww.google.com\u002Fsearch?udm=50&aep=11&q=","content\u002Fshared\u002Fnav.md","Site navigation",false,null,{"type":166,"value":167,"toc":168},"minimark",[],{"title":169,"searchDepth":170,"depth":170,"links":171},"",2,[],"md","\u002Fshared\u002Fnav",{"title":162,"description":169},"shared\u002Fnav","Q7sDe7TuGEwhwUMamyeOxjvGlsUaF3Iay9VTW0KaE_U",{"enabled":163,"message":178,"linkLabel":79,"linkHref":80,"id":179,"title":180,"archived":163,"authors":164,"badge":164,"body":181,"date":164,"definedTerm":164,"department":164,"description":169,"extension":172,"eyebrow":164,"faqHeader":164,"faqs":164,"footerBand":164,"headline":164,"image":164,"industry":164,"jobType":164,"listed":131,"location":164,"navigation":131,"openRoles":164,"pageLayout":164,"path":185,"relatedHeading":164,"seo":186,"series":164,"sitemap":163,"status":164,"stem":187,"subhead":164,"tags":164,"video":164,"whyJoin":164,"workplaceType":164,"__hash__":188},"We're hiring! Join the team building the Sentient Enterprise.","content\u002Fshared\u002Fhiring.md","Hiring banner",{"type":166,"value":182,"toc":183},[],{"title":169,"searchDepth":170,"depth":170,"links":184},[],"\u002Fshared\u002Fhiring",{"title":180,"description":169},"shared\u002Fhiring","1zs3boivKda1e-b-hAyuNcmZSKjZUAXmecnwHVgcHzk",{"id":190,"title":191,"archived":163,"authors":164,"badge":192,"body":198,"date":512,"definedTerm":164,"department":164,"description":513,"extension":172,"eyebrow":164,"faqHeader":514,"faqs":517,"footerBand":164,"headline":164,"image":164,"industry":164,"jobType":164,"listed":163,"location":164,"navigation":131,"openRoles":164,"pageLayout":164,"path":527,"relatedHeading":164,"seo":528,"series":529,"sitemap":131,"status":164,"stem":530,"subhead":164,"tags":531,"video":164,"whyJoin":164,"workplaceType":164,"__hash__":536},"content\u002Fblog\u002Fnimbus-vs-openclaw.md","Nimbus vs OpenClaw: A Chat Bot on Your Phone, or a Company Workspace with Approvals?",{"label":193,"10|authors":194},"Comparisons",[195],{"name":196,"to":197},"Nimbus Research","https:\u002F\u002Fgonimbus.ai",{"type":166,"value":199,"toc":493},[200,209,216,224,229,292,296,299,312,320,323,326,329,333,336,339,347,351,364,367,374,386,390,395,398,402,405,409,412,416,422,426,429,433,436,440,443,447,450,454,467,471],[201,202,203,208],"p",{},[204,205,207],"a",{"href":206},"https:\u002F\u002Fdocs.openclaw.ai\u002F","OpenClaw"," is a personal or team assistant you install and reach from the chat apps you already live in. Nimbus is a company workspace where a write into Salesforce waits for a named person — and RevOps can refuse it.",[201,210,211,212,215],{},"Both are “an agent.” They are not the same job. A WhatsApp number that can reach a shell is a privileged identity, whether the README is charming or not. The ",[204,213,214],{"href":206},"official docs"," are clear about the audience: developers and power users who want a personal assistant they can message from anywhere, without handing their data to a hosted chatbot. That design is right for a homelab, a founder who wants Telegram on the train, or a tightly scoped internal bot that never sees customer data. It is popular because it works. Popularity is not a control system.",[201,217,218,219,223],{},"OpenClaw is an open-source project (it has also been known as Clawdbot and Moltbot) that you run on your own computer or server. One process sits in the middle; you connect Discord, Google Chat, iMessage, Microsoft Teams, Signal, Slack, Telegram, WhatsApp, and more. You pick the model. You pay that model bill. Setup can be minutes if you are comfortable installing software and pasting an API key. Community packs add tools; treat a marketplace install like unreviewed software with credentials. The ",[204,220,222],{"href":221},"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw","code"," is public. Self-hosting is the point. Self-hosting is also the obligation.",[225,226,228],"h2",{"id":227},"words-youll-hear","Words you’ll hear",[230,231,232,240,246,252,258,264,270,276],"ul",{},[233,234,235,239],"li",{},[236,237,238],"strong",{},"OpenClaw."," An open-source project (it has also been known as Clawdbot and Moltbot) that you run on your own computer or server. One process sits in the middle; you connect Discord, Google Chat, iMessage, Microsoft Teams, Signal, Slack, Telegram, WhatsApp, and more.",[233,241,242,245],{},[236,243,244],{},"Self-hosted."," You pick the model. You pay that model bill. Setup can be minutes if you are comfortable installing software and pasting an API key.",[233,247,248,251],{},[236,249,250],{},"Skills \u002F marketplace."," Community packs that add tools. Treat a marketplace install like unreviewed software with credentials.",[233,253,254,257],{},[236,255,256],{},"Workstream."," In Nimbus, a shared workspace for one job — people, tools, budget, and a finish line.",[233,259,260,263],{},[236,261,262],{},"Agent teams."," AI specialists grouped like departments, assigned to the workstream.",[233,265,266,269],{},[236,267,268],{},"Write-back."," Changing a live system. If an agent can edit an opportunity from a Telegram chat, you no longer have a CRM. You have a group chat with side effects.",[233,271,272,275],{},[236,273,274],{},"Lifecycle Graph."," The record of what ran, who approved, and what changed.",[233,277,278,281,282,286,287,291],{},[236,279,280],{},"Secure AI system development."," The ",[204,283,285],{"href":284},"https:\u002F\u002Fwww.ncsc.gov.uk\u002Fcollection\u002Fguidelines-secure-ai-system-development","UK NCSC guidelines",", issued jointly with ",[204,288,290],{"href":289},"https:\u002F\u002Fwww.cisa.gov\u002Fnews-events\u002Fnews\u002Fdhs-cisa-and-uk-ncsc-release-joint-guidelines-secure-ai-system-development","CISA",": logging, monitoring, and not exposing sensitive data — whether you built the system or stitched it from tools and APIs.",[225,293,295],{"id":294},"why-the-difference-matters","Why the difference matters",[201,297,298],{},"Anyone who can message the bot can try to become the bot. A viral internal bot is a classic “we use AI” slide. It is also a classic reason scaling stalls: nobody can say which token the bot uses, who is allowed to talk to it, or what it changed last Tuesday. OpenClaw’s scarce resource is reach: many messaging surfaces, one agent. Nimbus’s scarce resource is control: many operators and systems, one release process.",[201,300,301,302,306,307,311],{},"OpenClaw memory is whatever you attached: files, a store, community packs. Two people can run two OpenClaws and disagree about last week’s decision because each bot remembered a different thread. There is no company ",[204,303,305],{"href":304},"\u002Fblog\u002Fwhat-is-a-company-wiki-for-ai-agents\u002F","wiki"," product and no Lifecycle Graph of releases. Nimbus memory is three places you can show a colleague: the wiki (what we claim), ",[204,308,310],{"href":309},"\u002Fintegrations\u002F","connectors"," (what Salesforce or the ledger claim), and the graph (what we did). That is what you show when someone asks, “What did we approve?”",[201,313,314,315,319],{},"A personal assistant on your phone and a system that updates customer records are not the same system, even if both answer in chat. The joint NCSC and CISA guidelines exist because the second one is an AI system you operate. Running the software on your own computer does not waive logging, monitoring, or ",[204,316,318],{"href":317},"\u002Fblog\u002Fwhat-is-write-back-governance\u002F","write-back"," gates. Customer data in a WhatsApp-connected agent is still sensitive data in an AI system you operate. Someone else running the server reduces your upkeep. It does not give you workstreams, specialist teams, or a Lifecycle Graph. A service level on a machine is not a release process.",[201,321,322],{},"If an agent can edit an opportunity from a Telegram chat, you no longer have a CRM. You have a group chat with side effects. Skills from a marketplace make that easier, not safer. Treat a pack that adds tools like unreviewed software with credentials — because that is what it is.",[201,324,325],{},"Role by role: a developer or power user who wants Telegram on the train gets the product OpenClaw was designed for. Security should hear “privileged identity,” not “fun bot.” RevOps should refuse a write path that lives in a group chat. Finance cannot reconstruct last Tuesday from a thread only the bot remembered. IT asked to “just host it for the company” is being asked to become the platform team for a personal assistant. A COO counting GitHub stars is measuring excitement. Companies measure blast radius.",[201,327,328],{},"You can still want OpenClaw after a security conversation. Keep it contained: no production credentials, not a public WhatsApp number on company data, a named owner, and an exit — the proven job becomes a Nimbus workstream; the bot goes back to being personal. Personal agents can feed drafts into Nimbus workstreams. Do not let the chat bot hold write credentials to core systems.",[225,330,332],{"id":331},"when-openclaw-is-a-better-fit","When OpenClaw is a better fit",[201,334,335],{},"Choose OpenClaw for personal productivity, home automation, and greenfield bots where you are the admin. Choose it when the blast radius is your own chats and files.",[201,337,338],{},"Do not choose OpenClaw as the company AI platform because it has more GitHub stars than last quarter’s shortlist. Stars measure excitement. Companies measure blast radius.",[201,340,341,342,346],{},"If you still want OpenClaw after a security conversation, keep it contained: no production credentials, not a public WhatsApp number on company data, a named owner, and an exit — the proven job becomes a Nimbus workstream; the bot goes back to being personal. Same layer as ",[204,343,345],{"href":344},"\u002Fblog\u002Fnimbus-vs-hermes\u002F","Hermes",": a personal assistant you look after. OpenClaw maximises channels. Hermes maximises skills and personal memory. Neither is a company OS.",[225,348,350],{"id":349},"how-this-shows-up-in-nimbus","How this shows up in Nimbus",[201,352,353,354,358,359,363],{},"Nimbus is the application you log into at work. Operators do not babysit a process on a server. They open a ",[204,355,357],{"href":356},"\u002Fproduct\u002Fworkstreams\u002F","workstream"," with ",[204,360,362],{"href":361},"\u002Fproduct\u002Fagent-teams\u002F","agent teams"," and connectors.",[201,365,366],{},"Writes into those tools stay off until you turn them on. A quoted change sits until a human signs. You can think of Nimbus as the place OpenClaw users graduate to when the bot needs a company identity: production passwords leave the home server, writes pick up an approval, and the artefact lands where other people can find it.",[201,368,369,370,373],{},"Nimbus ",[204,371,372],{"href":309},"integrations"," are a catalogue you scope per workspace — more than 2,000 tools — read-only until write is enabled. The default if someone adds a dangerous skill is not “whatever the host allowed.” The default is: the connector cannot write until you say so.",[201,375,376,377,381,382,385],{},"See the ",[204,378,380],{"href":379},"\u002Foverview\u002F","overview"," and ",[204,383,39],{"href":384},"\u002Fproduct\u002Fgovernance\u002F",".",[225,387,389],{"id":388},"questions-people-actually-ask","Questions people actually ask",[391,392,394],"h3",{"id":393},"is-openclaw-a-nimbus-competitor","Is OpenClaw a Nimbus competitor?",[201,396,397],{},"On a spreadsheet that says “we want an agent,” yes. In practice, one is a chat assistant you install. One is a company operating system for work, approvals, and memory.",[391,399,401],{"id":400},"can-we-put-openclaw-in-front-of-nimbus","Can we put OpenClaw in front of Nimbus?",[201,403,404],{},"Personal agents can feed drafts into Nimbus workstreams. Do not let the chat bot hold write credentials to core systems. Put those in Nimbus connector scopes.",[391,406,408],{"id":407},"what-about-a-hosted-or-cloud-openclaw","What about a hosted or cloud OpenClaw?",[201,410,411],{},"Someone else running the server reduces your upkeep. It does not give you workstreams, specialist teams, or a Lifecycle Graph. A service level on a machine is not a release process.",[391,413,415],{"id":414},"is-openclaw-the-same-as-hermes","Is OpenClaw the same as Hermes?",[201,417,418,419,385],{},"Same layer — a personal assistant you look after — different emphasis. OpenClaw maximises channels. Hermes maximises skills and personal memory. Neither is a company OS. See ",[204,420,421],{"href":344},"Nimbus vs Hermes",[391,423,425],{"id":424},"does-self-hosting-mean-we-can-skip-logging-and-monitoring","Does self-hosting mean we can skip logging and monitoring?",[201,427,428],{},"No. Customer data in a WhatsApp-connected agent is still sensitive data in an AI system you operate. NCSC and CISA’s joint guidelines include logging, monitoring, and not exposing that data to unauthorised parties.",[391,430,432],{"id":431},"can-we-standardise-the-company-on-openclaw-if-we-lock-down-who-can-message-it","Can we standardise the company on OpenClaw if we lock down who can message it?",[201,434,435],{},"Locking down who can talk to the bot is necessary and not sufficient. You still lack workstreams, specialist teams, a wiki, quoted writes, and a graph. A tightly scoped internal bot that never sees customer data can stay. A company platform cannot be “the bot, but with a allow-list.”",[391,437,439],{"id":438},"who-owns-an-internal-openclaw","Who owns an internal OpenClaw?",[201,441,442],{},"Whoever runs the process owns the outcome: tokens, skills, who may message it, what it can reach. That is usually a developer, not RevOps. If the bot can change production data, you have given a personal-assistant owner a CRM duty they did not ask for. Move that duty to Nimbus governance.",[391,444,446],{"id":445},"how-do-we-retire-a-viral-bot-without-a-fight","How do we retire a viral bot without a fight?",[201,448,449],{},"Name an exit in advance: the proven job becomes a workstream; production credentials leave the bot; the bot goes back to being personal. Stars and habit are not an argument to keep a WhatsApp number on company data.",[225,451,453],{"id":452},"related-reading","Related reading",[201,455,456,460,461,464,465,385],{},[204,457,459],{"href":458},"\u002Fblog\u002Fwhat-is-shadow-ai\u002F","What is shadow AI",", ",[204,462,463],{"href":317},"What is write-back governance",", and ",[204,466,421],{"href":344},[225,468,470],{"id":469},"sources","Sources",[230,472,473,478,483,488],{},[233,474,475],{},[204,476,477],{"href":206},"OpenClaw documentation",[233,479,480],{},[204,481,482],{"href":221},"OpenClaw on GitHub",[233,484,485],{},[204,486,487],{"href":284},"UK NCSC, Guidelines for secure AI system development",[233,489,490],{},[204,491,492],{"href":289},"CISA and UK NCSC joint guidelines for secure AI system development",{"title":169,"searchDepth":170,"depth":170,"links":494},[495,496,497,498,499,510,511],{"id":227,"depth":170,"text":228},{"id":294,"depth":170,"text":295},{"id":331,"depth":170,"text":332},{"id":349,"depth":170,"text":350},{"id":388,"depth":170,"text":389,"children":500},[501,503,504,505,506,507,508,509],{"id":393,"depth":502,"text":394},3,{"id":400,"depth":502,"text":401},{"id":407,"depth":502,"text":408},{"id":414,"depth":502,"text":415},{"id":424,"depth":502,"text":425},{"id":431,"depth":502,"text":432},{"id":438,"depth":502,"text":439},{"id":445,"depth":502,"text":446},{"id":452,"depth":170,"text":453},{"id":469,"depth":170,"text":470},"2026-08-17","OpenClaw is a self-hosted agent you message from WhatsApp or Telegram; Nimbus is the company workspace where a CRM write waits for a named person.",{"eyebrow":515,"title":516},"Short answers","A phone bot versus a company workspace",[518,521,524],{"question":519,"answer":520},"What is OpenClaw?","A self-hosted agent you message from WhatsApp or Telegram.",{"question":522,"answer":523},"What can that not do?","It cannot make a CRM write wait for a named person inside a company workspace.",{"question":525,"answer":526},"When is a chat bot the wrong home for the job?","When the action changes a business system and someone has to be able to refuse it.","\u002Fblog\u002Fnimbus-vs-openclaw",{"title":191,"description":513},"comparisons","blog\u002Fnimbus-vs-openclaw",[529,532,533,534,535],"openclaw","clawdbot","self-hosted-agents","governance","lHJrOKexpIQljmj2IQony0dKKxlFz117KJgrQEANYB0",{"hero":538,"id":540,"title":541,"archived":163,"authors":164,"badge":164,"body":542,"date":164,"definedTerm":164,"department":164,"description":546,"extension":172,"eyebrow":547,"faqHeader":164,"faqs":164,"footerBand":548,"headline":164,"image":164,"industry":164,"jobType":164,"listed":131,"location":164,"navigation":131,"openRoles":164,"pageLayout":164,"path":60,"relatedHeading":554,"seo":555,"series":164,"sitemap":131,"status":164,"stem":556,"subhead":164,"tags":164,"video":164,"whyJoin":164,"workplaceType":164,"__hash__":557},{"filename":539},"u2221455217_Flat_design_of_a_futuristic_minimalist_landscape__5d589295-cdea-4ea9-a262-be766881accf_1.png","content\u002Fblog\u002Findex.md","Exploring the future of intelligence.",{"type":166,"value":543,"toc":544},[],{"title":169,"searchDepth":170,"depth":170,"links":545},[],"Deep dives into pre-cognitive intelligence, sentient enterprises, and the evolving landscape of AI-driven business transformation.","Latest Research",{"headline":549,"description":550,"primaryLabel":551,"primaryTo":552,"secondaryLabel":553,"secondaryTo":12},"Stay at the frontier.","Subscribe for product updates and new insights.","Subscribe","\u002Fnewsletter","Explore the platform","More research",{"title":541,"description":546},"blog\u002Findex","BFSWGYO9bcTlaulivKYWyg08_DJHsdGg3OC6g_CG1Hw",[559,881],{"id":560,"title":561,"archived":163,"authors":164,"badge":562,"body":565,"date":512,"definedTerm":164,"department":164,"description":860,"extension":172,"eyebrow":164,"faqHeader":861,"faqs":863,"footerBand":164,"headline":164,"image":164,"industry":164,"jobType":164,"listed":163,"location":164,"navigation":131,"openRoles":164,"pageLayout":164,"path":873,"relatedHeading":164,"seo":874,"series":529,"sitemap":131,"status":164,"stem":875,"subhead":164,"tags":876,"video":164,"whyJoin":164,"workplaceType":164,"__hash__":880},"content\u002Fblog\u002Fnimbus-vs-paperclip.md","Nimbus vs Paperclip: An Org Chart for Other People’s Bots, or a Product a COO Can Log Into?",{"label":193,"10|authors":563},[564],{"name":196,"to":197},{"type":166,"value":566,"toc":842},[567,574,586,602,604,662,664,667,673,686,689,692,699,703,710,713,716,719,721,724,733,738,740,744,747,751,754,758,761,765,768,772,782,786,791,795,798,802,805,807,819,821],[201,568,569,573],{},[204,570,572],{"href":571},"https:\u002F\u002Fpaperclip.ing\u002F","Paperclip"," is the management layer people reach for when they already run OpenClaw, Hermes, Claude, Cursor, or a pile of custom workers and have lost track of who is doing what and what it costs. Nimbus is the finished product those operators log into: one shared workspace for a job, specialist teams, official playbooks, and a record of what shipped.",[201,575,576,577,581,582,585],{},"Paperclip is multiplayer for ",[578,579,580],"em",{},"agents",". Nimbus is multiplayer for departments and the people in them. The insight behind Paperclip is correct. Multi-agent chaos is an organisation-design problem, not a prompting problem. If you have lived through “we have twelve automations, three chat bots, and a coding agent fleet,” Paperclip feels like relief. Someone finally named the org chart. Relief is not a workplace. An org chart of agents is a start. A signed-off outcome in a workstream is the product those agents would work ",[578,583,584],{},"in",", not the scheduler that wakes them.",[201,587,588,589,592,593,381,597,601],{},"Paperclip is an open-source app to manage AI agents for work. You define a goal, “hire” agents into roles, set monthly budgets, and run work through tickets. Agents wake on a schedule and stop when they hit the budget. The ",[204,590,222],{"href":591},"https:\u002F\u002Fgithub.com\u002Fpaperclipai\u002Fpaperclip"," is public; you can run it yourself. It works with many agents — the site lists Claude, Codex, Gemini, Cursor, Hermes, OpenClaw, and others. If a worker can receive a heartbeat, it can be hired. ",[204,594,596],{"href":595},"https:\u002F\u002Fdocs.crewai.com\u002F","CrewAI",[204,598,600],{"href":599},"https:\u002F\u002Farxiv.org\u002Fabs\u002F2308.00352","MetaGPT"," are the research-and-builder names for that orchestration category. Paperclip is that category as a product you hire into.",[225,603,228],{"id":227},[230,605,606,615,626,632,637,642,648,657],{},[233,607,608,611,612,614],{},[236,609,610],{},"Paperclip."," An open-source app to manage AI agents for work. You define a goal, “hire” agents into roles, set monthly budgets, and run work through tickets. Agents wake on a schedule and stop when they hit the budget. The ",[204,613,222],{"href":591}," is public; you can run it yourself.",[233,616,617,620,621,381,623,625],{},[236,618,619],{},"Orchestration."," Coordinating several agents. ",[204,622,596],{"href":595},[204,624,600],{"href":599}," are the research-and-builder names for that category. Paperclip is that category as a product you hire into.",[233,627,628,631],{},[236,629,630],{},"Agent budget."," Cap the worker, warn at 80%, pause at 100%. Necessary cost control. Not the same as stopping a bad write.",[233,633,634,636],{},[236,635,256],{}," In Nimbus, a shared workspace for one job — the ticket a non-engineer can actually run.",[233,638,639,641],{},[236,640,262],{}," AI specialists grouped like departments: finance, go-to-market, ops. You are not wiring a cluster of other people’s bots on day one.",[233,643,644,647],{},[236,645,646],{},"Wiki."," Official playbooks those teams must respect.",[233,649,650,652,653,656],{},[236,651,268],{}," Changing a live system. Paperclip’s FAQ is frank: it governs what agents do ",[578,654,655],{},"to Paperclip"," (hiring, strategy). Your agents are your own, and you secure them however you want.",[233,658,659,661],{},[236,660,274],{}," What ran, who approved, and what changed — so next quarter’s team does not relitigate the exception from Slack archaeology.",[225,663,295],{"id":294},[201,665,666],{},"The limitation is structural. Paperclip assumes you bring the employees (the agents), the tools, the memory, and the identity story. That is honest. It is also why a scheduler is not the product your board logs into. You still need a place work is grounded, a place writes are gated, and a place the company remembers.",[201,668,669,670,672],{},"A worker that hits its budget and stops is a cost control. A worker that hits production with the wrong SKU is an incident. Nimbus also caps spend so a long-running job cannot silently burn the month (usage limits and budgets in money). The extra loop is change control: which system a write hits, who signs, where the artefact is stored. See ",[204,671,535],{"href":384},". Cap-at-100% is necessary. It is not the same as stopping a bad write.",[201,674,675,676,678,679,682,683,685],{},"Paperclip does not replace a knowledge layer. Each hired agent may remember differently — Hermes how-to notes here, OpenClaw files there, a folder nobody owns. Different agents will each tell you a different last quarter. Nimbus ships wiki plus ",[204,677,310],{"href":309}," plus the ",[204,680,23],{"href":681},"\u002Fblog\u002Fwhat-is-a-lifecycle-graph\u002F"," so execution has one place to read from and a gated place to write to. Paperclip’s FAQ is frank: it governs what agents do ",[578,684,655],{}," (hiring, strategy). Your agents are your own, and you secure them however you want. That frankness is a virtue. It is also the gap. Write-back into Salesforce is not Paperclip’s job unless you built it into the workers you hired.",[201,687,688],{},"Speed of new agents is exactly why a scheduler appears. It is also why a scheduler is not the office. A staff rota does not replace the workplace. It only says who is on shift. OpenClaw and Hermes are employees. Paperclip is the org chart. Nimbus is the company plus the office. Buying all three still does not give you a Lifecycle Graph unless Nimbus (or something like it) is in the stack.",[201,690,691],{},"Role by role: an engineer running OpenClaw, Hermes, and a coding fleet will feel Paperclip as relief — budgets, tickets, a heartbeat. A Head of Ops should not be asked to assemble that roster on day one; they need a product they can log into. Finance cares that a pause-at-budget is not a pause-at-bad-journal. Security inherits whatever each hired agent can already do; Paperclip does not secure them for you. A COO comparing open source versus a hosted product is choosing which lock they can staff: Paperclip reduces vendor lock-in and increases ops lock-in. Most companies can complete a vendor review. Few can run a round-the-clock agent operations desk.",[201,693,694,695,698],{},"If you are committed to those workers and only need orchestration, Paperclip is in-category. If you are not building an OS, do not start with the scheduler. Treat the workers as prototypes. Recreate the ",[578,696,697],{},"jobs"," as Nimbus workstreams and agent teams. Leave the old bots as personal tools without production credentials. Do not lift-and-shift tickets. Lift-and-shift the operating loop.",[225,700,702],{"id":701},"when-paperclip-is-a-better-fit","When Paperclip is a better fit",[201,704,705,706,709],{},"Choose Paperclip when you are committed to OpenClaw, Hermes, or custom workers, you have people to operate them, and you only need orchestration. Choose it as a research scheduler in a lab. Choose it if your company ",[578,707,708],{},"is"," building an agent OS and you need that scheduler while you build the rest.",[201,711,712],{},"If you are not building an OS, do not start with the scheduler. A staff rota does not replace the office. It only says who is on shift.",[201,714,715],{},"Paperclip’s value shows up when you have several different workers to coordinate. Nimbus’s value shows up at one team that must touch production systems safely. You do not need Paperclip if you only have one agent. You might still need Nimbus.",[201,717,718],{},"Do not put a second org chart on top of Nimbus. Nimbus already assigns work to agent teams. Two budgets and two sources of truth is a support nightmare. If you migrate, migrate jobs, not tickets.",[225,720,350],{"id":349},[201,722,723],{},"Nimbus is the application layer a Head of Ops opens without assembling a roster of third-party bots on day one.",[201,725,726,727,381,729,732],{},"You attach connectors under a read-only default. Humans release writes. You get specialist teams and a canvas, then you attach systems. See ",[204,728,362],{"href":361},[204,730,731],{"href":356},"workstreams",". Spend is capped by usage limits and budgets so a long-running job cannot silently burn the month — and the write still waits for a signer.",[201,734,735,736,385],{},"Start at the ",[204,737,380],{"href":379},[225,739,389],{"id":388},[391,741,743],{"id":742},"is-nimbus-paperclip-with-a-nicer-screen","Is Nimbus “Paperclip with a nicer screen”?",[201,745,746],{},"No. The overlap is control: roles, budgets, assignment. The product is the work loop and the graph. A ticket router does not give you official playbooks or a read-only-default CRM connector.",[391,748,750],{"id":749},"can-paperclip-orchestrate-nimbus","Can Paperclip orchestrate Nimbus?",[201,752,753],{},"Unnatural. Nimbus already assigns work to agent teams. A second org chart on top is two budgets, two sources of truth, and a support nightmare.",[391,755,757],{"id":756},"open-source-vs-a-hosted-product-which-lock-in-is-worse","Open source vs a hosted product — which lock-in is worse?",[201,759,760],{},"Paperclip reduces vendor lock-in and increases ops lock-in: you staff the bots. Nimbus is the reverse. Pick the lock you can actually staff. Most companies can complete a vendor review. Few can run a round-the-clock agent operations desk.",[391,762,764],{"id":763},"do-we-need-paperclip-if-we-only-have-one-agent","Do we need Paperclip if we only have one agent?",[201,766,767],{},"No. Paperclip’s value shows up when you have several different workers to coordinate. Nimbus’s value shows up at one team that must touch production systems safely.",[391,769,771],{"id":770},"how-does-paperclip-relate-to-openclaw-and-hermes","How does Paperclip relate to OpenClaw and Hermes?",[201,773,774,775,381,779,781],{},"OpenClaw and Hermes are employees. Paperclip is the org chart. Nimbus is the company plus the office. See ",[204,776,778],{"href":777},"\u002Fblog\u002Fnimbus-vs-openclaw\u002F","Nimbus vs OpenClaw",[204,780,421],{"href":344},". Buying all three still does not give you a Lifecycle Graph.",[391,783,785],{"id":784},"can-we-migrate-from-paperclip-to-nimbus","Can we migrate from Paperclip to Nimbus?",[201,787,788,789,698],{},"Treat the workers as prototypes. Recreate the ",[578,790,697],{},[391,792,794],{"id":793},"does-a-budget-cap-replace-write-back-governance","Does a budget cap replace write-back governance?",[201,796,797],{},"No. A worker that hits its budget and stops is a cost control. A worker that hits production with the wrong SKU is an incident. Caps are necessary. They do not quote a field change or name a signer.",[391,799,801],{"id":800},"who-should-run-paperclip-if-we-keep-it","Who should run Paperclip if we keep it?",[201,803,804],{},"Whoever already operates the bots — usually engineering. Do not hand a Head of Ops a scheduler and call it a workplace. If operators need to finish a job, they need Nimbus. If engineers need to wake a fleet, they may still want Paperclip in the lab, off production credentials.",[225,806,453],{"id":452},[201,808,809,460,813,464,817,385],{},[204,810,812],{"href":811},"\u002Fblog\u002Fwhat-is-multi-agent-ai\u002F","What is multi-agent AI",[204,814,816],{"href":815},"\u002Fblog\u002Fwhat-is-an-ai-workstream\u002F","What is an AI workstream",[204,818,778],{"href":777},[225,820,470],{"id":469},[230,822,823,827,832,837],{},[233,824,825],{},[204,826,572],{"href":571},[233,828,829],{},[204,830,831],{"href":591},"Paperclip on GitHub",[233,833,834],{},[204,835,836],{"href":595},"CrewAI documentation",[233,838,839],{},[204,840,841],{"href":599},"Hong et al., MetaGPT (arXiv:2308.00352)",{"title":169,"searchDepth":170,"depth":170,"links":843},[844,845,846,847,848,858,859],{"id":227,"depth":170,"text":228},{"id":294,"depth":170,"text":295},{"id":701,"depth":170,"text":702},{"id":349,"depth":170,"text":350},{"id":388,"depth":170,"text":389,"children":849},[850,851,852,853,854,855,856,857],{"id":742,"depth":502,"text":743},{"id":749,"depth":502,"text":750},{"id":756,"depth":502,"text":757},{"id":763,"depth":502,"text":764},{"id":770,"depth":502,"text":771},{"id":784,"depth":502,"text":785},{"id":793,"depth":502,"text":794},{"id":800,"depth":502,"text":801},{"id":452,"depth":170,"text":453},{"id":469,"depth":170,"text":470},"Paperclip organises the agents you already run; Nimbus is the finished workplace where departments share one job — not twelve bots nobody owns.",{"eyebrow":515,"title":862},"An org chart for bots, or one shared job",[864,867,870],{"question":865,"answer":866},"What does Paperclip organise?","The agents you already run. It is a way to see other people's bots.",{"question":868,"answer":869},"What does a department still need?","One shared job, a finish line, and an owner. Twelve bots with no owner is not that.",{"question":871,"answer":872},"Who is Nimbus for in this comparison?","The COO who needs a product people log into to finish work, not a map of agents nobody is accountable for.","\u002Fblog\u002Fnimbus-vs-paperclip",{"title":561,"description":860},"blog\u002Fnimbus-vs-paperclip",[529,877,878,879,535],"paperclip","multi-agent","orchestration","W67icN9laN6XBOt93cMC0RzT-Zrg3f-bzT8ineJ3FYM",{"id":882,"title":883,"archived":163,"authors":164,"badge":884,"body":887,"date":512,"definedTerm":164,"department":164,"description":1175,"extension":172,"eyebrow":164,"faqHeader":1176,"faqs":1178,"footerBand":164,"headline":164,"image":164,"industry":164,"jobType":164,"listed":163,"location":164,"navigation":131,"openRoles":164,"pageLayout":164,"path":1188,"relatedHeading":164,"seo":1189,"series":529,"sitemap":131,"status":164,"stem":1190,"subhead":164,"tags":1191,"video":164,"whyJoin":164,"workplaceType":164,"__hash__":1196},"content\u002Fblog\u002Fnimbus-vs-hermes.md","Nimbus vs Hermes: A Personal Agent That Learns You, or a System That Remembers the Business?",{"label":193,"10|authors":885},[886],{"name":196,"to":197},{"type":166,"value":888,"toc":1157},[889,904,907,919,921,974,976,983,986,995,1002,1005,1017,1023,1027,1034,1039,1042,1044,1047,1060,1064,1066,1070,1073,1077,1080,1084,1087,1091,1094,1098,1101,1105,1109,1113,1116,1120,1123,1125,1135,1137],[201,890,891,895,896,899,900,903],{},[204,892,894],{"href":893},"https:\u002F\u002Fhermes-agent.nousresearch.com\u002F","Hermes Agent"," is built to get better at ",[578,897,898],{},"you",". It remembers your projects, writes little how-to notes for itself after a hard task, and can schedule briefings while you are away. Nimbus is built so the ",[578,901,902],{},"business"," still knows what happened when that person is on a plane: official playbooks, a named signer on writes, and a record that does not live on one laptop.",[201,905,906],{},"Both are “an agent that remembers.” They are not the same memory. Personal memory is preferences, procedures, the way you like a report. Company memory is playbooks, signers, and a graph the next person can query. Hermes is honest about the bargain: remembering you is the product. Nimbus is honest about a different bargain: the company still knows after you leave.",[201,908,909,910,914,915,918],{},"Hermes is a real step beyond a chat window that forgets you every morning. It is an open-source personal agent from ",[204,911,913],{"href":912},"https:\u002F\u002Fnousresearch.com\u002F","Nous Research",". You install it on a Mac, Windows, or Linux machine. It can also live in Telegram, Discord, Slack, WhatsApp, Signal, email, or a terminal. It talks to many model providers, so you are not locked to one lab. It can spin up helper agents with their own conversations. The ",[204,916,222],{"href":917},"https:\u002F\u002Fgithub.com\u002Fnousresearch\u002Fhermes-agent\u002F"," is public. If you are a founder, a researcher, or a power user who will actually look after the install, Hermes is doing the job it was designed for.",[225,920,228],{"id":227},[230,922,923,932,937,943,948,953,958,963],{},[233,924,925,928,929,931],{},[236,926,927],{},"Hermes Agent."," An open-source personal agent from ",[204,930,913],{"href":912},". You install it on a Mac, Windows, or Linux machine. It can also live in Telegram, Discord, Slack, WhatsApp, Signal, email, or a terminal.",[233,933,934,936],{},[236,935,244],{}," You run the software. You pay the model bill. You keep the secrets. You are the operator.",[233,938,939,942],{},[236,940,941],{},"Personal memory."," Preferences, procedures, the way you like a report. Powerful for one operator. Risky if that operator also has mailbox and company-file access.",[233,944,945,947],{},[236,946,256],{}," In Nimbus, a shared workspace for one job — not a private conversation on a machine.",[233,949,950,952],{},[236,951,646],{}," Official playbooks: how we book a journal, who may sign, what “done” means. Agents read that, not a private note on a desktop.",[233,954,955,957],{},[236,956,268],{}," Changing a live system. Reads are on by default. Writes stay off until you name a person who must approve.",[233,959,960,962],{},[236,961,274],{}," The company record of what ran, who approved, and what changed. When the operator leaves, the record does not leave with their laptop.",[233,964,965,968,969,973],{},[236,966,967],{},"Secure by Design."," ",[204,970,972],{"href":971},"https:\u002F\u002Fwww.cisa.gov\u002Fsecurebydesign","CISA’s programme"," about who owns security outcomes. When you run software yourself, you are the operator.",[225,975,295],{"id":294},[201,977,978,979,982],{},"You also own the upkeep. A laptop agent with mailbox and company files is a privileged identity you operate. ",[204,980,981],{"href":971},"CISA’s Secure by Design"," framing is blunt: if you chose to run the agent yourself, you own the outcome. Logging, least privilege, and a named signer are yours to provide. Hermes will not invent them because it learned your email voice.",[201,984,985],{},"On Hermes, the trail of a finance journal is a conversation on a machine, a how-to note the agent wrote for itself, maybe an email it sent. That may be enough for one person. It is not enough for an auditor who asks, “Show me the approved version.” Self-hosting means you keep the secrets and pay the model bill. It does not mean the company has a release process. Hosting choice is not company governance.",[201,987,988,989,991,992,994],{},"On Nimbus, finance opens a ",[204,990,357],{"href":815},". The wiki states the journal policy. The ledger connector is read-only until a human releases the write. The ",[204,993,23],{"href":681}," keeps the brief, the draft, the signer, and the change. When the operator leaves, the record does not leave with their laptop. Nimbus is not trying to learn your email voice. It is trying to make sure finance cannot post a journal without a named signer, and that the analysis still exists in two years.",[201,996,997,998,1001],{},"If three people each run Hermes, you have three memories and no shared playbook. One of them will eventually put a production password in a local file “just for this week.” That is not a Hermes flaw. It is what happens when a personal agent becomes the unofficial company system — ",[204,999,1000],{"href":458},"shadow AI"," with a better memory. Auto-promoting a note from one user’s Hermes into company-wide write access is how a friendly shortcut spreads.",[201,1003,1004],{},"A laptop is convenient and easy to lose. A server you run yourself is always on and a bigger target if it is reachable from the internet. Neither gives you a named signer on a journal. Hermes can live in many chat apps; reach is not a control system. The more surfaces the agent sits on, the more ways a privileged identity can be messaged.",[201,1006,1007,1008,1011,1012,1016],{},"Role by role: a founder or researcher who will patch the install gets a personal agent that improves at ",[578,1009,1010],{},"their"," workflows — that is the fit. IT should not be asked to standardise the company on a fleet of laptops and a spreadsheet of who is supposed to update them. Finance cannot treat a how-to note on a desktop as the journal policy. Security inherits CISA’s point: you ran it, you own the outcome. A COO who needs an org chart for those personal agents is already in a different product — see ",[204,1013,1015],{"href":1014},"\u002Fblog\u002Fnimbus-vs-paperclip\u002F","Nimbus vs Paperclip",". Operators who need the business to remember should not wait for each person’s Hermes to become unofficial infrastructure.",[201,1018,1019,1020,1022],{},"The job split is clean if you keep it clean. Hermes (or something like ",[204,1021,207],{"href":777},") as a personal assistant with no production passwords. Nimbus as the place that work is submitted, approved, and remembered. Feed drafts into a workstream the way you would feed a human’s first pass. Do not let Hermes hold the write password.",[225,1024,1026],{"id":1025},"when-hermes-is-a-better-fit","When Hermes is a better fit",[201,1028,1029,1030,1033],{},"Choose Hermes when you are the user, you want an agent that improves at ",[578,1031,1032],{},"your"," workflows, and the blast radius is your own files. Choose it to feel what a persistent agent is like before you operationalise anything. Choose it in a lab that will never touch customer systems.",[201,1035,1036,1037,385],{},"Do not standardise the company on Hermes and call it an AI programme. You will recreate a pile of personal agents and a spreadsheet of who is supposed to patch them. If you need an org chart for those agents, that is a different product again — see ",[204,1038,1015],{"href":1014},[201,1040,1041],{},"You can use both. Hermes as a personal assistant with no production passwords. Nimbus as the place that work is submitted, approved, and remembered. That coexistence only works if credentials stay out of the personal agent. A brilliant personal memory with a production login is still a privileged identity on a laptop.",[225,1043,350],{"id":349},[201,1045,1046],{},"Nimbus is a company system, not a program you install on one person’s machine. You log in the way you log into any other business app. You do not hope they remember to patch it.",[201,1048,1049,1052,1053,1055,1056,1059],{},[204,1050,1051],{"href":309},"Connectors"," link to the tools you already run — the ledger, the CRM, the shared drive. ",[204,1054,39],{"href":384}," is the release path: agents draft, humans release, the graph keeps the decision. The ",[204,1057,305],{"href":1058},"\u002Fproduct\u002Fwiki\u002F"," is where “how we do this” lives after a human has reviewed it — not a private note the agent wrote for itself. You still review the vendor. You do not become the platform team for every laptop.",[201,1061,735,1062,385],{},[204,1063,380],{"href":379},[225,1065,389],{"id":388},[391,1067,1069],{"id":1068},"is-nimbus-built-on-hermes","Is Nimbus built on Hermes?",[201,1071,1072],{},"No. They sit on different layers. Nimbus may call some of the same models Hermes uses. That is the model market, not a fork.",[391,1074,1076],{"id":1075},"can-hermes-be-our-company-ai-platform","Can Hermes be our company AI platform?",[201,1078,1079],{},"Only if you are willing to staff the upkeep: identity, secrets, updates, and a release process for anything that touches production. At that point you are building a company system by hand. Most operators should not.",[391,1081,1083],{"id":1082},"where-should-the-how-we-do-this-notes-live","Where should the “how we do this” notes live?",[201,1085,1086],{},"On a personal agent, or as playbooks in the Nimbus wiki after a human has reviewed them. Auto-promoting a note from one user’s Hermes into company-wide write access is how a friendly shortcut spreads.",[391,1088,1090],{"id":1089},"can-we-run-hermes-beside-nimbus","Can we run Hermes beside Nimbus?",[201,1092,1093],{},"Yes — as a personal assistant with no production credentials. Feed drafts into a Nimbus workstream the way you would feed a human’s first pass. Do not let Hermes hold the write password.",[391,1095,1097],{"id":1096},"does-it-matter-if-hermes-runs-on-a-laptop-or-a-server","Does it matter if Hermes runs on a laptop or a server?",[201,1099,1100],{},"A laptop is convenient and easy to lose. A server you run yourself is always on and a bigger target if it is reachable from the internet. Neither gives you a named signer on a journal. Hosting choice is not company governance.",[391,1102,1104],{"id":1103},"how-is-hermes-different-from-openclaw","How is Hermes different from OpenClaw?",[201,1106,418,1107,385],{},[204,1108,778],{"href":777},[391,1110,1112],{"id":1111},"who-owns-security-if-we-allow-hermes","Who owns security if we allow Hermes?",[201,1114,1115],{},"You do. CISA’s Secure by Design framing is about who owns security outcomes. When you run the software yourself, you are the operator. Logging, least privilege, and a named signer are yours to provide. Nimbus does not remove the need to review a vendor; it does mean you are not the platform team for every laptop.",[391,1117,1119],{"id":1118},"what-happens-when-the-person-who-ran-hermes-leaves","What happens when the person who ran Hermes leaves?",[201,1121,1122],{},"Their personal memory leaves with them, unless you copied it somewhere else. That is the product working as designed. If the business needed the journal policy, the signer, and the change, those should already have lived in a workstream and a graph — not on a machine that is about to be wiped.",[225,1124,453],{"id":452},[201,1126,1127,460,1131,464,1133,385],{},[204,1128,1130],{"href":1129},"\u002Fblog\u002Fwhat-is-institutional-memory-in-enterprise-ai\u002F","What is institutional memory in enterprise AI",[204,1132,463],{"href":317},[204,1134,778],{"href":777},[225,1136,470],{"id":469},[230,1138,1139,1143,1148,1152],{},[233,1140,1141],{},[204,1142,894],{"href":893},[233,1144,1145],{},[204,1146,1147],{"href":917},"Hermes Agent on GitHub",[233,1149,1150],{},[204,1151,913],{"href":912},[233,1153,1154],{},[204,1155,1156],{"href":971},"CISA Secure by Design",{"title":169,"searchDepth":170,"depth":170,"links":1158},[1159,1160,1161,1162,1163,1173,1174],{"id":227,"depth":170,"text":228},{"id":294,"depth":170,"text":295},{"id":1025,"depth":170,"text":1026},{"id":349,"depth":170,"text":350},{"id":388,"depth":170,"text":389,"children":1164},[1165,1166,1167,1168,1169,1170,1171,1172],{"id":1068,"depth":502,"text":1069},{"id":1075,"depth":502,"text":1076},{"id":1082,"depth":502,"text":1083},{"id":1089,"depth":502,"text":1090},{"id":1096,"depth":502,"text":1097},{"id":1103,"depth":502,"text":1104},{"id":1111,"depth":502,"text":1112},{"id":1118,"depth":502,"text":1119},{"id":452,"depth":170,"text":453},{"id":469,"depth":170,"text":470},"Hermes Agent is a self-hosted personal agent that learns how you work; Nimbus remembers how the company works when that person is away.",{"eyebrow":515,"title":1177},"A person who learns you, or a company that remembers",[1179,1182,1185],{"question":1180,"answer":1181},"What is Hermes?","A self-hosted personal agent that learns how you work.",{"question":1183,"answer":1184},"What happens when that person is away?","The learning stays with them. Nimbus is built to remember how the company works after they leave.",{"question":1186,"answer":1187},"Who should use which?","A personal agent for an individual's workflow. Nimbus when the job, the approval, and the record belong to the business.","\u002Fblog\u002Fnimbus-vs-hermes",{"title":883,"description":1175},"blog\u002Fnimbus-vs-hermes",[529,1192,1193,1194,1195],"hermes","nous-research","open-source-agents","memory","HdCVpUJz_7IRtFD2udziizCMoL1rL5kPy0JeMTpa13s",{"fold":1198,"id":1202,"title":1203,"archived":163,"authors":164,"badge":164,"body":1204,"date":164,"definedTerm":164,"department":164,"description":169,"extension":172,"eyebrow":164,"faqHeader":164,"faqs":164,"footerBand":1208,"headline":164,"image":164,"industry":164,"jobType":164,"listed":131,"location":164,"navigation":131,"openRoles":164,"pageLayout":164,"path":1212,"relatedHeading":164,"seo":1213,"series":164,"sitemap":163,"status":164,"stem":1214,"subhead":164,"tags":164,"video":164,"whyJoin":164,"workplaceType":164,"__hash__":1215},{"headline":1199,"description":1200,"primaryLabel":8,"primaryTo":1201,"secondaryLabel":553,"secondaryTo":12},"Run frontier AI your business actually owns.","Governed workstreams, 3,000+ integrations, and a proprietary knowledge graph. Start on Free.","\u002Fsignup?plan=free","content\u002Fshared\u002Fcta.md","Site CTAs",{"type":166,"value":1205,"toc":1206},[],{"title":169,"searchDepth":170,"depth":170,"links":1207},[],{"headline":1209,"description":1210,"primaryLabel":8,"primaryTo":1201,"secondaryLabel":1211,"secondaryTo":85},"See what governed AI looks like on your stack.","Connect your tools, run a workstream, and keep every decision on your ledger. Start on Free.","Talk to our team","\u002Fshared\u002Fcta",{"title":1203,"description":169},"shared\u002Fcta","eYqahyaPnbp8GKrWpoORbZdtmkWmgHr5F61ZHOnb8sY",1792999477658]