[{"data":1,"prerenderedAt":1215},["ShallowReactive",2],{"site-nav-content":3,"blog:/blog/nimbus-vs-microsoft-copilot":163,"blog-index-copy":544,"blog:/blog/nimbus-vs-microsoft-copilot:surround":565,"hiring-banner-content":1184,"site-cta-content":1196},{"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":532,"department":150,"description":533,"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":534,"relatedHeading":150,"seo":535,"series":536,"sitemap":115,"status":150,"stem":537,"subhead":150,"tags":538,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":543},"content/blog/nimbus-vs-microsoft-copilot.md","Nimbus vs Microsoft Copilot: Great Inside Office, or Work That Leaves Microsoft?",{"label":167,"10|authors":168},"Comparisons",[169],{"name":170,"to":120},"Nimbus Research",{"type":152,"value":172,"toc":513},[173,196,199,223,228,284,288,294,306,313,325,328,331,335,338,341,344,347,350,354,365,380,387,393,397,402,405,409,412,416,421,425,432,436,439,443,446,450,457,461,467,471,484,488],[174,175,176,177,187,188,195],"p",{},"“Copilot” is several products that get collapsed in procurement. ",[178,179,180],"strong",{},[181,182,186],"a",{"href":183,"rel":184},"https://www.microsoft.com/microsoft-365/copilot",[185],"nofollow","Microsoft 365 Copilot"," is the add-on that sits in Word, Excel, PowerPoint, Outlook, Teams, and the Copilot app. ",[178,189,190],{},[181,191,194],{"href":192,"rel":193},"https://learn.microsoft.com/en-us/microsoft-copilot-studio/",[185],"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,197,198],{},"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,200,201,202,207,208,213,214,218,219,222],{},"Microsoft’s own ",[181,203,206],{"href":204,"rel":205},"https://learn.microsoft.com/en-us/microsoft-365/copilot/microsoft-365-copilot-architecture",[185],"architecture"," and ",[181,209,212],{"href":210,"rel":211},"https://learn.microsoft.com/en-us/copilot/microsoft-365/microsoft-365-copilot-privacy",[185],"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 ",[215,216,217],"em",{},"find and draft inside Microsoft",", not ",[215,220,221],{},"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.",[224,225,227],"h2",{"id":226},"words-youll-hear","Words you’ll hear",[229,230,231,238,244,250,256,262,272,278],"ul",{},[232,233,234,237],"li",{},[178,235,236],{},"Microsoft 365 Copilot."," The per-person assistant inside Office, grounded in Microsoft Graph — mail, files, meetings, and sites the user can already access.",[232,239,240,243],{},[178,241,242],{},"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.",[232,245,246,249],{},[178,247,248],{},"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.",[232,251,252,255],{},[178,253,254],{},"Agent Builder."," Simple agents inside Copilot, grounded in Microsoft 365 content, for information workers.",[232,257,258,261],{},[178,259,260],{},"Workstream."," In Nimbus, a shared workspace for one job across systems that are not all Microsoft.",[232,263,264,267,268,271],{},[178,265,266],{},"Write-back."," Changing a live system. You ",[215,269,270],{},"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.",[232,273,274,277],{},[178,275,276],{},"Lifecycle Graph."," The causal record of who approved, what changed, and what the next team should believe.",[232,279,280,283],{},[178,281,282],{},"E5."," Microsoft 365 E5 explains identity, compliance, and Office. It does not explain CRM write-back or a company work ledger.",[224,285,287],{"id":286},"why-the-difference-matters","Why the difference matters",[174,289,290,291,293],{},"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 ",[215,292,270],{}," 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,295,296,297,301,302,305],{},"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 ",[181,298,300],{"href":299},"what-is-an-ai-workstream","workstream"," puts those in one job. Records stay read-only until someone who is allowed to approve writes actually does. The ",[181,303,23],{"href":304},"what-is-a-lifecycle-graph"," keeps the release.",[174,307,308,312],{},[181,309,311],{"href":310},"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,314,315,316,320,321,324],{},"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 ",[181,317,319],{"href":318},"what-is-write-back-governance","write-back",", choosing models across vendors, or a Lifecycle Graph. Standardise Copilot where Microsoft’s graph ",[215,322,323],{},"is"," the work. Standardise an operating layer where the business process is the work.",[174,326,327],{},"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,329,330],{},"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.",[224,332,334],{"id":333},"when-microsoft-copilot-is-a-better-fit","When Microsoft Copilot is a better fit",[174,336,337],{},"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,339,340],{},"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,342,343],{},"SharePoint agents are Q&A on sites. Use them for findability. Do not use them as the operating model.",[174,345,346],{},"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,348,349],{},"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.",[224,351,353],{"id":352},"how-this-shows-up-in-nimbus","How this shows up in Nimbus",[174,355,356,357,360,361,364],{},"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 ",[181,358,359],{"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 ",[181,362,363],{"href":84},"sales",", not as a reason Copilot and Nimbus are the same product.",[174,366,367,368,371,372,375,376,379],{},"The ",[181,369,370],{"href":28},"wiki"," is what the company asserts. ",[181,373,374],{"href":51},"Connectors"," are scoped per workspace. Agents get the systems you attached, in the mode you allowed, until a human releases a write. ",[181,377,378],{"href":20},"Agent teams"," finish the work Copilot handed you after the recap.",[174,381,382,383,386],{},"You can ",[181,384,385],{"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,388,389,390,392],{},"See ",[181,391,39],{"href":40},".",[224,394,396],{"id":395},"questions-people-actually-ask","Questions people actually ask",[398,399,401],"h3",{"id":400},"does-nimbus-replace-microsoft-365-copilot","Does Nimbus replace Microsoft 365 Copilot?",[174,403,404],{},"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.",[398,406,408],{"id":407},"does-copilot-studio-replace-nimbus","Does Copilot Studio replace Nimbus?",[174,410,411],{},"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.",[398,413,415],{"id":414},"can-nimbus-use-azure-openai-or-microsoft-models","Can Nimbus use Azure OpenAI or Microsoft models?",[174,417,418,419,364],{},"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 ",[181,420,363],{"href":84},[398,422,424],{"id":423},"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,426,427,428,320,430,324],{},"E5 explains identity, compliance, and Office. It does not explain CRM ",[181,429,319],{"href":318},[215,431,323],{},[398,433,435],{"id":434},"do-we-need-a-microsoft-partner-to-get-nimbus-running","Do we need a Microsoft partner to get Nimbus running?",[174,437,438],{},"No. You can set it up yourselves. Copilot Studio at organisational scale usually is not self-serve in the same way.",[398,440,442],{"id":441},"can-we-keep-copilot-and-put-salesforce-writes-in-nimbus","Can we keep Copilot and put Salesforce writes in Nimbus?",[174,444,445],{},"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.",[398,447,449],{"id":448},"who-should-own-which-product","Who should own which product?",[174,451,452,453,456],{},"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 ",[215,454,455],{},"and"," write gates. A single “we already pay Microsoft” owner will stretch Copilot into an operating layer.",[398,458,460],{"id":459},"what-about-glean-if-we-already-have-copilot","What about Glean if we already have Copilot?",[174,462,463,464,392],{},"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 ",[181,465,466],{"href":310},"Nimbus vs Glean",[224,468,470],{"id":469},"related-reading","Related reading",[174,472,473,476,477,481,482,392],{},[181,474,475],{"href":318},"What is write-back governance",", ",[181,478,480],{"href":479},"what-is-an-enterprise-ai-operating-system","What is an enterprise AI operating system",", and ",[181,483,466],{"href":310},[224,485,487],{"id":486},"sources","Sources",[229,489,490,495,501,507],{},[232,491,492],{},[181,493,186],{"href":183,"rel":494},[185],[232,496,497],{},[181,498,500],{"href":210,"rel":499},[185],"Microsoft 365 Copilot privacy",[232,502,503],{},[181,504,506],{"href":204,"rel":505},[185],"Microsoft 365 Copilot architecture",[232,508,509],{},[181,510,512],{"href":192,"rel":511},[185],"Microsoft Copilot Studio",{"title":155,"searchDepth":156,"depth":156,"links":514},[515,516,517,518,519,530,531],{"id":226,"depth":156,"text":227},{"id":286,"depth":156,"text":287},{"id":333,"depth":156,"text":334},{"id":352,"depth":156,"text":353},{"id":395,"depth":156,"text":396,"children":520},[521,523,524,525,526,527,528,529],{"id":400,"depth":522,"text":401},3,{"id":407,"depth":522,"text":408},{"id":414,"depth":522,"text":415},{"id":423,"depth":522,"text":424},{"id":434,"depth":522,"text":435},{"id":441,"depth":522,"text":442},{"id":448,"depth":522,"text":449},{"id":459,"depth":522,"text":460},{"id":469,"depth":156,"text":470},{"id":486,"depth":156,"text":487},"2026-08-17","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":165,"description":533},"comparisons","blog/nimbus-vs-microsoft-copilot",[536,539,540,541,542],"microsoft-copilot","copilot-studio","m365","enterprise-ai","w0CEv3bGzwk5Xggxh5z3sCk2Gdyqblmgq31V3RjJB0o",{"hero":545,"id":547,"title":548,"archived":149,"authors":150,"badge":150,"body":549,"date":150,"department":150,"description":553,"extension":158,"eyebrow":554,"faqHeader":150,"faqs":150,"footerBand":555,"headline":150,"image":150,"industry":150,"jobType":150,"listed":149,"location":150,"navigation":115,"openRoles":150,"pageLayout":150,"path":60,"relatedHeading":561,"seo":562,"series":150,"sitemap":115,"status":150,"stem":563,"subhead":150,"tags":150,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":564},{"filename":546},"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":550,"toc":551},[],{"title":155,"searchDepth":156,"depth":156,"links":552},[],"Deep dives into pre-cognitive intelligence, sentient enterprises, and the evolving landscape of AI-driven business transformation.","Latest Research",{"headline":556,"description":557,"primaryLabel":558,"primaryTo":559,"secondaryLabel":560,"secondaryTo":12},"Stay at the frontier.","Subscribe for product updates and new insights.","Subscribe","/newsletter","Explore the platform","More research",{"title":548,"description":553},"blog/index","eK1RCXdDW8nfLSyKRXGB1mJm9FAmhAO6GWXwNKOMNVE",[566,868],{"id":567,"title":568,"archived":149,"authors":150,"badge":569,"body":572,"date":532,"department":150,"description":858,"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":859,"relatedHeading":150,"seo":860,"series":536,"sitemap":115,"status":150,"stem":861,"subhead":150,"tags":862,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":867},"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":570},[571],{"name":170,"to":120},{"type":152,"value":573,"toc":840},[574,582,590,599,601,660,662,665,676,682,685,688,691,695,698,701,709,711,721,724,731,739,741,745,748,752,755,759,762,766,772,776,779,783,786,790,793,797,800,802,812,814],[174,575,576,581],{},[181,577,580],{"href":578,"rel":579},"https://docs.openclaw.ai/",[185],"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,583,584,585,589],{},"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 ",[181,586,588],{"href":578,"rel":587},[185],"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,591,592,593,598],{},"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 ",[181,594,597],{"href":595,"rel":596},"https://github.com/openclaw/openclaw",[185],"code"," is public. Self-hosting is the point. Self-hosting is also the obligation.",[224,600,227],{"id":226},[229,602,603,609,615,621,626,632,637,642],{},[232,604,605,608],{},[178,606,607],{},"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.",[232,610,611,614],{},[178,612,613],{},"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.",[232,616,617,620],{},[178,618,619],{},"Skills / marketplace."," Community packs that add tools. Treat a marketplace install like unreviewed software with credentials.",[232,622,623,625],{},[178,624,260],{}," In Nimbus, a shared workspace for one job — people, tools, budget, and a finish line.",[232,627,628,631],{},[178,629,630],{},"Agent teams."," AI specialists grouped like departments, assigned to the workstream.",[232,633,634,636],{},[178,635,266],{}," 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.",[232,638,639,641],{},[178,640,276],{}," The record of what ran, who approved, and what changed.",[232,643,644,647,648,653,654,659],{},[178,645,646],{},"Secure AI system development."," The ",[181,649,652],{"href":650,"rel":651},"https://www.ncsc.gov.uk/collection/guidelines-secure-ai-system-development",[185],"UK NCSC guidelines",", issued jointly with ",[181,655,658],{"href":656,"rel":657},"https://www.cisa.gov/news-events/news/dhs-cisa-and-uk-ncsc-release-joint-guidelines-secure-ai-system-development",[185],"CISA",": logging, monitoring, and not exposing sensitive data — whether you built the system or stitched it from tools and APIs.",[224,661,287],{"id":286},[174,663,664],{},"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,666,667,668,671,672,675],{},"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 ",[181,669,370],{"href":670},"what-is-a-company-wiki-for-ai-agents"," product and no Lifecycle Graph of releases. Nimbus memory is three places you can show a colleague: the wiki (what we claim), ",[181,673,674],{"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,677,678,679,681],{},"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 ",[181,680,319],{"href":318}," 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,683,684],{},"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,686,687],{},"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,689,690],{},"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.",[224,692,694],{"id":693},"when-openclaw-is-a-better-fit","When OpenClaw is a better fit",[174,696,697],{},"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,699,700],{},"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,702,703,704,708],{},"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 ",[181,705,707],{"href":706},"nimbus-vs-hermes","Hermes",": a personal assistant you look after. OpenClaw maximises channels. Hermes maximises skills and personal memory. Neither is a company OS.",[224,710,353],{"id":352},[174,712,713,714,716,717,720],{},"Nimbus is the application you log into at work. Operators do not babysit a process on a server. They open a ",[181,715,300],{"href":32}," with ",[181,718,719],{"href":20},"agent teams"," and connectors.",[174,722,723],{},"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,725,726,727,730],{},"Nimbus ",[181,728,729],{"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,732,733,734,207,737,392],{},"See the ",[181,735,736],{"href":12},"overview",[181,738,39],{"href":40},[224,740,396],{"id":395},[398,742,744],{"id":743},"is-openclaw-a-nimbus-competitor","Is OpenClaw a Nimbus competitor?",[174,746,747],{},"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.",[398,749,751],{"id":750},"can-we-put-openclaw-in-front-of-nimbus","Can we put OpenClaw in front of Nimbus?",[174,753,754],{},"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.",[398,756,758],{"id":757},"what-about-a-hosted-or-cloud-openclaw","What about a hosted or cloud OpenClaw?",[174,760,761],{},"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.",[398,763,765],{"id":764},"is-openclaw-the-same-as-hermes","Is OpenClaw the same as Hermes?",[174,767,768,769,392],{},"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 ",[181,770,771],{"href":706},"Nimbus vs Hermes",[398,773,775],{"id":774},"does-self-hosting-mean-we-can-skip-logging-and-monitoring","Does self-hosting mean we can skip logging and monitoring?",[174,777,778],{},"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.",[398,780,782],{"id":781},"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,784,785],{},"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.”",[398,787,789],{"id":788},"who-owns-an-internal-openclaw","Who owns an internal OpenClaw?",[174,791,792],{},"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.",[398,794,796],{"id":795},"how-do-we-retire-a-viral-bot-without-a-fight","How do we retire a viral bot without a fight?",[174,798,799],{},"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.",[224,801,470],{"id":469},[174,803,804,476,808,481,810,392],{},[181,805,807],{"href":806},"what-is-shadow-ai","What is shadow AI",[181,809,475],{"href":318},[181,811,771],{"href":706},[224,813,487],{"id":486},[229,815,816,822,828,834],{},[232,817,818],{},[181,819,821],{"href":578,"rel":820},[185],"OpenClaw documentation",[232,823,824],{},[181,825,827],{"href":595,"rel":826},[185],"OpenClaw on GitHub",[232,829,830],{},[181,831,833],{"href":650,"rel":832},[185],"UK NCSC, Guidelines for secure AI system development",[232,835,836],{},[181,837,839],{"href":656,"rel":838},[185],"CISA and UK NCSC joint guidelines for secure AI system development",{"title":155,"searchDepth":156,"depth":156,"links":841},[842,843,844,845,846,856,857],{"id":226,"depth":156,"text":227},{"id":286,"depth":156,"text":287},{"id":693,"depth":156,"text":694},{"id":352,"depth":156,"text":353},{"id":395,"depth":156,"text":396,"children":847},[848,849,850,851,852,853,854,855],{"id":743,"depth":522,"text":744},{"id":750,"depth":522,"text":751},{"id":757,"depth":522,"text":758},{"id":764,"depth":522,"text":765},{"id":774,"depth":522,"text":775},{"id":781,"depth":522,"text":782},{"id":788,"depth":522,"text":789},{"id":795,"depth":522,"text":796},{"id":469,"depth":156,"text":470},{"id":486,"depth":156,"text":487},"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":568,"description":858},"blog/nimbus-vs-openclaw",[536,863,864,865,866],"openclaw","clawdbot","self-hosted-agents","governance","R2AG8WRzElJpkIZT-mTrXwUibawfvKwSz-PJQiq-YgU",{"id":869,"title":870,"archived":149,"authors":150,"badge":871,"body":874,"date":532,"department":150,"description":1174,"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":1175,"relatedHeading":150,"seo":1176,"series":536,"sitemap":115,"status":150,"stem":1177,"subhead":150,"tags":1178,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":1183},"content/blog/nimbus-vs-hermes.md","Nimbus vs Hermes: A Personal Agent That Learns You, or a System That Remembers the Business?",{"label":167,"10|authors":872},[873],{"name":170,"to":120},{"type":152,"value":875,"toc":1156},[876,892,895,909,911,967,969,977,980,989,996,999,1011,1018,1022,1029,1034,1037,1039,1042,1053,1058,1060,1064,1067,1071,1074,1078,1081,1085,1088,1092,1095,1099,1104,1108,1111,1115,1118,1120,1130,1132],[174,877,878,883,884,887,888,891],{},[181,879,882],{"href":880,"rel":881},"https://hermes-agent.nousresearch.com/",[185],"Hermes Agent"," is built to get better at ",[215,885,886],{},"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 ",[215,889,890],{},"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.",[174,893,894],{},"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.",[174,896,897,898,903,904,908],{},"Hermes is a real step beyond a chat window that forgets you every morning. It is an open-source personal agent from ",[181,899,902],{"href":900,"rel":901},"https://nousresearch.com/",[185],"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 ",[181,905,597],{"href":906,"rel":907},"https://github.com/nousresearch/hermes-agent/",[185]," 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.",[224,910,227],{"id":226},[229,912,913,923,928,934,939,945,950,955],{},[232,914,915,918,919,922],{},[178,916,917],{},"Hermes Agent."," An open-source personal agent from ",[181,920,902],{"href":900,"rel":921},[185],". You install it on a Mac, Windows, or Linux machine. It can also live in Telegram, Discord, Slack, WhatsApp, Signal, email, or a terminal.",[232,924,925,927],{},[178,926,613],{}," You run the software. You pay the model bill. You keep the secrets. You are the operator.",[232,929,930,933],{},[178,931,932],{},"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.",[232,935,936,938],{},[178,937,260],{}," In Nimbus, a shared workspace for one job — not a private conversation on a machine.",[232,940,941,944],{},[178,942,943],{},"Wiki."," Official playbooks: how we book a journal, who may sign, what “done” means. Agents read that, not a private note on a desktop.",[232,946,947,949],{},[178,948,266],{}," Changing a live system. Reads are on by default. Writes stay off until you name a person who must approve.",[232,951,952,954],{},[178,953,276],{}," The company record of what ran, who approved, and what changed. When the operator leaves, the record does not leave with their laptop.",[232,956,957,960,961,966],{},[178,958,959],{},"Secure by Design."," ",[181,962,965],{"href":963,"rel":964},"https://www.cisa.gov/securebydesign",[185],"CISA’s programme"," about who owns security outcomes. When you run software yourself, you are the operator.",[224,968,287],{"id":286},[174,970,971,972,976],{},"You also own the upkeep. A laptop agent with mailbox and company files is a privileged identity you operate. ",[181,973,975],{"href":963,"rel":974},[185],"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.",[174,978,979],{},"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.",[174,981,982,983,985,986,988],{},"On Nimbus, finance opens a ",[181,984,300],{"href":299},". The wiki states the journal policy. The ledger connector is read-only until a human releases the write. The ",[181,987,23],{"href":304}," 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.",[174,990,991,992,995],{},"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 — ",[181,993,994],{"href":806},"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.",[174,997,998],{},"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.",[174,1000,1001,1002,1005,1006,1010],{},"Role by role: a founder or researcher who will patch the install gets a personal agent that improves at ",[215,1003,1004],{},"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 ",[181,1007,1009],{"href":1008},"nimbus-vs-paperclip","Nimbus vs Paperclip",". Operators who need the business to remember should not wait for each person’s Hermes to become unofficial infrastructure.",[174,1012,1013,1014,1017],{},"The job split is clean if you keep it clean. Hermes (or something like ",[181,1015,580],{"href":1016},"nimbus-vs-openclaw",") 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.",[224,1019,1021],{"id":1020},"when-hermes-is-a-better-fit","When Hermes is a better fit",[174,1023,1024,1025,1028],{},"Choose Hermes when you are the user, you want an agent that improves at ",[215,1026,1027],{},"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.",[174,1030,1031,1032,392],{},"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 ",[181,1033,1009],{"href":1008},[174,1035,1036],{},"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.",[224,1038,353],{"id":352},[174,1040,1041],{},"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.",[174,1043,1044,1046,1047,1049,1050,1052],{},[181,1045,374],{"href":51}," link to the tools you already run — the ledger, the CRM, the shared drive. ",[181,1048,39],{"href":40}," is the release path: agents draft, humans release, the graph keeps the decision. The ",[181,1051,370],{"href":28}," 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.",[174,1054,1055,1056,392],{},"Start at the ",[181,1057,736],{"href":12},[224,1059,396],{"id":395},[398,1061,1063],{"id":1062},"is-nimbus-built-on-hermes","Is Nimbus built on Hermes?",[174,1065,1066],{},"No. They sit on different layers. Nimbus may call some of the same models Hermes uses. That is the model market, not a fork.",[398,1068,1070],{"id":1069},"can-hermes-be-our-company-ai-platform","Can Hermes be our company AI platform?",[174,1072,1073],{},"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.",[398,1075,1077],{"id":1076},"where-should-the-how-we-do-this-notes-live","Where should the “how we do this” notes live?",[174,1079,1080],{},"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.",[398,1082,1084],{"id":1083},"can-we-run-hermes-beside-nimbus","Can we run Hermes beside Nimbus?",[174,1086,1087],{},"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.",[398,1089,1091],{"id":1090},"does-it-matter-if-hermes-runs-on-a-laptop-or-a-server","Does it matter if Hermes runs on a laptop or a server?",[174,1093,1094],{},"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.",[398,1096,1098],{"id":1097},"how-is-hermes-different-from-openclaw","How is Hermes different from OpenClaw?",[174,1100,768,1101,392],{},[181,1102,1103],{"href":1016},"Nimbus vs OpenClaw",[398,1105,1107],{"id":1106},"who-owns-security-if-we-allow-hermes","Who owns security if we allow Hermes?",[174,1109,1110],{},"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.",[398,1112,1114],{"id":1113},"what-happens-when-the-person-who-ran-hermes-leaves","What happens when the person who ran Hermes leaves?",[174,1116,1117],{},"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.",[224,1119,470],{"id":469},[174,1121,1122,476,1126,481,1128,392],{},[181,1123,1125],{"href":1124},"what-is-institutional-memory-in-enterprise-ai","What is institutional memory in enterprise AI",[181,1127,475],{"href":318},[181,1129,1103],{"href":1016},[224,1131,487],{"id":486},[229,1133,1134,1139,1145,1150],{},[232,1135,1136],{},[181,1137,882],{"href":880,"rel":1138},[185],[232,1140,1141],{},[181,1142,1144],{"href":906,"rel":1143},[185],"Hermes Agent on GitHub",[232,1146,1147],{},[181,1148,902],{"href":900,"rel":1149},[185],[232,1151,1152],{},[181,1153,1155],{"href":963,"rel":1154},[185],"CISA Secure by Design",{"title":155,"searchDepth":156,"depth":156,"links":1157},[1158,1159,1160,1161,1162,1172,1173],{"id":226,"depth":156,"text":227},{"id":286,"depth":156,"text":287},{"id":1020,"depth":156,"text":1021},{"id":352,"depth":156,"text":353},{"id":395,"depth":156,"text":396,"children":1163},[1164,1165,1166,1167,1168,1169,1170,1171],{"id":1062,"depth":522,"text":1063},{"id":1069,"depth":522,"text":1070},{"id":1076,"depth":522,"text":1077},{"id":1083,"depth":522,"text":1084},{"id":1090,"depth":522,"text":1091},{"id":1097,"depth":522,"text":1098},{"id":1106,"depth":522,"text":1107},{"id":1113,"depth":522,"text":1114},{"id":469,"depth":156,"text":470},{"id":486,"depth":156,"text":487},"Hermes Agent is a self-hosted personal agent that learns how you work; Nimbus remembers how the company works when that person is away.","/blog/nimbus-vs-hermes",{"title":870,"description":1174},"blog/nimbus-vs-hermes",[536,1179,1180,1181,1182],"hermes","nous-research","open-source-agents","memory","bOOe-srYHxqaxWVNoXUnSpNT7JEjUHGwtgJj_YPpGjA",{"enabled":149,"message":1185,"linkLabel":78,"linkHref":79,"id":1186,"title":1187,"archived":149,"authors":150,"badge":150,"body":1188,"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":1192,"relatedHeading":150,"seo":1193,"series":150,"sitemap":115,"status":150,"stem":1194,"subhead":150,"tags":150,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":1195},"We're hiring! Join the team building the Sentient Enterprise.","content/shared/hiring.md","Hiring banner",{"type":152,"value":1189,"toc":1190},[],{"title":155,"searchDepth":156,"depth":156,"links":1191},[],"/shared/hiring",{"title":1187,"description":155},"shared/hiring","-6bioYD7lKYokGUVU3ff4hHTvB-sDyOMuCptKHnojfk",{"fold":1197,"id":1201,"title":1202,"archived":149,"authors":150,"badge":150,"body":1203,"date":150,"department":150,"description":155,"extension":158,"eyebrow":150,"faqHeader":150,"faqs":150,"footerBand":1207,"headline":150,"image":150,"industry":150,"jobType":150,"listed":149,"location":150,"navigation":115,"openRoles":150,"pageLayout":150,"path":1211,"relatedHeading":150,"seo":1212,"series":150,"sitemap":115,"status":150,"stem":1213,"subhead":150,"tags":150,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":1214},{"headline":1198,"description":1199,"primaryLabel":8,"primaryTo":1200,"secondaryLabel":560,"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":1204,"toc":1205},[],{"title":155,"searchDepth":156,"depth":156,"links":1206},[],{"headline":1208,"description":1209,"primaryLabel":8,"primaryTo":1200,"secondaryLabel":1210,"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":1202,"description":155},"shared/cta","YHK6Fb8AvCPR1zZq7R_xiXUG0hwhP5UxHA8Ix52JQp4",1787194070930]