[{"data":1,"prerenderedAt":1193},["ShallowReactive",2],{"site-nav-content":3,"blog:/blog/nimbus-vs-glean":163,"blog-index-copy":516,"blog:/blog/nimbus-vs-glean:surround":537,"hiring-banner-content":1162,"site-cta-content":1174},{"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":504,"department":150,"description":505,"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":506,"relatedHeading":150,"seo":507,"series":508,"sitemap":115,"status":150,"stem":509,"subhead":150,"tags":510,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":515},"content/blog/nimbus-vs-glean.md","Nimbus vs Glean: Finding the Deck vs Running the Job That Deck Implies",{"label":167,"10|authors":168},"Comparisons",[169],{"name":170,"to":120},"Nimbus Research",{"type":152,"value":172,"toc":485},[173,184,192,200,205,257,261,276,284,287,290,293,296,299,303,311,314,317,320,324,327,346,353,362,366,371,377,381,384,388,391,395,398,402,409,413,424,428,431,435,438,442,456,460],[174,175,176,183],"p",{},[177,178,182],"a",{"href":179,"rel":180},"https://www.glean.com/",[181],"nofollow","Glean"," 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,185,186,187,191],{},"Glean’s centre of gravity is ",[188,189,190],"strong",{},"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,193,194,199],{},[177,195,198],{"href":196,"rel":197},"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.",[201,202,204],"h2",{"id":203},"words-youll-hear","Words you’ll hear",[206,207,208,215,221,227,233,239,245,251],"ul",{},[209,210,211,214],"li",{},[188,212,213],{},"Workplace search."," An index across the apps the company already uses, so people stop hunting for files.",[209,216,217,220],{},[188,218,219],{},"Permission mirroring."," If a document is restricted in Drive, Glean should not surface it in a chat answer. That is the product.",[209,222,223,226],{},[188,224,225],{},"Knowledge graph (Glean)."," A map of people, documents, and activity for retrieval. Not the same as Nimbus’s Lifecycle Graph.",[209,228,229,232],{},[188,230,231],{},"Crawl."," The programme of connecting apps, mapping identity, and keeping the index fresh. Why IT sponsors Glean. Why it takes time.",[209,234,235,238],{},[188,236,237],{},"Workstream."," In Nimbus, a shared workspace for one job — not a search result.",[209,240,241,244],{},[188,242,243],{},"Write-back."," Changing a live system. Search products add agents on top of the index. Nimbus treats the write as a first-class release.",[209,246,247,250],{},[188,248,249],{},"Lifecycle Graph."," A causal record of AI work: what ran, who approved it, what changed. Not an index of every file an employee ever touched.",[209,252,253,256],{},[188,254,255],{},"Copilot."," Microsoft’s assistant inside Office. Glean searches across many apps, including Microsoft. Neither is a governed execution layer.",[201,258,260],{"id":259},"why-the-difference-matters","Why the difference matters",[174,262,263,264,269,270,275],{},"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,265,268],{"href":266,"rel":267},"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,271,274],{"href":272,"rel":273},"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,277,278,279,283],{},"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,280,282],{"href":281},"what-is-write-back-governance","read-only until you open it",", then a person on the change.",[174,285,286],{},"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,288,289],{},"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,291,292],{},"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,294,295],{},"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,297,298],{},"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.",[201,300,302],{"id":301},"when-glean-is-a-better-fit","When Glean is a better fit",[174,304,305,306,310],{},"Choose Glean when the corpus is huge, permissions ",[307,308,309],"em",{},"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,312,313],{},"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,315,316],{},"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,318,319],{},"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.",[201,321,323],{"id":322},"how-this-shows-up-in-nimbus","How this shows up in Nimbus",[174,325,326],{},"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,328,329,330,333,334,337,338,341,342,345],{},"The ",[177,331,332],{"href":28},"wiki"," is what the company asserts. ",[177,335,336],{"href":51},"Connectors"," are scoped per ",[177,339,340],{"href":32},"workstream",". 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,343,344],{"href":36},"Perception"," is ordinary language over that scoped world, not a second Glean.",[174,347,348,349,352],{},"You can ",[177,350,351],{"href":12},"set Nimbus up yourselves",": a workspace, wiki, connectors, a first workstream. You do not wait for an index of every historical file to finish.",[174,354,355,356,358,359,361],{},"See ",[177,357,39],{"href":40}," and the ",[177,360,23],{"href":24},".",[201,363,365],{"id":364},"questions-people-actually-ask","Questions people actually ask",[367,368,370],"h3",{"id":369},"does-glean-require-more-implementation-than-nimbus","Does Glean require more implementation than Nimbus?",[174,372,373,374,376],{},"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 ",[307,375,309],{}," the work.",[367,378,380],{"id":379},"does-nimbus-replace-glean","Does Nimbus replace Glean?",[174,382,383],{},"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.",[367,385,387],{"id":386},"both-mention-knowledge-graphs-are-they-the-same","Both mention knowledge graphs. Are they the same?",[174,389,390],{},"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.",[367,392,394],{"id":393},"can-nimbus-search-drive-and-slack","Can Nimbus search Drive and Slack?",[174,396,397],{},"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.",[367,399,401],{"id":400},"glean-vs-copilot-vs-nimbus","Glean vs Copilot vs Nimbus?",[174,403,404,405,361],{},"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,406,408],{"href":407},"nimbus-vs-microsoft-copilot","Nimbus vs Microsoft Copilot",[367,410,412],{"id":411},"can-we-run-glean-and-nimbus-together","Can we run Glean and Nimbus together?",[174,414,415,416,419,420,423],{},"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 ",[307,417,418],{},"see"," is not permission to ",[307,421,422],{},"change",". Route mutations through Nimbus governance.",[367,425,427],{"id":426},"who-should-own-which-product","Who should own which product?",[174,429,430],{},"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.",[367,432,434],{"id":433},"if-glean-has-agents-now-why-add-nimbus","If Glean has agents now, why add Nimbus?",[174,436,437],{},"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.",[201,439,441],{"id":440},"related-reading","Related reading",[174,443,444,448,449,453,454,361],{},[177,445,447],{"href":446},"what-is-enterprise-rag","What is enterprise RAG",", ",[177,450,452],{"href":451},"what-is-a-lifecycle-graph","What is a lifecycle graph",", and ",[177,455,408],{"href":407},[201,457,459],{"id":458},"sources","Sources",[206,461,462,467,473,479],{},[209,463,464],{},[177,465,182],{"href":179,"rel":466},[181],[209,468,469],{},[177,470,472],{"href":196,"rel":471},[181],"Glean product",[209,474,475],{},[177,476,478],{"href":272,"rel":477},[181],"Glean security",[209,480,481],{},[177,482,484],{"href":266,"rel":483},[181],"NIST SP 800-53 Rev. 5 (Access Control)",{"title":155,"searchDepth":156,"depth":156,"links":486},[487,488,489,490,491,502,503],{"id":203,"depth":156,"text":204},{"id":259,"depth":156,"text":260},{"id":301,"depth":156,"text":302},{"id":322,"depth":156,"text":323},{"id":364,"depth":156,"text":365,"children":492},[493,495,496,497,498,499,500,501],{"id":369,"depth":494,"text":370},3,{"id":379,"depth":494,"text":380},{"id":386,"depth":494,"text":387},{"id":393,"depth":494,"text":394},{"id":400,"depth":494,"text":401},{"id":411,"depth":494,"text":412},{"id":426,"depth":494,"text":427},{"id":433,"depth":494,"text":434},{"id":440,"depth":156,"text":441},{"id":458,"depth":156,"text":459},"2026-08-17","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":165,"description":505},"comparisons","blog/nimbus-vs-glean",[508,511,512,513,514],"glean","enterprise-search","knowledge-graph","agents","GaY9-99viUbh6e-P2OUDGOvCd7i49ockwlAhmKjb4TE",{"hero":517,"id":519,"title":520,"archived":149,"authors":150,"badge":150,"body":521,"date":150,"department":150,"description":525,"extension":158,"eyebrow":526,"faqHeader":150,"faqs":150,"footerBand":527,"headline":150,"image":150,"industry":150,"jobType":150,"listed":149,"location":150,"navigation":115,"openRoles":150,"pageLayout":150,"path":60,"relatedHeading":533,"seo":534,"series":150,"sitemap":115,"status":150,"stem":535,"subhead":150,"tags":150,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":536},{"filename":518},"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":522,"toc":523},[],{"title":155,"searchDepth":156,"depth":156,"links":524},[],"Deep dives into pre-cognitive intelligence, sentient enterprises, and the evolving landscape of AI-driven business transformation.","Latest Research",{"headline":528,"description":529,"primaryLabel":530,"primaryTo":531,"secondaryLabel":532,"secondaryTo":12},"Stay at the frontier.","Subscribe for product updates and new insights.","Subscribe","/newsletter","Explore the platform","More research",{"title":520,"description":525},"blog/index","eK1RCXdDW8nfLSyKRXGB1mJm9FAmhAO6GWXwNKOMNVE",[538,862],{"id":539,"title":540,"archived":149,"authors":150,"badge":541,"body":544,"date":504,"department":150,"description":852,"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":853,"relatedHeading":150,"seo":854,"series":508,"sitemap":115,"status":150,"stem":855,"subhead":150,"tags":856,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":861},"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":542},[543],{"name":170,"to":120},{"type":152,"value":545,"toc":834},[546,562,565,580,582,639,641,649,652,662,670,673,685,693,697,704,709,712,714,717,728,734,736,740,743,747,750,754,757,761,764,768,771,775,781,785,788,792,795,797,808,810],[174,547,548,553,554,557,558,561],{},[177,549,552],{"href":550,"rel":551},"https://hermes-agent.nousresearch.com/",[181],"Hermes Agent"," is built to get better at ",[307,555,556],{},"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 ",[307,559,560],{},"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,563,564],{},"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,566,567,568,573,574,579],{},"Hermes is a real step beyond a chat window that forgets you every morning. It is an open-source personal agent from ",[177,569,572],{"href":570,"rel":571},"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,575,578],{"href":576,"rel":577},"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.",[201,581,204],{"id":203},[206,583,584,594,600,606,611,617,622,627],{},[209,585,586,589,590,593],{},[188,587,588],{},"Hermes Agent."," An open-source personal agent from ",[177,591,572],{"href":570,"rel":592},[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.",[209,595,596,599],{},[188,597,598],{},"Self-hosted."," You run the software. You pay the model bill. You keep the secrets. You are the operator.",[209,601,602,605],{},[188,603,604],{},"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.",[209,607,608,610],{},[188,609,237],{}," In Nimbus, a shared workspace for one job — not a private conversation on a machine.",[209,612,613,616],{},[188,614,615],{},"Wiki."," Official playbooks: how we book a journal, who may sign, what “done” means. Agents read that, not a private note on a desktop.",[209,618,619,621],{},[188,620,243],{}," Changing a live system. Reads are on by default. Writes stay off until you name a person who must approve.",[209,623,624,626],{},[188,625,249],{}," The company record of what ran, who approved, and what changed. When the operator leaves, the record does not leave with their laptop.",[209,628,629,632,633,638],{},[188,630,631],{},"Secure by Design."," ",[177,634,637],{"href":635,"rel":636},"https://www.cisa.gov/securebydesign",[181],"CISA’s programme"," about who owns security outcomes. When you run software yourself, you are the operator.",[201,640,260],{"id":259},[174,642,643,644,648],{},"You also own the upkeep. A laptop agent with mailbox and company files is a privileged identity you operate. ",[177,645,647],{"href":635,"rel":646},[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,650,651],{},"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,653,654,655,658,659,661],{},"On Nimbus, finance opens a ",[177,656,340],{"href":657},"what-is-an-ai-workstream",". The wiki states the journal policy. The ledger connector is read-only until a human releases the write. The ",[177,660,23],{"href":451}," 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,663,664,665,669],{},"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,666,668],{"href":667},"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,671,672],{},"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,674,675,676,679,680,684],{},"Role by role: a founder or researcher who will patch the install gets a personal agent that improves at ",[307,677,678],{},"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,681,683],{"href":682},"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,686,687,688,692],{},"The job split is clean if you keep it clean. Hermes (or something like ",[177,689,691],{"href":690},"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.",[201,694,696],{"id":695},"when-hermes-is-a-better-fit","When Hermes is a better fit",[174,698,699,700,703],{},"Choose Hermes when you are the user, you want an agent that improves at ",[307,701,702],{},"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,705,706,707,361],{},"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,708,683],{"href":682},[174,710,711],{},"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.",[201,713,323],{"id":322},[174,715,716],{},"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,718,719,721,722,724,725,727],{},[177,720,336],{"href":51}," link to the tools you already run — the ledger, the CRM, the shared drive. ",[177,723,39],{"href":40}," is the release path: agents draft, humans release, the graph keeps the decision. The ",[177,726,332],{"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,729,730,731,361],{},"Start at the ",[177,732,733],{"href":12},"overview",[201,735,365],{"id":364},[367,737,739],{"id":738},"is-nimbus-built-on-hermes","Is Nimbus built on Hermes?",[174,741,742],{},"No. They sit on different layers. Nimbus may call some of the same models Hermes uses. That is the model market, not a fork.",[367,744,746],{"id":745},"can-hermes-be-our-company-ai-platform","Can Hermes be our company AI platform?",[174,748,749],{},"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.",[367,751,753],{"id":752},"where-should-the-how-we-do-this-notes-live","Where should the “how we do this” notes live?",[174,755,756],{},"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.",[367,758,760],{"id":759},"can-we-run-hermes-beside-nimbus","Can we run Hermes beside Nimbus?",[174,762,763],{},"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.",[367,765,767],{"id":766},"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,769,770],{},"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.",[367,772,774],{"id":773},"how-is-hermes-different-from-openclaw","How is Hermes different from OpenClaw?",[174,776,777,778,361],{},"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,779,780],{"href":690},"Nimbus vs OpenClaw",[367,782,784],{"id":783},"who-owns-security-if-we-allow-hermes","Who owns security if we allow Hermes?",[174,786,787],{},"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.",[367,789,791],{"id":790},"what-happens-when-the-person-who-ran-hermes-leaves","What happens when the person who ran Hermes leaves?",[174,793,794],{},"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.",[201,796,441],{"id":440},[174,798,799,448,803,453,806,361],{},[177,800,802],{"href":801},"what-is-institutional-memory-in-enterprise-ai","What is institutional memory in enterprise AI",[177,804,805],{"href":281},"What is write-back governance",[177,807,780],{"href":690},[201,809,459],{"id":458},[206,811,812,817,823,828],{},[209,813,814],{},[177,815,552],{"href":550,"rel":816},[181],[209,818,819],{},[177,820,822],{"href":576,"rel":821},[181],"Hermes Agent on GitHub",[209,824,825],{},[177,826,572],{"href":570,"rel":827},[181],[209,829,830],{},[177,831,833],{"href":635,"rel":832},[181],"CISA Secure by Design",{"title":155,"searchDepth":156,"depth":156,"links":835},[836,837,838,839,840,850,851],{"id":203,"depth":156,"text":204},{"id":259,"depth":156,"text":260},{"id":695,"depth":156,"text":696},{"id":322,"depth":156,"text":323},{"id":364,"depth":156,"text":365,"children":841},[842,843,844,845,846,847,848,849],{"id":738,"depth":494,"text":739},{"id":745,"depth":494,"text":746},{"id":752,"depth":494,"text":753},{"id":759,"depth":494,"text":760},{"id":766,"depth":494,"text":767},{"id":773,"depth":494,"text":774},{"id":783,"depth":494,"text":784},{"id":790,"depth":494,"text":791},{"id":440,"depth":156,"text":441},{"id":458,"depth":156,"text":459},"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":540,"description":852},"blog/nimbus-vs-hermes",[508,857,858,859,860],"hermes","nous-research","open-source-agents","memory","bOOe-srYHxqaxWVNoXUnSpNT7JEjUHGwtgJj_YPpGjA",{"id":863,"title":864,"archived":149,"authors":150,"badge":865,"body":868,"date":504,"department":150,"description":1153,"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":1154,"relatedHeading":150,"seo":1155,"series":508,"sitemap":115,"status":150,"stem":1156,"subhead":150,"tags":1157,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":1161},"content/blog/nimbus-vs-dust.md","Nimbus vs Dust: A Shared Agent Studio or a Place Departments Finish Work?",{"label":167,"10|authors":866},[867],{"name":170,"to":120},{"type":152,"value":869,"toc":1135},[870,878,881,890,892,942,944,947,964,967,982,989,992,995,999,1002,1010,1013,1015,1018,1023,1029,1035,1037,1041,1044,1048,1053,1057,1060,1064,1067,1071,1074,1078,1081,1085,1088,1092,1095,1097,1108,1110],[174,871,872,877],{},[177,873,876],{"href":874,"rel":875},"https://dust.tt",[181],"Dust"," is a shared agent studio. Your people write agents in plain language, connect them to Slack, Notion, Google Drive, GitHub, Salesforce, Zendesk and other apps, and pick which AI model each agent should use. Nimbus is the place those drafts have to survive contact with the rest of the company: go-to-market, finance, and ops on one job, with a sign-off and a record of what changed.",[174,879,880],{},"Dust’s centre of gravity is the agent itself: create it, share it, run it. Nimbus’s centre of gravity is the job. That is not a slight. Studios are how teams stop trapping a useful helper in one person’s chat history. Jobs are how several departments finish something that still makes sense next quarter. If you buy a studio and expect a ledger, you will be disappointed in the studio. If you buy a work OS and expect a flexible agent workshop as the main experience, you will be disappointed in the OS.",[174,882,883,884,889],{},"Dust is a French company, and that is part of why European buyers look at it closely. GDPR still applies when agents process personal data in company tools. Teams share agents, so the same helper is not trapped in one person’s history. Admins get company sign-in, roles for who can build or run an agent, and activity logs. Engineers can plug Dust agents into other developer tools. Model choice is real: OpenAI, Anthropic, Google, Mistral and others. Dust’s ",[177,885,888],{"href":886,"rel":887},"https://docs.dust.tt/docs/user-documentation/getting-started/dust-rollout-guide/welcome-to-dust",[181],"rollout guide"," describes that studio as an enterprise AI platform connecting models to internal knowledge, tools, and workflows.",[201,891,204],{"id":203},[206,893,894,900,910,916,921,926,931,936],{},[209,895,896,899],{},[188,897,898],{},"Agent studio."," A place to build, share, and run custom agents. Dust’s product. Useful. Not the same as a place several departments finish one job.",[209,901,902,905,906,909],{},[188,903,904],{},"Multiplayer agents."," Dust’s term for agents that are not trapped in one person’s chat history. Real. Still primarily ",[307,907,908],{},"shared agents",", not a lasting record of what finance approved.",[209,911,912,915],{},[188,913,914],{},"Model choice."," Dust works with OpenAI, Anthropic, Google, Mistral and others, so you are not locked to one chatbot brand. Nimbus does the same, and treats the choice as an operating decision: do not use the most expensive model for every small task.",[209,917,918,920],{},[188,919,237],{}," In Nimbus, a shared workspace for one job, with the right people, tools, and approval rules.",[209,922,923,925],{},[188,924,615],{}," Official playbooks agents must follow.",[209,927,928,930],{},[188,929,243],{}," Changing a live system. In Nimbus, connectors stay read-only until a named person signs.",[209,932,933,935],{},[188,934,249],{}," The causal record of what the AI did, who approved it, and what changed.",[209,937,938,941],{},[188,939,940],{},"CNIL."," France’s data-protection authority. Dust is a French company; GDPR still applies when agents process personal data in company tools.",[201,943,260],{"id":259},[174,945,946],{},"Teams can share Dust agents, so the same helper is not trapped in one person’s history. That “multiplayer” claim is fair. Admins get company sign-in, roles for who can build or run an agent, and activity logs. Engineers can plug Dust agents into other developer tools. Dust’s rollout guide is written as a programme: connect models to internal knowledge, tools, and workflows. That is a studio you roll out, not a toy.",[174,948,949,950,952,953,956,957,960,961,963],{},"Whether finance ever sees a discount field depends on how disciplined you were about who can invoke that agent, and whether anyone filed the run somewhere finance actually looks. Activity logs tell you that an agent ran. They do not automatically become a signed-off version of a CRM change. In Nimbus, go-to-market and finance sit on the same ",[177,951,340],{"href":657},". An ",[177,954,955],{"href":20},"agent team"," drafts against the ",[177,958,332],{"href":959},"what-is-a-company-wiki-for-ai-agents",". Customer records stay read-only until someone who is allowed to approve writes actually does. The ",[177,962,23],{"href":451}," keeps the signed-off version, not only the chat that produced it.",[174,965,966],{},"Dust searches connected sources and whatever you put in an agent’s knowledge. That works well when the files are clean. It gets fragile when the same fact lives in Slack, a deck, and a CRM field, and nobody is the official owner. If your failure is “the agent answered from an outdated Notion page,” Dust’s freshness and permission model matter most. If your failure is “we ran this last quarter and nobody can find the version finance signed,” you need a record of the job, not another shared agent.",[174,968,969,970,975,976,981],{},"Because Dust is French, the natural data-protection authority is the ",[177,971,974],{"href":972,"rel":973},"https://www.cnil.fr/en/ai-system-development-cnils-recommendations-to-comply-gdpr",[181],"CNIL",". CNIL is clear that GDPR still applies when you develop and run AI that processes personal data, including when those systems later connect to company tools. A shared Salesforce agent is not “just a helper.” It is processing with a purpose. ",[177,977,980],{"href":978,"rel":979},"https://www.cnil.fr/en/ensuring-security-ai-systems-development",[181],"CNIL’s security sheet"," puts Article 32 in plain language: security of processing is a risk-based obligation. European origin does not exempt you from deciding who may change production data. Dust’s buyers often arrive with that question already on the table — which is healthy.",[174,983,984,985,988],{},"Model choice is a shared strength. Dust lets you pick a model per agent. Nimbus treats that choice as an operating decision: do not use the most expensive model for every small task. See ",[177,986,987],{"href":45},"models",". The difference is whether the choice sits on an agent you published, or on a step inside a job with a budget in NTUs (work credits).",[174,990,991],{},"The fork is practical by role. A team lead who wants reusable helpers on Slack, Notion, and Drive will feel at home in Dust — publishing an agent is the product. An engineer who wants Dust sitting in the middle of existing tools has a path; that is a hub, not a COO login. Finance cares whether a discount field changed, who signed, and which playbook applied. Legal and a DPO in Europe will read CNIL and still ask purpose, retention, and who can write. Ops eventually wants one canvas for a cross-department job, not a catalogue of agents each team invented.",[174,993,994],{},"The hidden cost in Dust is operational: who owns the write policy when an agent can change production data. The hidden cost in Nimbus is adoption: operators must run workstreams, not only chat. Pick the cost you can staff.",[201,996,998],{"id":997},"when-dust-is-a-better-fit","When Dust is a better fit",[174,1000,1001],{},"Choose Dust when your job this quarter is “let teams publish reusable agents on our Slack, Notion, and Drive,” you are happy for knowledge to live in those source systems, and you want a flexible studio rather than an opinionated place to finish cross-department work.",[174,1003,1004,1005,1009],{},"Dust is also the better match if you have engineers who want Dust sitting in the middle of your existing tools, and you do not want a workstream-and-record layer yet. It is a strong alternative to ",[177,1006,1008],{"href":1007},"nimbus-vs-chatgpt-enterprise","ChatGPT Enterprise"," when you need company context and custom agents you can share — especially in Europe and the mid-market.",[174,1011,1012],{},"Many teams start in an agent studio and later need sign-off, a ledger, and department-shaped work. That is the path Nimbus is built for — not an insult to Dust. You can keep Dust at the edge for engineering-tool agents and put Nimbus on the business jobs that need a sign-off. Coexistence is a policy: Dust agents do not hold production write passwords for money-moving systems; those writes wait in Nimbus.",[201,1014,323],{"id":322},[174,1016,1017],{},"You are not buying a folder of shared agents. You are buying a place go-to-market can draft, finance can review, and the company can still explain the change six months later.",[174,1019,1020,1022],{},[177,1021,336],{"href":51}," are scoped to the workspace and kept read-only until a write is approved. Nimbus publishes 2,000+ integrations; Dust publicly emphasises 70-plus, plus custom developer plug-ins. Count is not the whole story. Dust’s set on Slack, Notion, Drive, GitHub, Salesforce, and Zendesk may be exactly what a studio needs. Nimbus’s catalogue matters when the job spans a longer tail — and when the write path is a release, not an invocation.",[174,1024,348,1025,1028],{},[177,1026,1027],{"href":12},"set this up yourselves",". You do not need vendor engineers sitting with your team for months. Dust’s own rollout guide is still a rollout. Run that if you are buying a studio. Do not wait for it to grow a Lifecycle Graph.",[174,1030,355,1031,358,1033,361],{},[177,1032,39],{"href":40},[177,1034,23],{"href":24},[201,1036,365],{"id":364},[367,1038,1040],{"id":1039},"can-nimbus-replace-dust","Can Nimbus replace Dust?",[174,1042,1043],{},"If Dust is a handful of shared agents on Notion and Slack, yes — you move the jobs into workstreams and the playbooks into the wiki. If you have invested heavily in Dust as a hub for engineering tools, keep Dust at the edge and put Nimbus on the business jobs that need a sign-off.",[367,1045,1047],{"id":1046},"does-nimbus-lock-you-to-one-ai-vendor","Does Nimbus lock you to one AI vendor?",[174,1049,1050,1051,361],{},"No. Both products let you choose models. Dust lets you pick a model per agent. Nimbus treats that choice as an operating decision. See ",[177,1052,987],{"href":45},[367,1054,1056],{"id":1055},"is-dust-more-multiplayer-than-nimbus","Is Dust more “multiplayer” than Nimbus?",[174,1058,1059],{},"Dust coined multiplayer for shared agents, and that is real. Nimbus’s shared surface is the workstream: humans and agent teams across departments on one job, with the Lifecycle Graph as shared memory. Both are multiplayer. Nimbus includes the sign-off and the record.",[367,1061,1063],{"id":1062},"dust-vs-chatgpt-enterprise-vs-nimbus","Dust vs ChatGPT Enterprise vs Nimbus?",[174,1065,1066],{},"Dust is the closer peer: a shared agent studio with connectors. ChatGPT Enterprise is the default assistant plus team-owned agents inside OpenAI’s product. If you are leaving ChatGPT because you need shared, model-choice agents, Dust is the usual next stop. If you are leaving because you need write gates and a ledger, skip the studio. Three products, three centres of gravity: chat, published agent, job.",[367,1068,1070],{"id":1069},"how-should-we-think-about-cost","How should we think about cost?",[174,1072,1073],{},"Dust is typically seats plus usage on a workspace of agents. Nimbus meters the work you run, in NTUs (work credits). Compare a real workload — one programme that updates customer records — not list price per seat. The hidden cost in Dust is operational: who owns the write policy when an agent can change production data. The hidden cost in Nimbus is adoption: operators must run workstreams, not only chat.",[367,1075,1077],{"id":1076},"does-dusts-french-base-make-gdpr-easier","Does Dust’s French base make GDPR easier?",[174,1079,1080],{},"It makes the conversation more natural. CNIL’s guidance still applies: GDPR applies when you develop and run AI that processes personal data, and security of processing is a risk-based obligation. Publishing an agent is not a sign-off on the write.",[367,1082,1084],{"id":1083},"can-we-run-dust-agents-that-draft-and-nimbus-that-releases","Can we run Dust agents that draft and Nimbus that releases?",[174,1086,1087],{},"Yes. Treat Dust as the place teams publish helpers for knowledge work. Feed anything that must change a live system into a Nimbus workstream. Do not let the published agent hold the write password.",[367,1089,1091],{"id":1090},"who-should-own-dust-vs-nimbus","Who should own Dust vs Nimbus?",[174,1093,1094],{},"Platform or IT often owns a studio: who may build, who may run, which models, which connectors. Line operators own Nimbus workstreams because they own the outcome. If engineers want Dust in the middle of developer tools, let them — and keep money-moving writes off that hub.",[201,1096,441],{"id":440},[174,1098,1099,448,1103,453,1105,361],{},[177,1100,1102],{"href":1101},"what-is-multi-agent-ai","What is multi-agent AI",[177,1104,805],{"href":281},[177,1106,1107],{"href":1007},"Nimbus vs ChatGPT Enterprise",[201,1109,459],{"id":458},[206,1111,1112,1117,1123,1129],{},[209,1113,1114],{},[177,1115,876],{"href":874,"rel":1116},[181],[209,1118,1119],{},[177,1120,1122],{"href":886,"rel":1121},[181],"Dust rollout guide: Welcome to Dust",[209,1124,1125],{},[177,1126,1128],{"href":972,"rel":1127},[181],"CNIL, AI system development: recommendations to comply with the GDPR",[209,1130,1131],{},[177,1132,1134],{"href":978,"rel":1133},[181],"CNIL, Ensuring the security of an AI system's development",{"title":155,"searchDepth":156,"depth":156,"links":1136},[1137,1138,1139,1140,1141,1151,1152],{"id":203,"depth":156,"text":204},{"id":259,"depth":156,"text":260},{"id":997,"depth":156,"text":998},{"id":322,"depth":156,"text":323},{"id":364,"depth":156,"text":365,"children":1142},[1143,1144,1145,1146,1147,1148,1149,1150],{"id":1039,"depth":494,"text":1040},{"id":1046,"depth":494,"text":1047},{"id":1055,"depth":494,"text":1056},{"id":1062,"depth":494,"text":1063},{"id":1069,"depth":494,"text":1070},{"id":1076,"depth":494,"text":1077},{"id":1083,"depth":494,"text":1084},{"id":1090,"depth":494,"text":1091},{"id":440,"depth":156,"text":441},{"id":458,"depth":156,"text":459},"Dust is a shared studio for building and publishing AI agents; Nimbus is where departments finish a job with a named signer and a lasting record.","/blog/nimbus-vs-dust",{"title":864,"description":1153},"blog/nimbus-vs-dust",[508,1158,1159,514,1160],"dust","enterprise-ai","governance","NqfuVK0DzAxN3YIuQXXm9YlK5KTrksOvcSLPIIgskEA",{"enabled":149,"message":1163,"linkLabel":78,"linkHref":79,"id":1164,"title":1165,"archived":149,"authors":150,"badge":150,"body":1166,"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":1170,"relatedHeading":150,"seo":1171,"series":150,"sitemap":115,"status":150,"stem":1172,"subhead":150,"tags":150,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":1173},"We're hiring! Join the team building the Sentient Enterprise.","content/shared/hiring.md","Hiring banner",{"type":152,"value":1167,"toc":1168},[],{"title":155,"searchDepth":156,"depth":156,"links":1169},[],"/shared/hiring",{"title":1165,"description":155},"shared/hiring","-6bioYD7lKYokGUVU3ff4hHTvB-sDyOMuCptKHnojfk",{"fold":1175,"id":1179,"title":1180,"archived":149,"authors":150,"badge":150,"body":1181,"date":150,"department":150,"description":155,"extension":158,"eyebrow":150,"faqHeader":150,"faqs":150,"footerBand":1185,"headline":150,"image":150,"industry":150,"jobType":150,"listed":149,"location":150,"navigation":115,"openRoles":150,"pageLayout":150,"path":1189,"relatedHeading":150,"seo":1190,"series":150,"sitemap":115,"status":150,"stem":1191,"subhead":150,"tags":150,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":1192},{"headline":1176,"description":1177,"primaryLabel":8,"primaryTo":1178,"secondaryLabel":532,"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":1182,"toc":1183},[],{"title":155,"searchDepth":156,"depth":156,"links":1184},[],{"headline":1186,"description":1187,"primaryLabel":8,"primaryTo":1178,"secondaryLabel":1188,"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":1180,"description":155},"shared/cta","YHK6Fb8AvCPR1zZq7R_xiXUG0hwhP5UxHA8Ix52JQp4",1787194070383]