[{"data":1,"prerenderedAt":1216},["ShallowReactive",2],{"site-nav-content":3,"blog:/blog/nimbus-vs-openclaw":163,"blog-index-copy":502,"blog:/blog/nimbus-vs-openclaw:surround":523,"hiring-banner-content":1185,"site-cta-content":1197},{"header":4,"productNav":9,"nav":42,"footer":61,"askAI":116,"id":147,"title":148,"archived":149,"authors":150,"badge":150,"body":151,"date":150,"department":150,"description":155,"extension":158,"eyebrow":150,"faqHeader":150,"faqs":150,"footerBand":150,"headline":150,"image":150,"industry":150,"jobType":150,"listed":149,"location":150,"navigation":115,"openRoles":150,"pageLayout":150,"path":159,"relatedHeading":150,"seo":160,"series":150,"sitemap":115,"status":150,"stem":161,"subhead":150,"tags":150,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":162},{"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","/overview","Seven layers. One closed loop.",{"label":15,"to":16,"description":17},"Conflux","/product/conflux","Where your team, workstreams, and agents meet.",{"label":19,"to":20,"description":21},"Agent Teams","/product/agent-teams","Specialist teams - governed from day one.",{"label":23,"to":24,"description":25},"Lifecycle Graph","/product/lifecycle-graph","Intelligence that compounds across every interaction.",{"label":27,"to":28,"description":29},"Company Wiki","/product/wiki","Playbooks and policies where expertise stays.",{"label":31,"to":32,"description":33},"Workstreams","/product/workstreams","From brief to signed-off deliverable on one canvas.",{"label":35,"to":36,"description":37},"Perception Console","/product/perception","Ask your whole business in plain English.",{"label":39,"to":40,"description":41},"Governance","/product/governance","Frontier AI you can actually sign off on.",[43,46,49,52,55,58],{"label":44,"to":45},"Models","/models",{"label":47,"to":48},"Pricing","/pricing",{"label":50,"to":51},"Integrations","/integrations",{"label":53,"to":54},"Security","/security",{"label":56,"to":57},"Partners","/partners",{"label":59,"to":60},"Insights","/blog",{"productHeading":5,"companyHeading":62,"legalHeading":63,"docsLabel":64,"docsUrl":65,"statementLines":66,"copyright":69,"companyLinks":70,"legalLinks":85,"socialLinks":95,"bottomLinks":105},"Company","Legal","Docs","https://docs.gonimbus.ai",[67,68],"Stop training someone else's model.","Control your AI.","© 2026 Nimbus Intelligence, Inc. All rights reserved.",[71,72,73,74,75,77,80,83],{"label":47,"to":48},{"label":50,"to":51},{"label":53,"to":54},{"label":59,"to":60},{"label":76,"to":57},"Partner Program",{"label":78,"to":79},"Careers","/careers",{"label":81,"to":82},"System status","/status",{"label":7,"to":84},"/contact",[86,89,92],{"label":87,"to":88},"Terms of Service","/terms",{"label":90,"to":91},"Privacy Policy","/privacy",{"label":93,"to":94},"Compliance","/compliance",[96,99,102],{"label":97,"href":98},"LinkedIn","https://www.linkedin.com/company/gonimbusai/",{"label":100,"href":101},"X","https://x.com/gonimbusai",{"label":103,"href":104},"Instagram","https://www.instagram.com/gonimbus_ai/",[106,108,110,111,112],{"label":107,"to":88},"Terms",{"label":109,"to":91},"Privacy",{"label":93,"to":94},{"label":81,"to":82},{"label":113,"to":114,"external":115},"LLMs.txt","/llms.txt",true,{"text":117,"prompt":118},"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":119,"platforms":121},{" Summarize the highlights from Nimbus's website":120},"https://gonimbus.ai",[122,127,132,137,142],{"name":123,"label":124,"icon":125,"hrefPrefix":126},"chatgpt","ChatGPT","simple-icons:openai","https://chatgpt.com/?prompt=",{"name":128,"label":129,"icon":130,"hrefPrefix":131},"perplexity","Perplexity","mdi:magnify","https://www.perplexity.ai/search/new?q=",{"name":133,"label":134,"icon":135,"hrefPrefix":136},"grok","Grok","simple-icons:x","https://x.com/i/grok?text=",{"name":138,"label":139,"icon":140,"hrefPrefix":141},"claude","Claude","simple-icons:anthropic","https://claude.ai/new?q=",{"name":143,"label":144,"icon":145,"hrefPrefix":146},"google-ai","Google AI","simple-icons:google","https://www.google.com/search?udm=50&aep=11&q=","content/shared/nav.md","Site navigation",false,null,{"type":152,"value":153,"toc":154},"minimark",[],{"title":155,"searchDepth":156,"depth":156,"links":157},"",2,[],"md","/shared/nav",{"title":148,"description":155},"shared/nav","p6IsjEfjcrwkjwvGsPcuEkpoJSeUn2vJXPTxLWQfw9M",{"id":164,"title":165,"archived":149,"authors":150,"badge":166,"body":171,"date":490,"department":150,"description":491,"extension":158,"eyebrow":150,"faqHeader":150,"faqs":150,"footerBand":150,"headline":150,"image":150,"industry":150,"jobType":150,"listed":149,"location":150,"navigation":115,"openRoles":150,"pageLayout":150,"path":492,"relatedHeading":150,"seo":493,"series":494,"sitemap":115,"status":150,"stem":495,"subhead":150,"tags":496,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":501},"content/blog/nimbus-vs-openclaw.md","Nimbus vs OpenClaw: A Chat Bot on Your Phone, or a Company Workspace with Approvals?",{"label":167,"10|authors":168},"Comparisons",[169],{"name":170,"to":120},"Nimbus Research",{"type":152,"value":172,"toc":471},[173,184,192,201,206,271,275,278,290,298,301,304,307,311,314,317,325,329,340,343,350,360,364,369,372,376,379,383,386,390,396,400,403,407,410,414,417,421,424,428,441,445],[174,175,176,183],"p",{},[177,178,182],"a",{"href":179,"rel":180},"https://docs.openclaw.ai/",[181],"nofollow","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.",[174,185,186,187,191],{},"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 ",[177,188,190],{"href":179,"rel":189},[181],"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.",[174,193,194,195,200],{},"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 ",[177,196,199],{"href":197,"rel":198},"https://github.com/openclaw/openclaw",[181],"code"," is public. Self-hosting is the point. Self-hosting is also the obligation.",[202,203,205],"h2",{"id":204},"words-youll-hear","Words you’ll hear",[207,208,209,217,223,229,235,241,247,253],"ul",{},[210,211,212,216],"li",{},[213,214,215],"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.",[210,218,219,222],{},[213,220,221],{},"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.",[210,224,225,228],{},[213,226,227],{},"Skills / marketplace."," Community packs that add tools. Treat a marketplace install like unreviewed software with credentials.",[210,230,231,234],{},[213,232,233],{},"Workstream."," In Nimbus, a shared workspace for one job — people, tools, budget, and a finish line.",[210,236,237,240],{},[213,238,239],{},"Agent teams."," AI specialists grouped like departments, assigned to the workstream.",[210,242,243,246],{},[213,244,245],{},"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.",[210,248,249,252],{},[213,250,251],{},"Lifecycle Graph."," The record of what ran, who approved, and what changed.",[210,254,255,258,259,264,265,270],{},[213,256,257],{},"Secure AI system development."," The ",[177,260,263],{"href":261,"rel":262},"https://www.ncsc.gov.uk/collection/guidelines-secure-ai-system-development",[181],"UK NCSC guidelines",", issued jointly with ",[177,266,269],{"href":267,"rel":268},"https://www.cisa.gov/news-events/news/dhs-cisa-and-uk-ncsc-release-joint-guidelines-secure-ai-system-development",[181],"CISA",": logging, monitoring, and not exposing sensitive data — whether you built the system or stitched it from tools and APIs.",[202,272,274],{"id":273},"why-the-difference-matters","Why the difference matters",[174,276,277],{},"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.",[174,279,280,281,285,286,289],{},"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 ",[177,282,284],{"href":283},"what-is-a-company-wiki-for-ai-agents","wiki"," product and no Lifecycle Graph of releases. Nimbus memory is three places you can show a colleague: the wiki (what we claim), ",[177,287,288],{"href":51},"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?”",[174,291,292,293,297],{},"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 ",[177,294,296],{"href":295},"what-is-write-back-governance","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.",[174,299,300],{},"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.",[174,302,303],{},"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.",[174,305,306],{},"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.",[202,308,310],{"id":309},"when-openclaw-is-a-better-fit","When OpenClaw is a better fit",[174,312,313],{},"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.",[174,315,316],{},"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.",[174,318,319,320,324],{},"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 ",[177,321,323],{"href":322},"nimbus-vs-hermes","Hermes",": a personal assistant you look after. OpenClaw maximises channels. Hermes maximises skills and personal memory. Neither is a company OS.",[202,326,328],{"id":327},"how-this-shows-up-in-nimbus","How this shows up in Nimbus",[174,330,331,332,335,336,339],{},"Nimbus is the application you log into at work. Operators do not babysit a process on a server. They open a ",[177,333,334],{"href":32},"workstream"," with ",[177,337,338],{"href":20},"agent teams"," and connectors.",[174,341,342],{},"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.",[174,344,345,346,349],{},"Nimbus ",[177,347,348],{"href":51},"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.",[174,351,352,353,356,357,359],{},"See the ",[177,354,355],{"href":12},"overview"," and ",[177,358,39],{"href":40},".",[202,361,363],{"id":362},"questions-people-actually-ask","Questions people actually ask",[365,366,368],"h3",{"id":367},"is-openclaw-a-nimbus-competitor","Is OpenClaw a Nimbus competitor?",[174,370,371],{},"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.",[365,373,375],{"id":374},"can-we-put-openclaw-in-front-of-nimbus","Can we put OpenClaw in front of Nimbus?",[174,377,378],{},"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.",[365,380,382],{"id":381},"what-about-a-hosted-or-cloud-openclaw","What about a hosted or cloud OpenClaw?",[174,384,385],{},"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.",[365,387,389],{"id":388},"is-openclaw-the-same-as-hermes","Is OpenClaw the same as Hermes?",[174,391,392,393,359],{},"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 ",[177,394,395],{"href":322},"Nimbus vs Hermes",[365,397,399],{"id":398},"does-self-hosting-mean-we-can-skip-logging-and-monitoring","Does self-hosting mean we can skip logging and monitoring?",[174,401,402],{},"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.",[365,404,406],{"id":405},"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?",[174,408,409],{},"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.”",[365,411,413],{"id":412},"who-owns-an-internal-openclaw","Who owns an internal OpenClaw?",[174,415,416],{},"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.",[365,418,420],{"id":419},"how-do-we-retire-a-viral-bot-without-a-fight","How do we retire a viral bot without a fight?",[174,422,423],{},"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.",[202,425,427],{"id":426},"related-reading","Related reading",[174,429,430,434,435,438,439,359],{},[177,431,433],{"href":432},"what-is-shadow-ai","What is shadow AI",", ",[177,436,437],{"href":295},"What is write-back governance",", and ",[177,440,395],{"href":322},[202,442,444],{"id":443},"sources","Sources",[207,446,447,453,459,465],{},[210,448,449],{},[177,450,452],{"href":179,"rel":451},[181],"OpenClaw documentation",[210,454,455],{},[177,456,458],{"href":197,"rel":457},[181],"OpenClaw on GitHub",[210,460,461],{},[177,462,464],{"href":261,"rel":463},[181],"UK NCSC, Guidelines for secure AI system development",[210,466,467],{},[177,468,470],{"href":267,"rel":469},[181],"CISA and UK NCSC joint guidelines for secure AI system development",{"title":155,"searchDepth":156,"depth":156,"links":472},[473,474,475,476,477,488,489],{"id":204,"depth":156,"text":205},{"id":273,"depth":156,"text":274},{"id":309,"depth":156,"text":310},{"id":327,"depth":156,"text":328},{"id":362,"depth":156,"text":363,"children":478},[479,481,482,483,484,485,486,487],{"id":367,"depth":480,"text":368},3,{"id":374,"depth":480,"text":375},{"id":381,"depth":480,"text":382},{"id":388,"depth":480,"text":389},{"id":398,"depth":480,"text":399},{"id":405,"depth":480,"text":406},{"id":412,"depth":480,"text":413},{"id":419,"depth":480,"text":420},{"id":426,"depth":156,"text":427},{"id":443,"depth":156,"text":444},"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.","/blog/nimbus-vs-openclaw",{"title":165,"description":491},"comparisons","blog/nimbus-vs-openclaw",[494,497,498,499,500],"openclaw","clawdbot","self-hosted-agents","governance","R2AG8WRzElJpkIZT-mTrXwUibawfvKwSz-PJQiq-YgU",{"hero":503,"id":505,"title":506,"archived":149,"authors":150,"badge":150,"body":507,"date":150,"department":150,"description":511,"extension":158,"eyebrow":512,"faqHeader":150,"faqs":150,"footerBand":513,"headline":150,"image":150,"industry":150,"jobType":150,"listed":149,"location":150,"navigation":115,"openRoles":150,"pageLayout":150,"path":60,"relatedHeading":519,"seo":520,"series":150,"sitemap":115,"status":150,"stem":521,"subhead":150,"tags":150,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":522},{"filename":504},"u2221455217_Flat_design_of_a_futuristic_minimalist_landscape__5d589295-cdea-4ea9-a262-be766881accf_1.png","content/blog/index.md","Exploring the future of intelligence.",{"type":152,"value":508,"toc":509},[],{"title":155,"searchDepth":156,"depth":156,"links":510},[],"Deep dives into pre-cognitive intelligence, sentient enterprises, and the evolving landscape of AI-driven business transformation.","Latest Research",{"headline":514,"description":515,"primaryLabel":516,"primaryTo":517,"secondaryLabel":518,"secondaryTo":12},"Stay at the frontier.","Subscribe for product updates and new insights.","Subscribe","/newsletter","Explore the platform","More research",{"title":506,"description":511},"blog/index","eK1RCXdDW8nfLSyKRXGB1mJm9FAmhAO6GWXwNKOMNVE",[524,845],{"id":525,"title":526,"archived":149,"authors":150,"badge":527,"body":530,"date":490,"department":150,"description":836,"extension":158,"eyebrow":150,"faqHeader":150,"faqs":150,"footerBand":150,"headline":150,"image":150,"industry":150,"jobType":150,"listed":149,"location":150,"navigation":115,"openRoles":150,"pageLayout":150,"path":837,"relatedHeading":150,"seo":838,"series":494,"sitemap":115,"status":150,"stem":839,"subhead":150,"tags":840,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":844},"content/blog/nimbus-vs-paperclip.md","Nimbus vs Paperclip: An Org Chart for Other People’s Bots, or a Product a COO Can Log Into?",{"label":167,"10|authors":528},[529],{"name":170,"to":120},{"type":152,"value":531,"toc":818},[532,540,552,571,573,634,636,639,645,658,661,664,671,675,682,685,688,691,693,696,705,710,712,716,719,723,726,730,733,737,740,744,754,758,763,767,770,774,777,779,791,793],[174,533,534,539],{},[177,535,538],{"href":536,"rel":537},"https://paperclip.ing/",[181],"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.",[174,541,542,543,547,548,551],{},"Paperclip is multiplayer for ",[544,545,546],"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 ",[544,549,550],{},"in",", not the scheduler that wakes them.",[174,553,554,555,559,560,356,565,570],{},"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 ",[177,556,199],{"href":557,"rel":558},"https://github.com/paperclipai/paperclip",[181]," 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. ",[177,561,564],{"href":562,"rel":563},"https://docs.crewai.com/",[181],"CrewAI",[177,566,569],{"href":567,"rel":568},"https://arxiv.org/abs/2308.00352",[181],"MetaGPT"," are the research-and-builder names for that orchestration category. Paperclip is that category as a product you hire into.",[202,572,205],{"id":204},[207,574,575,585,598,604,609,614,620,629],{},[210,576,577,580,581,584],{},[213,578,579],{},"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 ",[177,582,199],{"href":557,"rel":583},[181]," is public; you can run it yourself.",[210,586,587,590,591,356,594,597],{},[213,588,589],{},"Orchestration."," Coordinating several agents. ",[177,592,564],{"href":562,"rel":593},[181],[177,595,569],{"href":567,"rel":596},[181]," are the research-and-builder names for that category. Paperclip is that category as a product you hire into.",[210,599,600,603],{},[213,601,602],{},"Agent budget."," Cap the worker, warn at 80%, pause at 100%. Necessary cost control. Not the same as stopping a bad write.",[210,605,606,608],{},[213,607,233],{}," In Nimbus, a shared workspace for one job — the ticket a non-engineer can actually run.",[210,610,611,613],{},[213,612,239],{}," AI specialists grouped like departments: finance, go-to-market, ops. You are not wiring a cluster of other people’s bots on day one.",[210,615,616,619],{},[213,617,618],{},"Wiki."," Official playbooks those teams must respect.",[210,621,622,624,625,628],{},[213,623,245],{}," Changing a live system. Paperclip’s FAQ is frank: it governs what agents do ",[544,626,627],{},"to Paperclip"," (hiring, strategy). Your agents are your own, and you secure them however you want.",[210,630,631,633],{},[213,632,251],{}," What ran, who approved, and what changed — so next quarter’s team does not relitigate the exception from Slack archaeology.",[202,635,274],{"id":273},[174,637,638],{},"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.",[174,640,641,642,644],{},"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 (metered in NTUs — work credits). The extra loop is change control: which system a write hits, who signs, where the artefact is stored. See ",[177,643,500],{"href":40},". Cap-at-100% is necessary. It is not the same as stopping a bad write.",[174,646,647,648,650,651,654,655,657],{},"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 ",[177,649,288],{"href":51}," plus the ",[177,652,23],{"href":653},"what-is-a-lifecycle-graph"," 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 ",[544,656,627],{}," (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.",[174,659,660],{},"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.",[174,662,663],{},"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.",[174,665,666,667,670],{},"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 ",[544,668,669],{},"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.",[202,672,674],{"id":673},"when-paperclip-is-a-better-fit","When Paperclip is a better fit",[174,676,677,678,681],{},"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 ",[544,679,680],{},"is"," building an agent OS and you need that scheduler while you build the rest.",[174,683,684],{},"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.",[174,686,687],{},"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.",[174,689,690],{},"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.",[202,692,328],{"id":327},[174,694,695],{},"Nimbus is the application layer a Head of Ops opens without assembling a roster of third-party bots on day one.",[174,697,698,699,356,701,704],{},"You attach connectors under a read-only default. Humans release writes. You get specialist teams and a canvas, then you attach systems. See ",[177,700,338],{"href":20},[177,702,703],{"href":32},"workstreams",". Spend is capped in NTUs so a long-running job cannot silently burn the month — and the write still waits for a signer.",[174,706,707,708,359],{},"Start at the ",[177,709,355],{"href":12},[202,711,363],{"id":362},[365,713,715],{"id":714},"is-nimbus-paperclip-with-a-nicer-screen","Is Nimbus “Paperclip with a nicer screen”?",[174,717,718],{},"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.",[365,720,722],{"id":721},"can-paperclip-orchestrate-nimbus","Can Paperclip orchestrate Nimbus?",[174,724,725],{},"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.",[365,727,729],{"id":728},"open-source-vs-a-hosted-product-which-lock-in-is-worse","Open source vs a hosted product — which lock-in is worse?",[174,731,732],{},"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.",[365,734,736],{"id":735},"do-we-need-paperclip-if-we-only-have-one-agent","Do we need Paperclip if we only have one agent?",[174,738,739],{},"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.",[365,741,743],{"id":742},"how-does-paperclip-relate-to-openclaw-and-hermes","How does Paperclip relate to OpenClaw and Hermes?",[174,745,746,747,356,751,753],{},"OpenClaw and Hermes are employees. Paperclip is the org chart. Nimbus is the company plus the office. See ",[177,748,750],{"href":749},"nimbus-vs-openclaw","Nimbus vs OpenClaw",[177,752,395],{"href":322},". Buying all three still does not give you a Lifecycle Graph.",[365,755,757],{"id":756},"can-we-migrate-from-paperclip-to-nimbus","Can we migrate from Paperclip to Nimbus?",[174,759,760,761,670],{},"Treat the workers as prototypes. Recreate the ",[544,762,669],{},[365,764,766],{"id":765},"does-a-budget-cap-replace-write-back-governance","Does a budget cap replace write-back governance?",[174,768,769],{},"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.",[365,771,773],{"id":772},"who-should-run-paperclip-if-we-keep-it","Who should run Paperclip if we keep it?",[174,775,776],{},"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.",[202,778,427],{"id":426},[174,780,781,434,785,438,789,359],{},[177,782,784],{"href":783},"what-is-multi-agent-ai","What is multi-agent AI",[177,786,788],{"href":787},"what-is-an-ai-workstream","What is an AI workstream",[177,790,750],{"href":749},[202,792,444],{"id":443},[207,794,795,800,806,812],{},[210,796,797],{},[177,798,538],{"href":536,"rel":799},[181],[210,801,802],{},[177,803,805],{"href":557,"rel":804},[181],"Paperclip on GitHub",[210,807,808],{},[177,809,811],{"href":562,"rel":810},[181],"CrewAI documentation",[210,813,814],{},[177,815,817],{"href":567,"rel":816},[181],"Hong et al., MetaGPT (arXiv:2308.00352)",{"title":155,"searchDepth":156,"depth":156,"links":819},[820,821,822,823,824,834,835],{"id":204,"depth":156,"text":205},{"id":273,"depth":156,"text":274},{"id":673,"depth":156,"text":674},{"id":327,"depth":156,"text":328},{"id":362,"depth":156,"text":363,"children":825},[826,827,828,829,830,831,832,833],{"id":714,"depth":480,"text":715},{"id":721,"depth":480,"text":722},{"id":728,"depth":480,"text":729},{"id":735,"depth":480,"text":736},{"id":742,"depth":480,"text":743},{"id":756,"depth":480,"text":757},{"id":765,"depth":480,"text":766},{"id":772,"depth":480,"text":773},{"id":426,"depth":156,"text":427},{"id":443,"depth":156,"text":444},"Paperclip organises the agents you already run; Nimbus is the finished workplace where departments share one job — not twelve bots nobody owns.","/blog/nimbus-vs-paperclip",{"title":526,"description":836},"blog/nimbus-vs-paperclip",[494,841,842,843,500],"paperclip","multi-agent","orchestration","9v34C0UEdjpM1myjS2p6Ck-9_OOxTapIYCAT9v4fM2I",{"id":846,"title":847,"archived":149,"authors":150,"badge":848,"body":851,"date":490,"department":150,"description":1175,"extension":158,"eyebrow":150,"faqHeader":150,"faqs":150,"footerBand":150,"headline":150,"image":150,"industry":150,"jobType":150,"listed":149,"location":150,"navigation":115,"openRoles":150,"pageLayout":150,"path":1176,"relatedHeading":150,"seo":1177,"series":494,"sitemap":115,"status":150,"stem":1178,"subhead":150,"tags":1179,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":1184},"content/blog/nimbus-vs-microsoft-copilot.md","Nimbus vs Microsoft Copilot: Great Inside Office, or Work That Leaves Microsoft?",{"label":167,"10|authors":849},[850],{"name":170,"to":120},{"type":152,"value":852,"toc":1157},[853,872,875,897,899,950,952,958,967,974,983,986,989,993,996,999,1002,1005,1008,1010,1021,1035,1042,1047,1049,1053,1056,1060,1063,1067,1072,1076,1083,1087,1090,1094,1097,1101,1108,1112,1118,1120,1130,1132],[174,854,855,856,863,864,871],{},"“Copilot” is several products that get collapsed in procurement. ",[213,857,858],{},[177,859,862],{"href":860,"rel":861},"https://www.microsoft.com/microsoft-365/copilot",[181],"Microsoft 365 Copilot"," is the add-on that sits in Word, Excel, PowerPoint, Outlook, Teams, and the Copilot app. ",[213,865,866],{},[177,867,870],{"href":868,"rel":869},"https://learn.microsoft.com/en-us/microsoft-copilot-studio/",[181],"Copilot Studio"," is the low-code environment for multi-step agents beyond Microsoft. Nimbus is for work that leaves Microsoft — Salesforce, NetSuite, and the rest of the stack where money actually moves.",[174,873,874],{},"Nobody else will be as good at “summarise this thread and the attached deck” inside Outlook. That recap is tenant productivity. Updating forty opportunities in Salesforce is company operations. If your programme starts with “every knowledge worker has a Copilot licence,” you are specifying Microsoft. If it starts with “RevOps will not allow unapproved Salesforce writes from an agent, and we need a record of those releases,” you are specifying Nimbus. You can keep both. Using Nimbus does not mean ripping Copilot out of Office.",[174,876,877,878,356,883,888,889,892,893,896],{},"Microsoft’s own ",[177,879,882],{"href":880,"rel":881},"https://learn.microsoft.com/en-us/microsoft-365/copilot/microsoft-365-copilot-architecture",[181],"architecture",[177,884,887],{"href":885,"rel":886},"https://learn.microsoft.com/en-us/copilot/microsoft-365/microsoft-365-copilot-privacy",[181],"privacy"," docs are the source: Copilot is grounded in Microsoft Graph — mail, files, meetings, and sites the user can already access — and prompts, responses, and Graph data are not used to train foundation LLMs. That is the right privacy story for find-and-draft inside Microsoft. It still describes ",[544,890,891],{},"find and draft inside Microsoft",", not ",[544,894,895],{},"sign a write in Salesforce",". Agent Builder covers simple agents inside Copilot, grounded in Microsoft 365 content, for information workers. Studio is the step that leaves Graph.",[202,898,205],{"id":204},[207,900,901,907,913,919,925,930,939,944],{},[210,902,903,906],{},[213,904,905],{},"Microsoft 365 Copilot."," The per-person assistant inside Office, grounded in Microsoft Graph — mail, files, meetings, and sites the user can already access.",[210,908,909,912],{},[213,910,911],{},"Microsoft Graph."," The map of what this person can already open in Microsoft 365. Copilot should not leak a file they cannot open in SharePoint.",[210,914,915,918],{},[213,916,917],{},"Copilot Studio."," Low-code agents with branching, approvals, and connectors to Salesforce, SAP, ServiceNow, and custom APIs. You can publish to Teams. Metering is often credits or messages on top of licences.",[210,920,921,924],{},[213,922,923],{},"Agent Builder."," Simple agents inside Copilot, grounded in Microsoft 365 content, for information workers.",[210,926,927,929],{},[213,928,233],{}," In Nimbus, a shared workspace for one job across systems that are not all Microsoft.",[210,931,932,934,935,938],{},[213,933,245],{}," Changing a live system. You ",[544,936,937],{},"can"," update Salesforce from Studio. The update is a flow-shaped side effect in Microsoft’s world. In Nimbus it is a quoted release with a named signer.",[210,940,941,943],{},[213,942,251],{}," The causal record of who approved, what changed, and what the next team should believe.",[210,945,946,949],{},[213,947,948],{},"E5."," Microsoft 365 E5 explains identity, compliance, and Office. It does not explain CRM write-back or a company work ledger.",[202,951,274],{"id":273},[174,953,954,955,957],{},"Studio agents that leave Graph for other connectors inherit a different permission story: connector logins, rules that stop sensitive files leaking, environment strategy. IT knows this is where Copilot programmes stall. You ",[544,956,937],{}," update Salesforce from Studio. The update is a flow-shaped side effect in Microsoft’s world. In Nimbus it is a quoted release with a named signer. Approvals in a Power Platform artefact are real. They are not a Lifecycle Graph of the job across departments.",[174,959,960,961,963,964,966],{},"In Nimbus, the scarce resource is control of work across systems that are not all Microsoft. The quarterly review deck may live in SharePoint. The opportunities live in Salesforce. The revenue number finance trusts may live in NetSuite. A ",[177,962,334],{"href":787}," puts those in one job. Records stay read-only until someone who is allowed to approve writes actually does. The ",[177,965,23],{"href":653}," keeps the release.",[174,968,969,973],{},[177,970,972],{"href":971},"nimbus-vs-glean","Glean","-class search and Copilot-class Graph grounding solve findability. Nimbus assumes you can already find the policy. The failure is that AI work does not land in a signed-off artefact. Purpose limitation is easier to explain when a recruiting workstream cannot see finance forecasts. A Copilot licence that sees “whatever this user can already open” is a different design — Microsoft’s Graph design, by intention. That design is correct inside Office. It is a wide blast radius if the same licence is treated as the operating model for every system the user can already open.",[174,975,976,977,979,980,982],{},"Lock-in is the honest trade. Copilot deepens Microsoft 365. Nimbus is lock-in of a different kind: the work loop and the graph. If most proprietary work is already in Microsoft, Copilot’s return is easier. If most money-moving systems are Salesforce, NetSuite, and specialist software, Copilot Studio becomes a connector project — and Nimbus was designed as that project plus the record. E5 explains identity, compliance, and Office. It does not explain CRM ",[177,978,296],{"href":295},", choosing models across vendors, or a Lifecycle Graph. Standardise Copilot where Microsoft’s graph ",[544,981,680],{}," the work. Standardise an operating layer where the business process is the work.",[174,984,985],{},"Role by role: a knowledge worker in Word, Excel, Outlook, and Teams wants the side pane — nobody else will recap the thread and the attached deck as well. IT owns Graph, licences, and often Studio as a Power Platform artefact: a helpdesk bot, an HR FAQ, a Teams helper. RevOps lives in Salesforce, not in SharePoint; a Studio connector to Salesforce is a flow-shaped side effect, not a company release. Finance trusts NetSuite, not the recap. Security will like Graph grounding and the privacy docs, and still ask who signed a CRM write. A CIO who already bought E5 should use Copilot where Microsoft’s graph is the work — and still not pretend E5 bought an operating layer.",[174,987,988],{},"SharePoint agents are Q&A on sites. Use them for findability. Do not use them as the operating model. Keep Copilot in Office. Put the job that leaves Microsoft in a workstream.",[202,990,992],{"id":991},"when-microsoft-copilot-is-a-better-fit","When Microsoft Copilot is a better fit",[174,994,995],{},"Choose Microsoft 365 Copilot when the job is knowledge-worker productivity in Word, Excel, Outlook, and Teams, and Microsoft’s own files and mail are the corpus.",[174,997,998],{},"Choose Copilot Studio when the agent is a Power Platform artefact IT will own — a helpdesk bot, an HR FAQ, a Teams helper. Metering is often credits or messages on top of licences; budget that as a Microsoft programme, not as a Nimbus substitute.",[174,1000,1001],{},"SharePoint agents are Q&A on sites. Use them for findability. Do not use them as the operating model.",[174,1003,1004],{},"Do not choose Copilot as a stealth operating layer for non-Microsoft systems. You will spend a year on connector reviews and still lack workstreams, specialist teams, and a Lifecycle Graph.",[174,1006,1007],{},"Keep Copilot in Office. Using Nimbus does not mean ripping it out. A coherent coexistence: Copilot for tenant productivity; Nimbus for jobs that also touch Salesforce, NetSuite, and the rest of the stack. Drafts can move from a recap into a workstream. Write credentials for money-moving systems should sit in Nimbus connector scopes, not in a Studio flow by default.",[202,1009,328],{"id":327},[174,1011,1012,1013,1016,1017,1020],{},"Nimbus does not try to be the Word side pane. It does not assume the only intelligence in the company is whatever Microsoft licensed this quarter. See ",[177,1014,1015],{"href":45},"models",". Routing includes not throwing the most powerful model at a simple lookup. Treat Microsoft-hosted models as infrastructure options in an enterprise conversation with ",[177,1018,1019],{"href":84},"sales",", not as a reason Copilot and Nimbus are the same product.",[174,1022,1023,1024,1026,1027,1030,1031,1034],{},"The ",[177,1025,284],{"href":28}," is what the company asserts. ",[177,1028,1029],{"href":51},"Connectors"," are scoped per workspace. Agents get the systems you attached, in the mode you allowed, until a human releases a write. ",[177,1032,1033],{"href":20},"Agent teams"," finish the work Copilot handed you after the recap.",[174,1036,1037,1038,1041],{},"You can ",[177,1039,1040],{"href":12},"set Nimbus up yourselves",". Copilot programmes at organisational scale are famous for implementation. Keep Copilot in Office; do not staff a consulting partner to invent an operating layer.",[174,1043,1044,1045,359],{},"See ",[177,1046,39],{"href":40},[202,1048,363],{"id":362},[365,1050,1052],{"id":1051},"does-nimbus-replace-microsoft-365-copilot","Does Nimbus replace Microsoft 365 Copilot?",[174,1054,1055],{},"No. Keep Copilot in Office. Nimbus does not try to be the Word side pane. It tries to be the place agent teams finish work that leaves Microsoft.",[365,1057,1059],{"id":1058},"does-copilot-studio-replace-nimbus","Does Copilot Studio replace Nimbus?",[174,1061,1062],{},"Only if “a few Power Platform agents” is the entire AI programme. Studio can be shared inside the Microsoft tenant. It does not replace Nimbus as a governed execution layer with a company wiki and an operational ledger.",[365,1064,1066],{"id":1065},"can-nimbus-use-azure-openai-or-microsoft-models","Can Nimbus use Azure OpenAI or Microsoft models?",[174,1068,1069,1070,1020],{},"Nimbus routes models for quality, cost, and latency — including not throwing the most powerful model at a simple lookup. Treat Microsoft-hosted models as infrastructure options in an enterprise conversation with ",[177,1071,1019],{"href":84},[365,1073,1075],{"id":1074},"why-not-standardise-on-copilot-because-we-already-buy-microsoft-365-e5","Why not standardise on Copilot because we already buy Microsoft 365 E5?",[174,1077,1078,1079,979,1081,982],{},"E5 explains identity, compliance, and Office. It does not explain CRM ",[177,1080,296],{"href":295},[544,1082,680],{},[365,1084,1086],{"id":1085},"do-we-need-a-microsoft-partner-to-get-nimbus-running","Do we need a Microsoft partner to get Nimbus running?",[174,1088,1089],{},"No. You can set it up yourselves. Copilot Studio at organisational scale usually is not self-serve in the same way.",[365,1091,1093],{"id":1092},"can-we-keep-copilot-and-put-salesforce-writes-in-nimbus","Can we keep Copilot and put Salesforce writes in Nimbus?",[174,1095,1096],{},"Yes. That is the intended coexistence. Recap in Outlook; finish in a workstream. Do not let a Studio Salesforce connector become the unofficial write path “because we already had an approval step in the flow.” Quote the change, name the signer, store the outcome.",[365,1098,1100],{"id":1099},"who-should-own-which-product","Who should own which product?",[174,1102,1103,1104,1107],{},"IT typically owns Microsoft 365 Copilot and Studio: licences, Graph, Power Platform environments. Line operators own Nimbus workstreams that touch Salesforce, NetSuite, and specialist systems. Security reviews Graph grounding ",[544,1105,1106],{},"and"," write gates. A single “we already pay Microsoft” owner will stretch Copilot into an operating layer.",[365,1109,1111],{"id":1110},"what-about-glean-if-we-already-have-copilot","What about Glean if we already have Copilot?",[174,1113,1114,1115,359],{},"Copilot respects Microsoft permissions inside Microsoft. Glean searches across many apps, including Microsoft, and respects source permissions. You may still need Glean if SharePoint search is not enough, and still need Nimbus if neither is an operating layer. See ",[177,1116,1117],{"href":971},"Nimbus vs Glean",[202,1119,427],{"id":426},[174,1121,1122,434,1124,438,1128,359],{},[177,1123,437],{"href":295},[177,1125,1127],{"href":1126},"what-is-an-enterprise-ai-operating-system","What is an enterprise AI operating system",[177,1129,1117],{"href":971},[202,1131,444],{"id":443},[207,1133,1134,1139,1145,1151],{},[210,1135,1136],{},[177,1137,862],{"href":860,"rel":1138},[181],[210,1140,1141],{},[177,1142,1144],{"href":885,"rel":1143},[181],"Microsoft 365 Copilot privacy",[210,1146,1147],{},[177,1148,1150],{"href":880,"rel":1149},[181],"Microsoft 365 Copilot architecture",[210,1152,1153],{},[177,1154,1156],{"href":868,"rel":1155},[181],"Microsoft Copilot Studio",{"title":155,"searchDepth":156,"depth":156,"links":1158},[1159,1160,1161,1162,1163,1173,1174],{"id":204,"depth":156,"text":205},{"id":273,"depth":156,"text":274},{"id":991,"depth":156,"text":992},{"id":327,"depth":156,"text":328},{"id":362,"depth":156,"text":363,"children":1164},[1165,1166,1167,1168,1169,1170,1171,1172],{"id":1051,"depth":480,"text":1052},{"id":1058,"depth":480,"text":1059},{"id":1065,"depth":480,"text":1066},{"id":1074,"depth":480,"text":1075},{"id":1085,"depth":480,"text":1086},{"id":1092,"depth":480,"text":1093},{"id":1099,"depth":480,"text":1100},{"id":1110,"depth":480,"text":1111},{"id":426,"depth":156,"text":427},{"id":443,"depth":156,"text":444},"Microsoft 365 Copilot lives in Word, Outlook, and Teams; Nimbus is for jobs that also touch Salesforce, NetSuite, and the rest of the business.","/blog/nimbus-vs-microsoft-copilot",{"title":847,"description":1175},"blog/nimbus-vs-microsoft-copilot",[494,1180,1181,1182,1183],"microsoft-copilot","copilot-studio","m365","enterprise-ai","w0CEv3bGzwk5Xggxh5z3sCk2Gdyqblmgq31V3RjJB0o",{"enabled":149,"message":1186,"linkLabel":78,"linkHref":79,"id":1187,"title":1188,"archived":149,"authors":150,"badge":150,"body":1189,"date":150,"department":150,"description":155,"extension":158,"eyebrow":150,"faqHeader":150,"faqs":150,"footerBand":150,"headline":150,"image":150,"industry":150,"jobType":150,"listed":149,"location":150,"navigation":115,"openRoles":150,"pageLayout":150,"path":1193,"relatedHeading":150,"seo":1194,"series":150,"sitemap":115,"status":150,"stem":1195,"subhead":150,"tags":150,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":1196},"We're hiring! Join the team building the Sentient Enterprise.","content/shared/hiring.md","Hiring banner",{"type":152,"value":1190,"toc":1191},[],{"title":155,"searchDepth":156,"depth":156,"links":1192},[],"/shared/hiring",{"title":1188,"description":155},"shared/hiring","-6bioYD7lKYokGUVU3ff4hHTvB-sDyOMuCptKHnojfk",{"fold":1198,"id":1202,"title":1203,"archived":149,"authors":150,"badge":150,"body":1204,"date":150,"department":150,"description":155,"extension":158,"eyebrow":150,"faqHeader":150,"faqs":150,"footerBand":1208,"headline":150,"image":150,"industry":150,"jobType":150,"listed":149,"location":150,"navigation":115,"openRoles":150,"pageLayout":150,"path":1212,"relatedHeading":150,"seo":1213,"series":150,"sitemap":115,"status":150,"stem":1214,"subhead":150,"tags":150,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":1215},{"headline":1199,"description":1200,"primaryLabel":8,"primaryTo":1201,"secondaryLabel":518,"secondaryTo":12},"Run frontier AI your business actually owns.","Governed agent swarms, 2,000+ integrations, and a knowledge graph that stays inside your walls. Free 7-day trial.","/checkout","content/shared/cta.md","Site CTAs",{"type":152,"value":1205,"toc":1206},[],{"title":155,"searchDepth":156,"depth":156,"links":1207},[],{"headline":1209,"description":1210,"primaryLabel":8,"primaryTo":1201,"secondaryLabel":1211,"secondaryTo":84},"See what governed AI looks like on your stack.","Connect your tools, run a workstream, and keep every decision on your ledger - free for 7 days.","Talk to our team","/shared/cta",{"title":1203,"description":155},"shared/cta","YHK6Fb8AvCPR1zZq7R_xiXUG0hwhP5UxHA8Ix52JQp4",1787194071142]