[{"data":1,"prerenderedAt":1227},["ShallowReactive",2],{"site-nav-content":3,"blog:/blog/nimbus-vs-hermes":163,"blog-index-copy":524,"blog:/blog/nimbus-vs-hermes:surround":545,"hiring-banner-content":1196,"site-cta-content":1208},{"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":512,"department":150,"description":513,"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":514,"relatedHeading":150,"seo":515,"series":516,"sitemap":115,"status":150,"stem":517,"subhead":150,"tags":518,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":523},"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":168},"Comparisons",[169],{"name":170,"to":120},"Nimbus Research",{"type":152,"value":172,"toc":493},[173,193,196,211,216,279,283,291,294,306,314,317,329,337,341,348,354,357,361,364,377,383,387,392,395,399,402,406,409,413,416,420,423,427,433,437,440,444,447,451,465,469],[174,175,176,183,184,188,189,192],"p",{},[177,178,182],"a",{"href":179,"rel":180},"https://hermes-agent.nousresearch.com/",[181],"nofollow","Hermes Agent"," is built to get better at ",[185,186,187],"em",{},"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 ",[185,190,191],{},"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,194,195],{},"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,197,198,199,204,205,210],{},"Hermes is a real step beyond a chat window that forgets you every morning. It is an open-source personal agent from ",[177,200,203],{"href":201,"rel":202},"https://nousresearch.com/",[181],"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 ",[177,206,209],{"href":207,"rel":208},"https://github.com/nousresearch/hermes-agent/",[181],"code"," 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.",[212,213,215],"h2",{"id":214},"words-youll-hear","Words you’ll hear",[217,218,219,231,237,243,249,255,261,267],"ul",{},[220,221,222,226,227,230],"li",{},[223,224,225],"strong",{},"Hermes Agent."," An open-source personal agent from ",[177,228,203],{"href":201,"rel":229},[181],". You install it on a Mac, Windows, or Linux machine. It can also live in Telegram, Discord, Slack, WhatsApp, Signal, email, or a terminal.",[220,232,233,236],{},[223,234,235],{},"Self-hosted."," You run the software. You pay the model bill. You keep the secrets. You are the operator.",[220,238,239,242],{},[223,240,241],{},"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.",[220,244,245,248],{},[223,246,247],{},"Workstream."," In Nimbus, a shared workspace for one job — not a private conversation on a machine.",[220,250,251,254],{},[223,252,253],{},"Wiki."," Official playbooks: how we book a journal, who may sign, what “done” means. Agents read that, not a private note on a desktop.",[220,256,257,260],{},[223,258,259],{},"Write-back."," Changing a live system. Reads are on by default. Writes stay off until you name a person who must approve.",[220,262,263,266],{},[223,264,265],{},"Lifecycle Graph."," The company record of what ran, who approved, and what changed. When the operator leaves, the record does not leave with their laptop.",[220,268,269,272,273,278],{},[223,270,271],{},"Secure by Design."," ",[177,274,277],{"href":275,"rel":276},"https://www.cisa.gov/securebydesign",[181],"CISA’s programme"," about who owns security outcomes. When you run software yourself, you are the operator.",[212,280,282],{"id":281},"why-the-difference-matters","Why the difference matters",[174,284,285,286,290],{},"You also own the upkeep. A laptop agent with mailbox and company files is a privileged identity you operate. ",[177,287,289],{"href":275,"rel":288},[181],"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,292,293],{},"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,295,296,297,301,302,305],{},"On Nimbus, finance opens a ",[177,298,300],{"href":299},"what-is-an-ai-workstream","workstream",". The wiki states the journal policy. The ledger connector is read-only until a human releases the write. The ",[177,303,23],{"href":304},"what-is-a-lifecycle-graph"," 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,307,308,309,313],{},"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 — ",[177,310,312],{"href":311},"what-is-shadow-ai","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,315,316],{},"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,318,319,320,323,324,328],{},"Role by role: a founder or researcher who will patch the install gets a personal agent that improves at ",[185,321,322],{},"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 ",[177,325,327],{"href":326},"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,330,331,332,336],{},"The job split is clean if you keep it clean. Hermes (or something like ",[177,333,335],{"href":334},"nimbus-vs-openclaw","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.",[212,338,340],{"id":339},"when-hermes-is-a-better-fit","When Hermes is a better fit",[174,342,343,344,347],{},"Choose Hermes when you are the user, you want an agent that improves at ",[185,345,346],{},"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,349,350,351,353],{},"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 ",[177,352,327],{"href":326},".",[174,355,356],{},"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.",[212,358,360],{"id":359},"how-this-shows-up-in-nimbus","How this shows up in Nimbus",[174,362,363],{},"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,365,366,369,370,372,373,376],{},[177,367,368],{"href":51},"Connectors"," link to the tools you already run — the ledger, the CRM, the shared drive. ",[177,371,39],{"href":40}," is the release path: agents draft, humans release, the graph keeps the decision. The ",[177,374,375],{"href":28},"wiki"," 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,378,379,380,353],{},"Start at the ",[177,381,382],{"href":12},"overview",[212,384,386],{"id":385},"questions-people-actually-ask","Questions people actually ask",[388,389,391],"h3",{"id":390},"is-nimbus-built-on-hermes","Is Nimbus built on Hermes?",[174,393,394],{},"No. They sit on different layers. Nimbus may call some of the same models Hermes uses. That is the model market, not a fork.",[388,396,398],{"id":397},"can-hermes-be-our-company-ai-platform","Can Hermes be our company AI platform?",[174,400,401],{},"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.",[388,403,405],{"id":404},"where-should-the-how-we-do-this-notes-live","Where should the “how we do this” notes live?",[174,407,408],{},"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.",[388,410,412],{"id":411},"can-we-run-hermes-beside-nimbus","Can we run Hermes beside Nimbus?",[174,414,415],{},"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.",[388,417,419],{"id":418},"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,421,422],{},"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.",[388,424,426],{"id":425},"how-is-hermes-different-from-openclaw","How is Hermes different from OpenClaw?",[174,428,429,430,353],{},"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,431,432],{"href":334},"Nimbus vs OpenClaw",[388,434,436],{"id":435},"who-owns-security-if-we-allow-hermes","Who owns security if we allow Hermes?",[174,438,439],{},"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.",[388,441,443],{"id":442},"what-happens-when-the-person-who-ran-hermes-leaves","What happens when the person who ran Hermes leaves?",[174,445,446],{},"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.",[212,448,450],{"id":449},"related-reading","Related reading",[174,452,453,457,458,462,463,353],{},[177,454,456],{"href":455},"what-is-institutional-memory-in-enterprise-ai","What is institutional memory in enterprise AI",", ",[177,459,461],{"href":460},"what-is-write-back-governance","What is write-back governance",", and ",[177,464,432],{"href":334},[212,466,468],{"id":467},"sources","Sources",[217,470,471,476,482,487],{},[220,472,473],{},[177,474,182],{"href":179,"rel":475},[181],[220,477,478],{},[177,479,481],{"href":207,"rel":480},[181],"Hermes Agent on GitHub",[220,483,484],{},[177,485,203],{"href":201,"rel":486},[181],[220,488,489],{},[177,490,492],{"href":275,"rel":491},[181],"CISA Secure by Design",{"title":155,"searchDepth":156,"depth":156,"links":494},[495,496,497,498,499,510,511],{"id":214,"depth":156,"text":215},{"id":281,"depth":156,"text":282},{"id":339,"depth":156,"text":340},{"id":359,"depth":156,"text":360},{"id":385,"depth":156,"text":386,"children":500},[501,503,504,505,506,507,508,509],{"id":390,"depth":502,"text":391},3,{"id":397,"depth":502,"text":398},{"id":404,"depth":502,"text":405},{"id":411,"depth":502,"text":412},{"id":418,"depth":502,"text":419},{"id":425,"depth":502,"text":426},{"id":435,"depth":502,"text":436},{"id":442,"depth":502,"text":443},{"id":449,"depth":156,"text":450},{"id":467,"depth":156,"text":468},"2026-08-17","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":165,"description":513},"comparisons","blog/nimbus-vs-hermes",[516,519,520,521,522],"hermes","nous-research","open-source-agents","memory","bOOe-srYHxqaxWVNoXUnSpNT7JEjUHGwtgJj_YPpGjA",{"hero":525,"id":527,"title":528,"archived":149,"authors":150,"badge":150,"body":529,"date":150,"department":150,"description":533,"extension":158,"eyebrow":534,"faqHeader":150,"faqs":150,"footerBand":535,"headline":150,"image":150,"industry":150,"jobType":150,"listed":149,"location":150,"navigation":115,"openRoles":150,"pageLayout":150,"path":60,"relatedHeading":541,"seo":542,"series":150,"sitemap":115,"status":150,"stem":543,"subhead":150,"tags":150,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":544},{"filename":526},"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":530,"toc":531},[],{"title":155,"searchDepth":156,"depth":156,"links":532},[],"Deep dives into pre-cognitive intelligence, sentient enterprises, and the evolving landscape of AI-driven business transformation.","Latest Research",{"headline":536,"description":537,"primaryLabel":538,"primaryTo":539,"secondaryLabel":540,"secondaryTo":12},"Stay at the frontier.","Subscribe for product updates and new insights.","Subscribe","/newsletter","Explore the platform","More research",{"title":528,"description":533},"blog/index","eK1RCXdDW8nfLSyKRXGB1mJm9FAmhAO6GWXwNKOMNVE",[546,888],{"id":547,"title":548,"archived":149,"authors":150,"badge":549,"body":552,"date":512,"department":150,"description":878,"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":879,"relatedHeading":150,"seo":880,"series":516,"sitemap":115,"status":150,"stem":881,"subhead":150,"tags":882,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":887},"content/blog/nimbus-vs-microsoft-copilot.md","Nimbus vs Microsoft Copilot: Great Inside Office, or Work That Leaves Microsoft?",{"label":167,"10|authors":550},[551],{"name":170,"to":120},{"type":152,"value":553,"toc":860},[554,573,576,599,601,652,654,660,669,676,687,690,693,697,700,703,706,709,712,714,725,738,745,750,752,756,759,763,766,770,775,779,786,790,793,797,800,804,811,815,821,823,833,835],[174,555,556,557,564,565,572],{},"“Copilot” is several products that get collapsed in procurement. ",[223,558,559],{},[177,560,563],{"href":561,"rel":562},"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. ",[223,566,567],{},[177,568,571],{"href":569,"rel":570},"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,574,575],{},"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,577,578,579,584,585,590,591,594,595,598],{},"Microsoft’s own ",[177,580,583],{"href":581,"rel":582},"https://learn.microsoft.com/en-us/microsoft-365/copilot/microsoft-365-copilot-architecture",[181],"architecture"," and ",[177,586,589],{"href":587,"rel":588},"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 ",[185,592,593],{},"find and draft inside Microsoft",", not ",[185,596,597],{},"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.",[212,600,215],{"id":214},[217,602,603,609,615,621,627,632,641,646],{},[220,604,605,608],{},[223,606,607],{},"Microsoft 365 Copilot."," The per-person assistant inside Office, grounded in Microsoft Graph — mail, files, meetings, and sites the user can already access.",[220,610,611,614],{},[223,612,613],{},"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.",[220,616,617,620],{},[223,618,619],{},"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.",[220,622,623,626],{},[223,624,625],{},"Agent Builder."," Simple agents inside Copilot, grounded in Microsoft 365 content, for information workers.",[220,628,629,631],{},[223,630,247],{}," In Nimbus, a shared workspace for one job across systems that are not all Microsoft.",[220,633,634,636,637,640],{},[223,635,259],{}," Changing a live system. You ",[185,638,639],{},"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.",[220,642,643,645],{},[223,644,265],{}," The causal record of who approved, what changed, and what the next team should believe.",[220,647,648,651],{},[223,649,650],{},"E5."," Microsoft 365 E5 explains identity, compliance, and Office. It does not explain CRM write-back or a company work ledger.",[212,653,282],{"id":281},[174,655,656,657,659],{},"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 ",[185,658,639],{}," 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,661,662,663,665,666,668],{},"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,664,300],{"href":299}," puts those in one job. Records stay read-only until someone who is allowed to approve writes actually does. The ",[177,667,23],{"href":304}," keeps the release.",[174,670,671,675],{},[177,672,674],{"href":673},"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,677,678,679,682,683,686],{},"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,680,681],{"href":460},"write-back",", choosing models across vendors, or a Lifecycle Graph. Standardise Copilot where Microsoft’s graph ",[185,684,685],{},"is"," the work. Standardise an operating layer where the business process is the work.",[174,688,689],{},"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,691,692],{},"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.",[212,694,696],{"id":695},"when-microsoft-copilot-is-a-better-fit","When Microsoft Copilot is a better fit",[174,698,699],{},"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,701,702],{},"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,704,705],{},"SharePoint agents are Q&A on sites. Use them for findability. Do not use them as the operating model.",[174,707,708],{},"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,710,711],{},"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.",[212,713,360],{"id":359},[174,715,716,717,720,721,724],{},"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,718,719],{"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,722,723],{"href":84},"sales",", not as a reason Copilot and Nimbus are the same product.",[174,726,727,728,730,731,733,734,737],{},"The ",[177,729,375],{"href":28}," is what the company asserts. ",[177,732,368],{"href":51}," are scoped per workspace. Agents get the systems you attached, in the mode you allowed, until a human releases a write. ",[177,735,736],{"href":20},"Agent teams"," finish the work Copilot handed you after the recap.",[174,739,740,741,744],{},"You can ",[177,742,743],{"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,746,747,748,353],{},"See ",[177,749,39],{"href":40},[212,751,386],{"id":385},[388,753,755],{"id":754},"does-nimbus-replace-microsoft-365-copilot","Does Nimbus replace Microsoft 365 Copilot?",[174,757,758],{},"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.",[388,760,762],{"id":761},"does-copilot-studio-replace-nimbus","Does Copilot Studio replace Nimbus?",[174,764,765],{},"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.",[388,767,769],{"id":768},"can-nimbus-use-azure-openai-or-microsoft-models","Can Nimbus use Azure OpenAI or Microsoft models?",[174,771,772,773,724],{},"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,774,723],{"href":84},[388,776,778],{"id":777},"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,780,781,782,682,784,686],{},"E5 explains identity, compliance, and Office. It does not explain CRM ",[177,783,681],{"href":460},[185,785,685],{},[388,787,789],{"id":788},"do-we-need-a-microsoft-partner-to-get-nimbus-running","Do we need a Microsoft partner to get Nimbus running?",[174,791,792],{},"No. You can set it up yourselves. Copilot Studio at organisational scale usually is not self-serve in the same way.",[388,794,796],{"id":795},"can-we-keep-copilot-and-put-salesforce-writes-in-nimbus","Can we keep Copilot and put Salesforce writes in Nimbus?",[174,798,799],{},"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.",[388,801,803],{"id":802},"who-should-own-which-product","Who should own which product?",[174,805,806,807,810],{},"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 ",[185,808,809],{},"and"," write gates. A single “we already pay Microsoft” owner will stretch Copilot into an operating layer.",[388,812,814],{"id":813},"what-about-glean-if-we-already-have-copilot","What about Glean if we already have Copilot?",[174,816,817,818,353],{},"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,819,820],{"href":673},"Nimbus vs Glean",[212,822,450],{"id":449},[174,824,825,457,827,462,831,353],{},[177,826,461],{"href":460},[177,828,830],{"href":829},"what-is-an-enterprise-ai-operating-system","What is an enterprise AI operating system",[177,832,820],{"href":673},[212,834,468],{"id":467},[217,836,837,842,848,854],{},[220,838,839],{},[177,840,563],{"href":561,"rel":841},[181],[220,843,844],{},[177,845,847],{"href":587,"rel":846},[181],"Microsoft 365 Copilot privacy",[220,849,850],{},[177,851,853],{"href":581,"rel":852},[181],"Microsoft 365 Copilot architecture",[220,855,856],{},[177,857,859],{"href":569,"rel":858},[181],"Microsoft Copilot Studio",{"title":155,"searchDepth":156,"depth":156,"links":861},[862,863,864,865,866,876,877],{"id":214,"depth":156,"text":215},{"id":281,"depth":156,"text":282},{"id":695,"depth":156,"text":696},{"id":359,"depth":156,"text":360},{"id":385,"depth":156,"text":386,"children":867},[868,869,870,871,872,873,874,875],{"id":754,"depth":502,"text":755},{"id":761,"depth":502,"text":762},{"id":768,"depth":502,"text":769},{"id":777,"depth":502,"text":778},{"id":788,"depth":502,"text":789},{"id":795,"depth":502,"text":796},{"id":802,"depth":502,"text":803},{"id":813,"depth":502,"text":814},{"id":449,"depth":156,"text":450},{"id":467,"depth":156,"text":468},"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":548,"description":878},"blog/nimbus-vs-microsoft-copilot",[516,883,884,885,886],"microsoft-copilot","copilot-studio","m365","enterprise-ai","w0CEv3bGzwk5Xggxh5z3sCk2Gdyqblmgq31V3RjJB0o",{"id":889,"title":890,"archived":149,"authors":150,"badge":891,"body":894,"date":512,"department":150,"description":1186,"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":1187,"relatedHeading":150,"seo":1188,"series":516,"sitemap":115,"status":150,"stem":1189,"subhead":150,"tags":1190,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":1195},"content/blog/nimbus-vs-glean.md","Nimbus vs Glean: Finding the Deck vs Running the Job That Deck Implies",{"label":167,"10|authors":892},[893],{"name":170,"to":120},{"type":152,"value":895,"toc":1168},[896,903,910,918,920,967,969,984,991,994,997,1000,1003,1006,1010,1017,1020,1023,1026,1028,1031,1045,1050,1057,1059,1063,1069,1073,1076,1080,1083,1087,1090,1094,1101,1105,1116,1118,1121,1125,1128,1130,1141,1143],[174,897,898,902],{},[177,899,674],{"href":900,"rel":901},"https://www.glean.com/",[181]," is workplace search that grew a work assistant on top. It finds files across Drive, Slack, Confluence, and the rest of the workplace — and it respects who is allowed to see them. Nimbus is the place you then run the job those files imply: update the customer record, file the next step, get a person to sign.",[174,904,905,906,909],{},"Glean’s centre of gravity is ",[223,907,908],{},"find the right object, for the right person, at the right time",". Nimbus’s is a signed-off outcome. Both products will say “knowledge” and “agents.” They are not the same purchase. Search that does not leak is a hard, years-long problem. A release on a live system is a different hard problem. Many enterprises have both. They should not pretend one vendor covers both because both say “knowledge graph.”",[174,911,912,917],{},[177,913,916],{"href":914,"rel":915},"https://www.glean.com/product",[181],"Glean’s product"," connects to Google Workspace, Microsoft 365, Slack, Salesforce, Confluence, Jira, and many more — publicly, 100+ workplace apps — then builds an index that respects the same permissions as the source system. Under the hood that is a mix of classic keyword search and meaning-based search, plus a map of people, documents, and activity. Glean has added assistants and agents so the search layer can also draft and automate. That architecture is why Glean wins large-enterprise search bake-offs. Identity, crawl, and permission fidelity are the hard problems, and Glean has spent years on them.",[212,919,215],{"id":214},[217,921,922,928,934,940,946,951,956,961],{},[220,923,924,927],{},[223,925,926],{},"Workplace search."," An index across the apps the company already uses, so people stop hunting for files.",[220,929,930,933],{},[223,931,932],{},"Permission mirroring."," If a document is restricted in Drive, Glean should not surface it in a chat answer. That is the product.",[220,935,936,939],{},[223,937,938],{},"Knowledge graph (Glean)."," A map of people, documents, and activity for retrieval. Not the same as Nimbus’s Lifecycle Graph.",[220,941,942,945],{},[223,943,944],{},"Crawl."," The programme of connecting apps, mapping identity, and keeping the index fresh. Why IT sponsors Glean. Why it takes time.",[220,947,948,950],{},[223,949,247],{}," In Nimbus, a shared workspace for one job — not a search result.",[220,952,953,955],{},[223,954,259],{}," Changing a live system. Search products add agents on top of the index. Nimbus treats the write as a first-class release.",[220,957,958,960],{},[223,959,265],{}," A causal record of AI work: what ran, who approved it, what changed. Not an index of every file an employee ever touched.",[220,962,963,966],{},[223,964,965],{},"Copilot."," Microsoft’s assistant inside Office. Glean searches across many apps, including Microsoft. Neither is a governed execution layer.",[212,968,282],{"id":281},[174,970,971,972,977,978,983],{},"If you have ever watched a naive chatbot answer from a restricted Drive folder, you understand why Glean exists. Permission mirroring is not a slogan. It is the product: if a document is restricted in Drive, Glean should not surface it in a chat answer. ",[177,973,976],{"href":974,"rel":975},"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final",[181],"NIST SP 800-53 Rev. 5"," Access Control (the AC family) is the control-catalogue reason: the system must enforce who may see what. ",[177,979,982],{"href":980,"rel":981},"https://www.glean.com/security",[181],"Glean’s security page"," describes that enforcement as a product: permission mirroring, encryption, and compliance claims. Glean is search that does not leak. It is not an AI risk-management framework, and it does not, by itself, put a named signer on a customer-record write.",[174,985,986,987,990],{},"Glean’s primary object is a document, message, ticket, or person. Nimbus’s primary object is a job, an agent team, a release. Glean’s success metric is time-to-answer. Nimbus’s is time-to-signed-off outcome. Glean’s write path is secondary — agents on top of the index. Nimbus’s write path is first-class: ",[177,988,989],{"href":460},"read-only until you open it",", then a person on the change.",[174,992,993],{},"Ask whether agents are a feature of search, or search is a feature of agents. Glean is the first. Nimbus is the second. Assistants on a permission-aware index are a reasonable next step for a search company. They still orbit findability. A workstream does not orbit a search result. It orbits a finish line, a budget, and a write policy.",[174,995,996],{},"The crawl is why IT sponsors Glean and why it takes time: connecting apps, mapping identity, keeping the index fresh, proving permission QA. That is the right model for a 20,000-person corpus. It is the wrong model if you needed a signed CRM update this quarter and were told to wait until 2019’s files had finished indexing. Nimbus assumes you can already find the policy, or that you will attach the systems this job needs. It does not wait for a company-wide crawl of every historical file.",[174,998,999],{},"The two “graphs” are the usual confusion. Glean’s knowledge graph is mostly an index of people and content for retrieval. Nimbus’s Lifecycle Graph is an operational ledger of work, agents, and releases. Collapsing the terms in a vendor meeting is how you buy the wrong one. You can run both graphs. You cannot substitute one for the other.",[174,1001,1002],{},"Role by role, the fork is practical. A CIO running a knowledge programme wants a universal search bar across 100+ apps, with permission mirroring as the non-negotiable. That is Glean. A Head of RevOps wants an agent to propose opportunity updates with a named signer — search will find the deck; it will not be the release. Security cares that Glean does not leak restricted files, and still cares who may change Salesforce. Knowledge workers want time-to-answer. Operators want time-to-signed-off outcome. Legal will not accept “the assistant found it” as the story of why a customer field moved.",[174,1004,1005],{},"A healthy split: Glean for findability across the sprawling workplace; Nimbus for execution on the jobs that mutate systems of record. Do not stretch Glean into an operating layer because it added agents. Do not stretch Nimbus into a crawl of every Confluence page because Perception can answer questions about the record.",[212,1007,1009],{"id":1008},"when-glean-is-a-better-fit","When Glean is a better fit",[174,1011,1012,1013,1016],{},"Choose Glean when the corpus is huge, permissions ",[185,1014,1015],{},"are"," the product, and you need a universal search bar across 100+ apps before you invent agent teams. Choose Glean also if the executive sponsor is the CIO’s knowledge programme rather than a line-of-business operating model.",[174,1018,1019],{},"Deployment is a crawl programme: identity mapping, permission QA, often with Glean or partner engineers in the building. That is the right model for a 20,000-person corpus. Do not treat that implementation cost as a reason Glean is “worse.” It is the cost of doing permission-aware search well.",[174,1021,1022],{},"Do not choose Glean as a stealth agent operating layer. You will spend a year on crawl quality and still lack workstreams, specialist teams, and change control on writes.",[174,1024,1025],{},"Some organisations will run Glean for findability and Nimbus for execution. That is a coherent architecture if you do not pretend one graph is the other. Keep Glean as the place people find the deck. Put the job the deck implies — update the customer record, file the next step, get a person to sign — in a Nimbus workstream. Connectors in Nimbus are not a substitute for Glean-scale historical crawl. A Glean assistant is not a substitute for a quoted write.",[212,1027,360],{"id":359},[174,1029,1030],{},"Search exists inside Nimbus as a way to ask about the record, your playbooks, and the systems you attached. It is not a company-wide crawl of 2019.",[174,1032,727,1033,730,1035,1037,1038,1040,1041,1044],{},[177,1034,375],{"href":28},[177,1036,368],{"href":51}," are scoped per ",[177,1039,300],{"href":32},". Agents do not get “search everything this user could theoretically open” as the default tool. They get the systems you attached, in the mode you allowed (usually read), until a human releases a write. ",[177,1042,1043],{"href":36},"Perception"," is ordinary language over that scoped world, not a second Glean.",[174,1046,740,1047,1049],{},[177,1048,743],{"href":12},": a workspace, wiki, connectors, a first workstream. You do not wait for an index of every historical file to finish.",[174,1051,747,1052,1054,1055,353],{},[177,1053,39],{"href":40}," and the ",[177,1056,23],{"href":24},[212,1058,386],{"id":385},[388,1060,1062],{"id":1061},"does-glean-require-more-implementation-than-nimbus","Does Glean require more implementation than Nimbus?",[174,1064,1065,1066,1068],{},"Usually yes. Permission-aware crawl at enterprise scale is a programme. Nimbus is self-service for most buyers: you are not waiting on vendor engineers sitting with your team for months to get collaboration, sign-off, and a causal record. That is not a claim that Glean is slow for no reason. Crawl and permission QA ",[185,1067,1015],{}," the work.",[388,1070,1072],{"id":1071},"does-nimbus-replace-glean","Does Nimbus replace Glean?",[174,1074,1075],{},"Only if your Glean usage is a thin Q&A bot on a small corpus. It does not replace Glean as permission-aware enterprise search across a sprawling workplace. If you need the latter, keep a search product.",[388,1077,1079],{"id":1078},"both-mention-knowledge-graphs-are-they-the-same","Both mention knowledge graphs. Are they the same?",[174,1081,1082],{},"No. Glean’s graph is mostly an index of people and content for retrieval. Nimbus’s Lifecycle Graph is an operational ledger of work, agents, and releases. Collapsing the terms in a vendor meeting is how you buy the wrong one.",[388,1084,1086],{"id":1085},"can-nimbus-search-drive-and-slack","Can Nimbus search Drive and Slack?",[174,1088,1089],{},"Connectors bring live systems into agent context and into questions you ask about the record. That is targeted operational retrieval, not a Glean-scale crawl of every historical file. If you need the latter, keep a search product.",[388,1091,1093],{"id":1092},"glean-vs-copilot-vs-nimbus","Glean vs Copilot vs Nimbus?",[174,1095,1096,1097,353],{},"Copilot is productivity inside Microsoft that respects Microsoft permissions. Glean is search across many apps (including Microsoft) that respects source permissions. Nimbus is governed execution. A Microsoft-first company may still need Glean if SharePoint search is not enough, and may still need Nimbus if Copilot Studio is not an operating layer. See ",[177,1098,1100],{"href":1099},"nimbus-vs-microsoft-copilot","Nimbus vs Microsoft Copilot",[388,1102,1104],{"id":1103},"can-we-run-glean-and-nimbus-together","Can we run Glean and Nimbus together?",[174,1106,1107,1108,1111,1112,1115],{},"Yes. That is the intended coexistence for organisations that have both a findability problem and an execution problem. Do not give Glean agents production write credentials because the index is permission-aware. Permission to ",[185,1109,1110],{},"see"," is not permission to ",[185,1113,1114],{},"change",". Route mutations through Nimbus governance.",[388,1117,803],{"id":802},[174,1119,1120],{},"The CIO’s knowledge programme typically owns Glean: identity mapping, crawl, permission QA. Line operators own Nimbus workstreams because they own the systems of record those jobs touch. Security reviews both — leak prevention on the search side, write gates on the execution side.",[388,1122,1124],{"id":1123},"if-glean-has-agents-now-why-add-nimbus","If Glean has agents now, why add Nimbus?",[174,1126,1127],{},"Because agents on an index are still a feature of search. Time-to-answer is not time-to-signed-off outcome. If the job is to change a customer record with a person on the write, you need a workstream, a wiki clause, and a graph — not another way to find the deck.",[212,1129,450],{"id":449},[174,1131,1132,457,1136,462,1139,353],{},[177,1133,1135],{"href":1134},"what-is-enterprise-rag","What is enterprise RAG",[177,1137,1138],{"href":304},"What is a lifecycle graph",[177,1140,1100],{"href":1099},[212,1142,468],{"id":467},[217,1144,1145,1150,1156,1162],{},[220,1146,1147],{},[177,1148,674],{"href":900,"rel":1149},[181],[220,1151,1152],{},[177,1153,1155],{"href":914,"rel":1154},[181],"Glean product",[220,1157,1158],{},[177,1159,1161],{"href":980,"rel":1160},[181],"Glean security",[220,1163,1164],{},[177,1165,1167],{"href":974,"rel":1166},[181],"NIST SP 800-53 Rev. 5 (Access Control)",{"title":155,"searchDepth":156,"depth":156,"links":1169},[1170,1171,1172,1173,1174,1184,1185],{"id":214,"depth":156,"text":215},{"id":281,"depth":156,"text":282},{"id":1008,"depth":156,"text":1009},{"id":359,"depth":156,"text":360},{"id":385,"depth":156,"text":386,"children":1175},[1176,1177,1178,1179,1180,1181,1182,1183],{"id":1061,"depth":502,"text":1062},{"id":1071,"depth":502,"text":1072},{"id":1078,"depth":502,"text":1079},{"id":1085,"depth":502,"text":1086},{"id":1092,"depth":502,"text":1093},{"id":1103,"depth":502,"text":1104},{"id":802,"depth":502,"text":803},{"id":1123,"depth":502,"text":1124},{"id":449,"depth":156,"text":450},{"id":467,"depth":156,"text":468},"Glean is permission-aware workplace search; Nimbus is the place an agent can change a customer record — with a person signing off.","/blog/nimbus-vs-glean",{"title":890,"description":1186},"blog/nimbus-vs-glean",[516,1191,1192,1193,1194],"glean","enterprise-search","knowledge-graph","agents","GaY9-99viUbh6e-P2OUDGOvCd7i49ockwlAhmKjb4TE",{"enabled":149,"message":1197,"linkLabel":78,"linkHref":79,"id":1198,"title":1199,"archived":149,"authors":150,"badge":150,"body":1200,"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":1204,"relatedHeading":150,"seo":1205,"series":150,"sitemap":115,"status":150,"stem":1206,"subhead":150,"tags":150,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":1207},"We're hiring! Join the team building the Sentient Enterprise.","content/shared/hiring.md","Hiring banner",{"type":152,"value":1201,"toc":1202},[],{"title":155,"searchDepth":156,"depth":156,"links":1203},[],"/shared/hiring",{"title":1199,"description":155},"shared/hiring","-6bioYD7lKYokGUVU3ff4hHTvB-sDyOMuCptKHnojfk",{"fold":1209,"id":1213,"title":1214,"archived":149,"authors":150,"badge":150,"body":1215,"date":150,"department":150,"description":155,"extension":158,"eyebrow":150,"faqHeader":150,"faqs":150,"footerBand":1219,"headline":150,"image":150,"industry":150,"jobType":150,"listed":149,"location":150,"navigation":115,"openRoles":150,"pageLayout":150,"path":1223,"relatedHeading":150,"seo":1224,"series":150,"sitemap":115,"status":150,"stem":1225,"subhead":150,"tags":150,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":1226},{"headline":1210,"description":1211,"primaryLabel":8,"primaryTo":1212,"secondaryLabel":540,"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":1216,"toc":1217},[],{"title":155,"searchDepth":156,"depth":156,"links":1218},[],{"headline":1220,"description":1221,"primaryLabel":8,"primaryTo":1212,"secondaryLabel":1222,"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":1214,"description":155},"shared/cta","YHK6Fb8AvCPR1zZq7R_xiXUG0hwhP5UxHA8Ix52JQp4",1787194070626]