[{"data":1,"prerenderedAt":1202},["ShallowReactive",2],{"site-nav-content":3,"blog:/blog/nimbus-vs-paperclip":163,"blog-index-copy":524,"blog:/blog/nimbus-vs-paperclip:surround":545,"hiring-banner-content":1171,"site-cta-content":1183},{"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":513,"department":150,"description":514,"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":515,"relatedHeading":150,"seo":516,"series":517,"sitemap":115,"status":150,"stem":518,"subhead":150,"tags":519,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":523},"content/blog/nimbus-vs-paperclip.md","Nimbus vs Paperclip: An Org Chart for Other People’s Bots, or a Product a COO Can Log Into?",{"label":167,"10|authors":168},"Comparisons",[169],{"name":170,"to":120},"Nimbus Research",{"type":152,"value":172,"toc":494},[173,184,196,217,222,290,294,297,304,318,321,324,331,335,342,345,348,351,355,358,368,375,379,384,387,391,394,398,401,405,408,412,424,428,433,437,440,444,447,451,465,469],[174,175,176,183],"p",{},[177,178,182],"a",{"href":179,"rel":180},"https://paperclip.ing/",[181],"nofollow","Paperclip"," is the management layer people reach for when they already run OpenClaw, Hermes, Claude, Cursor, or a pile of custom workers and have lost track of who is doing what and what it costs. Nimbus is the finished product those operators log into: one shared workspace for a job, specialist teams, official playbooks, and a record of what shipped.",[174,185,186,187,191,192,195],{},"Paperclip is multiplayer for ",[188,189,190],"em",{},"agents",". Nimbus is multiplayer for departments and the people in them. The insight behind Paperclip is correct. Multi-agent chaos is an organisation-design problem, not a prompting problem. If you have lived through “we have twelve automations, three chat bots, and a coding agent fleet,” Paperclip feels like relief. Someone finally named the org chart. Relief is not a workplace. An org chart of agents is a start. A signed-off outcome in a workstream is the product those agents would work ",[188,193,194],{},"in",", not the scheduler that wakes them.",[174,197,198,199,204,205,210,211,216],{},"Paperclip is an open-source app to manage AI agents for work. You define a goal, “hire” agents into roles, set monthly budgets, and run work through tickets. Agents wake on a schedule and stop when they hit the budget. The ",[177,200,203],{"href":201,"rel":202},"https://github.com/paperclipai/paperclip",[181],"code"," is public; you can run it yourself. It works with many agents — the site lists Claude, Codex, Gemini, Cursor, Hermes, OpenClaw, and others. If a worker can receive a heartbeat, it can be hired. ",[177,206,209],{"href":207,"rel":208},"https://docs.crewai.com/",[181],"CrewAI"," and ",[177,212,215],{"href":213,"rel":214},"https://arxiv.org/abs/2308.00352",[181],"MetaGPT"," are the research-and-builder names for that orchestration category. Paperclip is that category as a product you hire into.",[218,219,221],"h2",{"id":220},"words-youll-hear","Words you’ll hear",[223,224,225,237,250,256,262,268,274,284],"ul",{},[226,227,228,232,233,236],"li",{},[229,230,231],"strong",{},"Paperclip."," An open-source app to manage AI agents for work. You define a goal, “hire” agents into roles, set monthly budgets, and run work through tickets. Agents wake on a schedule and stop when they hit the budget. The ",[177,234,203],{"href":201,"rel":235},[181]," is public; you can run it yourself.",[226,238,239,242,243,210,246,249],{},[229,240,241],{},"Orchestration."," Coordinating several agents. ",[177,244,209],{"href":207,"rel":245},[181],[177,247,215],{"href":213,"rel":248},[181]," are the research-and-builder names for that category. Paperclip is that category as a product you hire into.",[226,251,252,255],{},[229,253,254],{},"Agent budget."," Cap the worker, warn at 80%, pause at 100%. Necessary cost control. Not the same as stopping a bad write.",[226,257,258,261],{},[229,259,260],{},"Workstream."," In Nimbus, a shared workspace for one job — the ticket a non-engineer can actually run.",[226,263,264,267],{},[229,265,266],{},"Agent teams."," AI specialists grouped like departments: finance, go-to-market, ops. You are not wiring a cluster of other people’s bots on day one.",[226,269,270,273],{},[229,271,272],{},"Wiki."," Official playbooks those teams must respect.",[226,275,276,279,280,283],{},[229,277,278],{},"Write-back."," Changing a live system. Paperclip’s FAQ is frank: it governs what agents do ",[188,281,282],{},"to Paperclip"," (hiring, strategy). Your agents are your own, and you secure them however you want.",[226,285,286,289],{},[229,287,288],{},"Lifecycle Graph."," What ran, who approved, and what changed — so next quarter’s team does not relitigate the exception from Slack archaeology.",[218,291,293],{"id":292},"why-the-difference-matters","Why the difference matters",[174,295,296],{},"The limitation is structural. Paperclip assumes you bring the employees (the agents), the tools, the memory, and the identity story. That is honest. It is also why a scheduler is not the product your board logs into. You still need a place work is grounded, a place writes are gated, and a place the company remembers.",[174,298,299,300,303],{},"A worker that hits its budget and stops is a cost control. A worker that hits production with the wrong SKU is an incident. Nimbus also caps spend so a long-running job cannot silently burn the month (metered in NTUs — work credits). The extra loop is change control: which system a write hits, who signs, where the artefact is stored. See ",[177,301,302],{"href":40},"governance",". Cap-at-100% is necessary. It is not the same as stopping a bad write.",[174,305,306,307,310,311,314,315,317],{},"Paperclip does not replace a knowledge layer. Each hired agent may remember differently — Hermes how-to notes here, OpenClaw files there, a folder nobody owns. Different agents will each tell you a different last quarter. Nimbus ships wiki plus ",[177,308,309],{"href":51},"connectors"," plus the ",[177,312,23],{"href":313},"what-is-a-lifecycle-graph"," so execution has one place to read from and a gated place to write to. Paperclip’s FAQ is frank: it governs what agents do ",[188,316,282],{}," (hiring, strategy). Your agents are your own, and you secure them however you want. That frankness is a virtue. It is also the gap. Write-back into Salesforce is not Paperclip’s job unless you built it into the workers you hired.",[174,319,320],{},"Speed of new agents is exactly why a scheduler appears. It is also why a scheduler is not the office. A staff rota does not replace the workplace. It only says who is on shift. OpenClaw and Hermes are employees. Paperclip is the org chart. Nimbus is the company plus the office. Buying all three still does not give you a Lifecycle Graph unless Nimbus (or something like it) is in the stack.",[174,322,323],{},"Role by role: an engineer running OpenClaw, Hermes, and a coding fleet will feel Paperclip as relief — budgets, tickets, a heartbeat. A Head of Ops should not be asked to assemble that roster on day one; they need a product they can log into. Finance cares that a pause-at-budget is not a pause-at-bad-journal. Security inherits whatever each hired agent can already do; Paperclip does not secure them for you. A COO comparing open source versus a hosted product is choosing which lock they can staff: Paperclip reduces vendor lock-in and increases ops lock-in. Most companies can complete a vendor review. Few can run a round-the-clock agent operations desk.",[174,325,326,327,330],{},"If you are committed to those workers and only need orchestration, Paperclip is in-category. If you are not building an OS, do not start with the scheduler. Treat the workers as prototypes. Recreate the ",[188,328,329],{},"jobs"," as Nimbus workstreams and agent teams. Leave the old bots as personal tools without production credentials. Do not lift-and-shift tickets. Lift-and-shift the operating loop.",[218,332,334],{"id":333},"when-paperclip-is-a-better-fit","When Paperclip is a better fit",[174,336,337,338,341],{},"Choose Paperclip when you are committed to OpenClaw, Hermes, or custom workers, you have people to operate them, and you only need orchestration. Choose it as a research scheduler in a lab. Choose it if your company ",[188,339,340],{},"is"," building an agent OS and you need that scheduler while you build the rest.",[174,343,344],{},"If you are not building an OS, do not start with the scheduler. A staff rota does not replace the office. It only says who is on shift.",[174,346,347],{},"Paperclip’s value shows up when you have several different workers to coordinate. Nimbus’s value shows up at one team that must touch production systems safely. You do not need Paperclip if you only have one agent. You might still need Nimbus.",[174,349,350],{},"Do not put a second org chart on top of Nimbus. Nimbus already assigns work to agent teams. Two budgets and two sources of truth is a support nightmare. If you migrate, migrate jobs, not tickets.",[218,352,354],{"id":353},"how-this-shows-up-in-nimbus","How this shows up in Nimbus",[174,356,357],{},"Nimbus is the application layer a Head of Ops opens without assembling a roster of third-party bots on day one.",[174,359,360,361,210,364,367],{},"You attach connectors under a read-only default. Humans release writes. You get specialist teams and a canvas, then you attach systems. See ",[177,362,363],{"href":20},"agent teams",[177,365,366],{"href":32},"workstreams",". Spend is capped in NTUs so a long-running job cannot silently burn the month — and the write still waits for a signer.",[174,369,370,371,374],{},"Start at the ",[177,372,373],{"href":12},"overview",".",[218,376,378],{"id":377},"questions-people-actually-ask","Questions people actually ask",[380,381,383],"h3",{"id":382},"is-nimbus-paperclip-with-a-nicer-screen","Is Nimbus “Paperclip with a nicer screen”?",[174,385,386],{},"No. The overlap is control: roles, budgets, assignment. The product is the work loop and the graph. A ticket router does not give you official playbooks or a read-only-default CRM connector.",[380,388,390],{"id":389},"can-paperclip-orchestrate-nimbus","Can Paperclip orchestrate Nimbus?",[174,392,393],{},"Unnatural. Nimbus already assigns work to agent teams. A second org chart on top is two budgets, two sources of truth, and a support nightmare.",[380,395,397],{"id":396},"open-source-vs-a-hosted-product-which-lock-in-is-worse","Open source vs a hosted product — which lock-in is worse?",[174,399,400],{},"Paperclip reduces vendor lock-in and increases ops lock-in: you staff the bots. Nimbus is the reverse. Pick the lock you can actually staff. Most companies can complete a vendor review. Few can run a round-the-clock agent operations desk.",[380,402,404],{"id":403},"do-we-need-paperclip-if-we-only-have-one-agent","Do we need Paperclip if we only have one agent?",[174,406,407],{},"No. Paperclip’s value shows up when you have several different workers to coordinate. Nimbus’s value shows up at one team that must touch production systems safely.",[380,409,411],{"id":410},"how-does-paperclip-relate-to-openclaw-and-hermes","How does Paperclip relate to OpenClaw and Hermes?",[174,413,414,415,210,419,423],{},"OpenClaw and Hermes are employees. Paperclip is the org chart. Nimbus is the company plus the office. See ",[177,416,418],{"href":417},"nimbus-vs-openclaw","Nimbus vs OpenClaw",[177,420,422],{"href":421},"nimbus-vs-hermes","Nimbus vs Hermes",". Buying all three still does not give you a Lifecycle Graph.",[380,425,427],{"id":426},"can-we-migrate-from-paperclip-to-nimbus","Can we migrate from Paperclip to Nimbus?",[174,429,430,431,330],{},"Treat the workers as prototypes. Recreate the ",[188,432,329],{},[380,434,436],{"id":435},"does-a-budget-cap-replace-write-back-governance","Does a budget cap replace write-back governance?",[174,438,439],{},"No. A worker that hits its budget and stops is a cost control. A worker that hits production with the wrong SKU is an incident. Caps are necessary. They do not quote a field change or name a signer.",[380,441,443],{"id":442},"who-should-run-paperclip-if-we-keep-it","Who should run Paperclip if we keep it?",[174,445,446],{},"Whoever already operates the bots — usually engineering. Do not hand a Head of Ops a scheduler and call it a workplace. If operators need to finish a job, they need Nimbus. If engineers need to wake a fleet, they may still want Paperclip in the lab, off production credentials.",[218,448,450],{"id":449},"related-reading","Related reading",[174,452,453,457,458,462,463,374],{},[177,454,456],{"href":455},"what-is-multi-agent-ai","What is multi-agent AI",", ",[177,459,461],{"href":460},"what-is-an-ai-workstream","What is an AI workstream",", and ",[177,464,418],{"href":417},[218,466,468],{"id":467},"sources","Sources",[223,470,471,476,482,488],{},[226,472,473],{},[177,474,182],{"href":179,"rel":475},[181],[226,477,478],{},[177,479,481],{"href":201,"rel":480},[181],"Paperclip on GitHub",[226,483,484],{},[177,485,487],{"href":207,"rel":486},[181],"CrewAI documentation",[226,489,490],{},[177,491,493],{"href":213,"rel":492},[181],"Hong et al., MetaGPT (arXiv:2308.00352)",{"title":155,"searchDepth":156,"depth":156,"links":495},[496,497,498,499,500,511,512],{"id":220,"depth":156,"text":221},{"id":292,"depth":156,"text":293},{"id":333,"depth":156,"text":334},{"id":353,"depth":156,"text":354},{"id":377,"depth":156,"text":378,"children":501},[502,504,505,506,507,508,509,510],{"id":382,"depth":503,"text":383},3,{"id":389,"depth":503,"text":390},{"id":396,"depth":503,"text":397},{"id":403,"depth":503,"text":404},{"id":410,"depth":503,"text":411},{"id":426,"depth":503,"text":427},{"id":435,"depth":503,"text":436},{"id":442,"depth":503,"text":443},{"id":449,"depth":156,"text":450},{"id":467,"depth":156,"text":468},"2026-08-17","Paperclip organises the agents you already run; Nimbus is the finished workplace where departments share one job — not twelve bots nobody owns.","/blog/nimbus-vs-paperclip",{"title":165,"description":514},"comparisons","blog/nimbus-vs-paperclip",[517,520,521,522,302],"paperclip","multi-agent","orchestration","9v34C0UEdjpM1myjS2p6Ck-9_OOxTapIYCAT9v4fM2I",{"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,875],{"id":547,"title":548,"archived":149,"authors":150,"badge":549,"body":552,"date":513,"department":150,"description":866,"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":867,"relatedHeading":150,"seo":868,"series":517,"sitemap":115,"status":150,"stem":869,"subhead":150,"tags":870,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":874},"content/blog/nimbus-vs-perplexity.md","Nimbus vs Perplexity: Cited Answers from the Web, or Running the Work the Answer Implies?",{"label":167,"10|authors":550},[551],{"name":170,"to":120},{"type":152,"value":553,"toc":847},[554,562,565,585,587,638,640,648,666,669,677,684,687,691,694,697,700,703,705,716,726,733,738,740,744,747,751,754,758,761,765,768,772,778,782,785,789,792,796,799,803,806,808,820,822],[174,555,556,561],{},[177,557,560],{"href":558,"rel":559},"https://www.perplexity.ai/enterprise",[181],"Perplexity Enterprise"," is how people get cited answers from the web, and increasingly from files and connected tools. Nimbus is how the company runs the work those answers imply: a shared job, official playbooks, a human on the write.",[174,563,564],{},"If your bottleneck is “get a sourced answer fast,” Perplexity is in-category. If your bottleneck is “update the live recommendation without a shadow login,” Nimbus is in-category. Those are different verbs. Perplexity synthesises. Nimbus runs work. Do not shortlist an answer engine as a stealth operating system, and do not shortlist a work OS as the only web research tool.",[174,566,567,572,573,578,579,584],{},[177,568,571],{"href":569,"rel":570},"https://www.perplexity.ai/hub/blog/perplexity-launches-enterprise-pro",[181],"Perplexity’s launch note for Enterprise Pro"," is the original B2B pitch: team management, SSO, SOC 2, and a promise not to train on enterprise customer data. Their later ",[177,574,577],{"href":575,"rel":576},"https://www.perplexity.ai/hub/blog/how-perplexity-enterprise-pro-keeps-your-data-secure",[181],"security write-up"," is where those promises live in more detail. ",[177,580,583],{"href":581,"rel":582},"https://www.perplexity.ai/help-center/en/articles/10672063-introduction-to-perplexity-connectors-for-enterprise-orgs",[181],"Enterprise connectors"," can pull files from Drive, OneDrive, and SharePoint into that answer loop. Deep research and Computer-style loops browse and assemble memos, decks, and dashboards — still orbiting the thread that answers a question. That is a legitimate category. Perplexity trained a generation to expect synthesis with links, not a blue list of pages.",[218,586,221],{"id":220},[223,588,589,595,601,607,613,618,623,628],{},[226,590,591,594],{},[229,592,593],{},"Answer engine."," You ask; you get a synthesis with links, not a blue list of pages. Perplexity trained a generation to expect that.",[226,596,597,600],{},[229,598,599],{},"Enterprise Pro."," Perplexity’s B2B workspace: team management, SSO, SOC 2, and a promise not to train on enterprise customer data.",[226,602,603,606],{},[229,604,605],{},"Connectors (Perplexity)."," Pull files from Drive, OneDrive, and SharePoint into the answer loop. The right standard for an answer engine people will upload files into. Not a write gate on a retailer portal.",[226,608,609,612],{},[229,610,611],{},"Deep research / Computer."," Longer browse-and-assemble loops — memos, decks, dashboards — still orbiting the thread that answers a question.",[226,614,615,617],{},[229,616,260],{}," In Nimbus, a shared workspace for one job — not another search thread.",[226,619,620,622],{},[229,621,272],{}," Official playbooks: how we change assortment, who signs, what “done” means.",[226,624,625,627],{},[229,626,278],{}," Changing a live system. You do not want an answer engine holding production credentials.",[226,629,630,633,634,637],{},[229,631,632],{},"Perception."," Asking Nimbus in ordinary language over ",[188,635,636],{},"your"," graph, wiki, and scoped systems — with the next step being a workstream, not another search.",[218,639,293],{"id":292},[174,641,642,643,647],{},"It is also not workplace search. ",[177,644,646],{"href":645},"nimbus-vs-glean","Glean"," is permission-aware find-the-file across the apps your company already uses. Perplexity is web-native synthesis that can also ingest your stuff. Do not shortlist them as the same line on an RFP. Connectors that pull Drive, OneDrive, and SharePoint into the answer loop are the right standard for an answer engine people will upload files into. They are not years of crawl-and-permission engineering, and they are not a write gate on a retailer portal.",[174,649,650,651,654,655,658,659,662,663,665],{},"Perplexity’s trust story is provenance of ",[188,652,653],{},"claims",": links, snippets, a trail a human can click. That is the right standard for web research. Limits: memory of ",[188,656,657],{},"decisions"," is still thread-shaped unless you file the answer somewhere else. Nimbus’s trust story is provenance of ",[188,660,661],{},"actions",": who ran, what the wiki said, what was approved, what changed in a live system. Public-web citations may appear inside a workstream. They are not the product. The ",[177,664,23],{"href":313}," is.",[174,667,668],{},"SOC 2 and a non-training term make the research workspace safer to use. They do not turn a brief into a signed portal update. Uploading customer or employee files into any research workspace is still your processing. Those terms help. They do not replace a purpose for what you put in the box, and they do not replace a human on a production login. Perplexity Enterprise governance is mostly “who may ask and what corpus they see.” Nimbus governance is “who may change what.” Different verb.",[174,670,671,672,676],{},"A healthy pattern: Perplexity (or another search-grounded assistant) for the public-web pass; Nimbus for the company pass and the write. Do not paste a Perplexity answer into Salesforce — or a retailer portal — as if it were a ",[177,673,675],{"href":674},"what-is-write-back-governance","release",". If you force Perplexity to do the operational job, you will bolt on brittle browser clicking and call it operations. If you force Nimbus to be the only web research tool, you will underuse an engine that is very good at cited public synthesis.",[174,678,679,680,683],{},"Role by role: a researcher or strategist wants cited answers from the web — Perplexity is in-category. A knowledge-work programme wants SSO, SOC 2, and a non-training term so people stop using the consumer tab; that is Enterprise Pro doing its job. RevOps and merchandising need the answer to become a signed change in a live system, not another thread. Legal cares what you uploaded into the research workspace; SOC 2 helps and does not replace purpose. Marketing should not buy Perplexity because “we need to show up in answer engines” — getting found is marketing; running the company is operations. Security should block ",[188,681,682],{},"production credentials"," in any research agent, not necessarily block Perplexity itself.",[174,685,686],{},"Three verbs sit near each other on RFPs. Perplexity synthesises (especially the web). Glean finds (especially workplace files with source permissions). Nimbus runs work. Most large companies will eventually own at least two.",[218,688,690],{"id":689},"when-perplexity-is-a-better-fit","When Perplexity is a better fit",[174,692,693],{},"Choose Perplexity when the job is web-grounded research with citations, you do not need gated writes, and you want an answer engine as the daily UX. Choose it as a complement to Nimbus, not as a stealth OS.",[174,695,696],{},"Do not choose Perplexity because “we need to show up in answer engines.” Getting found is marketing. Running the company is operations.",[174,698,699],{},"If you force Perplexity to do the operational job, you will bolt on brittle browser clicking and call it operations. If you force Nimbus to be the only web research tool, you will underuse an engine that is very good at cited public synthesis.",[174,701,702],{},"Keep an answer engine for public-web research if it helps. Route execution to Nimbus. That is a data-handling rule plus an operating model, not a ban. Block production credentials in any research agent. Allow cited research.",[218,704,354],{"id":353},[174,706,707,708,711,712,715],{},"A ",[177,709,710],{"href":32},"workstream"," is the job after the brief. ",[177,713,714],{"href":51},"Connectors"," link to the tools you already run: internal sales, a research feed if you have one, the portal if you attach it. Reads first. Writes off until a named person releases them.",[174,717,718,719,722,723,725],{},"Nimbus can look like an answer box when you ask the business a question. It is not Perplexity. See ",[177,720,721],{"href":36},"Perception"," and the ",[177,724,373],{"href":12},". Perception is ordinary language over the Lifecycle Graph, policies, teams, and integrations — in a product where the next step is governed work. It is not a citation engine over the public web.",[174,727,728,729,732],{},"A research-shaped ",[177,730,731],{"href":20},"agent team"," is grounded in wiki playbooks plus connectors, then a human release, then a graph record you can query next quarter.",[174,734,735,736,374],{},"See ",[177,737,39],{"href":40},[218,739,378],{"id":377},[380,741,743],{"id":742},"does-nimbus-replace-perplexity","Does Nimbus replace Perplexity?",[174,745,746],{},"No. Keep an answer engine for public-web research if it helps. Nimbus Perception is for company graph, wiki, and scoped systems.",[380,748,750],{"id":749},"does-perplexity-replace-nimbus","Does Perplexity replace Nimbus?",[174,752,753],{},"Only if “ask the web” is the entire AI programme. It does not replace workstreams, agent teams, or write gates.",[380,755,757],{"id":756},"is-asking-nimbus-just-perplexity-on-internal-data","Is asking Nimbus just Perplexity on internal data?",[174,759,760],{},"No. Perception is ordinary language over the Lifecycle Graph, policies, teams, and integrations — in a product where the next step is governed work. It is not a citation engine over the public web.",[380,762,764],{"id":763},"perplexity-vs-glean-vs-nimbus","Perplexity vs Glean vs Nimbus?",[174,766,767],{},"Perplexity synthesises (especially the web). Glean finds (especially workplace files with source permissions). Nimbus runs work. Three verbs. Most large companies will eventually own at least two.",[380,769,771],{"id":770},"should-we-block-perplexity-if-we-buy-nimbus","Should we block Perplexity if we buy Nimbus?",[174,773,774,775,777],{},"Not by default. Block ",[188,776,682],{}," in any research agent. Allow cited research. Route execution to Nimbus. That is a data-handling rule plus an operating model, not a ban.",[380,779,781],{"id":780},"can-we-paste-perplexity-answers-into-salesforce","Can we paste Perplexity answers into Salesforce?",[174,783,784],{},"You can. You should not treat that paste as a release. Provenance of claims (links you can click) is not provenance of actions (who signed, what changed). File the brief into a workstream if the next step is a live-system update.",[380,786,788],{"id":787},"who-should-own-perplexity-vs-nimbus","Who should own Perplexity vs Nimbus?",[174,790,791],{},"Research, strategy, and often the knowledge-work programme own the answer engine: who may ask, what files may be uploaded, SSO. Line operators own Nimbus workstreams that change assortment, CRM, or portals. Legal reviews what goes in the box. Security reviews credentials, not the existence of citations.",[380,793,795],{"id":794},"do-perplexity-connectors-mean-it-is-now-a-work-os","Do Perplexity connectors mean it is now a work OS?",[174,797,798],{},"No. Pulling Drive, OneDrive, and SharePoint into an answer loop is the right standard for a research workspace. It is not a write gate, not a workstream, and not a Lifecycle Graph. Deep research that assembles a memo is still a thread that answers a question.",[380,800,802],{"id":801},"what-should-a-procurement-pack-actually-compare","What should a procurement pack actually compare?",[174,804,805],{},"Compare a week of work, not a list of logos. For Perplexity, the test is: can a named role get a cited answer on an approved corpus without uploading a customer file to a personal account? For Nimbus, the test is: can the same organisation take that brief into a scoped job, keep CRM read-only until a named person signs, and still reconstruct the change next quarter? If the pack only asks “do you have connectors,” both products will look the same and you will have bought the wrong week.",[218,807,450],{"id":449},[174,809,810,457,814,462,817,374],{},[177,811,813],{"href":812},"what-is-enterprise-rag","What is enterprise RAG",[177,815,816],{"href":674},"What is write-back governance",[177,818,819],{"href":645},"Nimbus vs Glean",[218,821,468],{"id":467},[223,823,824,829,835,841],{},[226,825,826],{},[177,827,560],{"href":558,"rel":828},[181],[226,830,831],{},[177,832,834],{"href":569,"rel":833},[181],"Perplexity launches Enterprise Pro",[226,836,837],{},[177,838,840],{"href":575,"rel":839},[181],"How Perplexity Enterprise Pro keeps your data secure",[226,842,843],{},[177,844,846],{"href":581,"rel":845},[181],"Introduction to Perplexity connectors for enterprise orgs",{"title":155,"searchDepth":156,"depth":156,"links":848},[849,850,851,852,853,864,865],{"id":220,"depth":156,"text":221},{"id":292,"depth":156,"text":293},{"id":689,"depth":156,"text":690},{"id":353,"depth":156,"text":354},{"id":377,"depth":156,"text":378,"children":854},[855,856,857,858,859,860,861,862,863],{"id":742,"depth":503,"text":743},{"id":749,"depth":503,"text":750},{"id":756,"depth":503,"text":757},{"id":763,"depth":503,"text":764},{"id":770,"depth":503,"text":771},{"id":780,"depth":503,"text":781},{"id":787,"depth":503,"text":788},{"id":794,"depth":503,"text":795},{"id":801,"depth":503,"text":802},{"id":449,"depth":156,"text":450},{"id":467,"depth":156,"text":468},"Perplexity is an answer engine with sources; Nimbus is the work OS that turns those answers into a signed change in the systems you already run.","/blog/nimbus-vs-perplexity",{"title":548,"description":866},"blog/nimbus-vs-perplexity",[517,128,871,872,873],"answer-engines","research","enterprise-ai","AD-SW40-t5d7q34OguIcefVqwVmAvBbykPz2ZwxI1Q4",{"id":876,"title":877,"archived":149,"authors":150,"badge":878,"body":881,"date":513,"department":150,"description":1162,"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":1163,"relatedHeading":150,"seo":1164,"series":517,"sitemap":115,"status":150,"stem":1165,"subhead":150,"tags":1166,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":1170},"content/blog/nimbus-vs-openclaw.md","Nimbus vs OpenClaw: A Chat Bot on Your Phone, or a Company Workspace with Approvals?",{"label":167,"10|authors":879},[880],{"name":170,"to":120},{"type":152,"value":882,"toc":1144},[883,891,899,907,909,967,969,972,983,990,993,996,999,1003,1006,1009,1016,1018,1027,1030,1037,1044,1046,1050,1053,1057,1060,1064,1067,1071,1076,1080,1083,1087,1090,1094,1097,1101,1104,1106,1116,1118],[174,884,885,890],{},[177,886,889],{"href":887,"rel":888},"https://docs.openclaw.ai/",[181],"OpenClaw"," is a personal or team assistant you install and reach from the chat apps you already live in. Nimbus is a company workspace where a write into Salesforce waits for a named person — and RevOps can refuse it.",[174,892,893,894,898],{},"Both are “an agent.” They are not the same job. A WhatsApp number that can reach a shell is a privileged identity, whether the README is charming or not. The ",[177,895,897],{"href":887,"rel":896},[181],"official docs"," are clear about the audience: developers and power users who want a personal assistant they can message from anywhere, without handing their data to a hosted chatbot. That design is right for a homelab, a founder who wants Telegram on the train, or a tightly scoped internal bot that never sees customer data. It is popular because it works. Popularity is not a control system.",[174,900,901,902,906],{},"OpenClaw is an open-source project (it has also been known as Clawdbot and Moltbot) that you run on your own computer or server. One process sits in the middle; you connect Discord, Google Chat, iMessage, Microsoft Teams, Signal, Slack, Telegram, WhatsApp, and more. You pick the model. You pay that model bill. Setup can be minutes if you are comfortable installing software and pasting an API key. Community packs add tools; treat a marketplace install like unreviewed software with credentials. The ",[177,903,203],{"href":904,"rel":905},"https://github.com/openclaw/openclaw",[181]," is public. Self-hosting is the point. Self-hosting is also the obligation.",[218,908,221],{"id":220},[223,910,911,917,923,929,934,939,944,949],{},[226,912,913,916],{},[229,914,915],{},"OpenClaw."," An open-source project (it has also been known as Clawdbot and Moltbot) that you run on your own computer or server. One process sits in the middle; you connect Discord, Google Chat, iMessage, Microsoft Teams, Signal, Slack, Telegram, WhatsApp, and more.",[226,918,919,922],{},[229,920,921],{},"Self-hosted."," You pick the model. You pay that model bill. Setup can be minutes if you are comfortable installing software and pasting an API key.",[226,924,925,928],{},[229,926,927],{},"Skills / marketplace."," Community packs that add tools. Treat a marketplace install like unreviewed software with credentials.",[226,930,931,933],{},[229,932,260],{}," In Nimbus, a shared workspace for one job — people, tools, budget, and a finish line.",[226,935,936,938],{},[229,937,266],{}," AI specialists grouped like departments, assigned to the workstream.",[226,940,941,943],{},[229,942,278],{}," Changing a live system. If an agent can edit an opportunity from a Telegram chat, you no longer have a CRM. You have a group chat with side effects.",[226,945,946,948],{},[229,947,288],{}," The record of what ran, who approved, and what changed.",[226,950,951,954,955,960,961,966],{},[229,952,953],{},"Secure AI system development."," The ",[177,956,959],{"href":957,"rel":958},"https://www.ncsc.gov.uk/collection/guidelines-secure-ai-system-development",[181],"UK NCSC guidelines",", issued jointly with ",[177,962,965],{"href":963,"rel":964},"https://www.cisa.gov/news-events/news/dhs-cisa-and-uk-ncsc-release-joint-guidelines-secure-ai-system-development",[181],"CISA",": logging, monitoring, and not exposing sensitive data — whether you built the system or stitched it from tools and APIs.",[218,968,293],{"id":292},[174,970,971],{},"Anyone who can message the bot can try to become the bot. A viral internal bot is a classic “we use AI” slide. It is also a classic reason scaling stalls: nobody can say which token the bot uses, who is allowed to talk to it, or what it changed last Tuesday. OpenClaw’s scarce resource is reach: many messaging surfaces, one agent. Nimbus’s scarce resource is control: many operators and systems, one release process.",[174,973,974,975,979,980,982],{},"OpenClaw memory is whatever you attached: files, a store, community packs. Two people can run two OpenClaws and disagree about last week’s decision because each bot remembered a different thread. There is no company ",[177,976,978],{"href":977},"what-is-a-company-wiki-for-ai-agents","wiki"," product and no Lifecycle Graph of releases. Nimbus memory is three places you can show a colleague: the wiki (what we claim), ",[177,981,309],{"href":51}," (what Salesforce or the ledger claim), and the graph (what we did). That is what you show when someone asks, “What did we approve?”",[174,984,985,986,989],{},"A personal assistant on your phone and a system that updates customer records are not the same system, even if both answer in chat. The joint NCSC and CISA guidelines exist because the second one is an AI system you operate. Running the software on your own computer does not waive logging, monitoring, or ",[177,987,988],{"href":674},"write-back"," gates. Customer data in a WhatsApp-connected agent is still sensitive data in an AI system you operate. Someone else running the server reduces your upkeep. It does not give you workstreams, specialist teams, or a Lifecycle Graph. A service level on a machine is not a release process.",[174,991,992],{},"If an agent can edit an opportunity from a Telegram chat, you no longer have a CRM. You have a group chat with side effects. Skills from a marketplace make that easier, not safer. Treat a pack that adds tools like unreviewed software with credentials — because that is what it is.",[174,994,995],{},"Role by role: a developer or power user who wants Telegram on the train gets the product OpenClaw was designed for. Security should hear “privileged identity,” not “fun bot.” RevOps should refuse a write path that lives in a group chat. Finance cannot reconstruct last Tuesday from a thread only the bot remembered. IT asked to “just host it for the company” is being asked to become the platform team for a personal assistant. A COO counting GitHub stars is measuring excitement. Companies measure blast radius.",[174,997,998],{},"You can still want OpenClaw after a security conversation. Keep it contained: no production credentials, not a public WhatsApp number on company data, a named owner, and an exit — the proven job becomes a Nimbus workstream; the bot goes back to being personal. Personal agents can feed drafts into Nimbus workstreams. Do not let the chat bot hold write credentials to core systems.",[218,1000,1002],{"id":1001},"when-openclaw-is-a-better-fit","When OpenClaw is a better fit",[174,1004,1005],{},"Choose OpenClaw for personal productivity, home automation, and greenfield bots where you are the admin. Choose it when the blast radius is your own chats and files.",[174,1007,1008],{},"Do not choose OpenClaw as the company AI platform because it has more GitHub stars than last quarter’s shortlist. Stars measure excitement. Companies measure blast radius.",[174,1010,1011,1012,1015],{},"If you still want OpenClaw after a security conversation, keep it contained: no production credentials, not a public WhatsApp number on company data, a named owner, and an exit — the proven job becomes a Nimbus workstream; the bot goes back to being personal. Same layer as ",[177,1013,1014],{"href":421},"Hermes",": a personal assistant you look after. OpenClaw maximises channels. Hermes maximises skills and personal memory. Neither is a company OS.",[218,1017,354],{"id":353},[174,1019,1020,1021,1023,1024,1026],{},"Nimbus is the application you log into at work. Operators do not babysit a process on a server. They open a ",[177,1022,710],{"href":32}," with ",[177,1025,363],{"href":20}," and connectors.",[174,1028,1029],{},"Writes into those tools stay off until you turn them on. A quoted change sits until a human signs. You can think of Nimbus as the place OpenClaw users graduate to when the bot needs a company identity: production passwords leave the home server, writes pick up an approval, and the artefact lands where other people can find it.",[174,1031,1032,1033,1036],{},"Nimbus ",[177,1034,1035],{"href":51},"integrations"," are a catalogue you scope per workspace — more than 2,000 tools — read-only until write is enabled. The default if someone adds a dangerous skill is not “whatever the host allowed.” The default is: the connector cannot write until you say so.",[174,1038,1039,1040,210,1042,374],{},"See the ",[177,1041,373],{"href":12},[177,1043,39],{"href":40},[218,1045,378],{"id":377},[380,1047,1049],{"id":1048},"is-openclaw-a-nimbus-competitor","Is OpenClaw a Nimbus competitor?",[174,1051,1052],{},"On a spreadsheet that says “we want an agent,” yes. In practice, one is a chat assistant you install. One is a company operating system for work, approvals, and memory.",[380,1054,1056],{"id":1055},"can-we-put-openclaw-in-front-of-nimbus","Can we put OpenClaw in front of Nimbus?",[174,1058,1059],{},"Personal agents can feed drafts into Nimbus workstreams. Do not let the chat bot hold write credentials to core systems. Put those in Nimbus connector scopes.",[380,1061,1063],{"id":1062},"what-about-a-hosted-or-cloud-openclaw","What about a hosted or cloud OpenClaw?",[174,1065,1066],{},"Someone else running the server reduces your upkeep. It does not give you workstreams, specialist teams, or a Lifecycle Graph. A service level on a machine is not a release process.",[380,1068,1070],{"id":1069},"is-openclaw-the-same-as-hermes","Is OpenClaw the same as Hermes?",[174,1072,1073,1074,374],{},"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,1075,422],{"href":421},[380,1077,1079],{"id":1078},"does-self-hosting-mean-we-can-skip-logging-and-monitoring","Does self-hosting mean we can skip logging and monitoring?",[174,1081,1082],{},"No. Customer data in a WhatsApp-connected agent is still sensitive data in an AI system you operate. NCSC and CISA’s joint guidelines include logging, monitoring, and not exposing that data to unauthorised parties.",[380,1084,1086],{"id":1085},"can-we-standardise-the-company-on-openclaw-if-we-lock-down-who-can-message-it","Can we standardise the company on OpenClaw if we lock down who can message it?",[174,1088,1089],{},"Locking down who can talk to the bot is necessary and not sufficient. You still lack workstreams, specialist teams, a wiki, quoted writes, and a graph. A tightly scoped internal bot that never sees customer data can stay. A company platform cannot be “the bot, but with a allow-list.”",[380,1091,1093],{"id":1092},"who-owns-an-internal-openclaw","Who owns an internal OpenClaw?",[174,1095,1096],{},"Whoever runs the process owns the outcome: tokens, skills, who may message it, what it can reach. That is usually a developer, not RevOps. If the bot can change production data, you have given a personal-assistant owner a CRM duty they did not ask for. Move that duty to Nimbus governance.",[380,1098,1100],{"id":1099},"how-do-we-retire-a-viral-bot-without-a-fight","How do we retire a viral bot without a fight?",[174,1102,1103],{},"Name an exit in advance: the proven job becomes a workstream; production credentials leave the bot; the bot goes back to being personal. Stars and habit are not an argument to keep a WhatsApp number on company data.",[218,1105,450],{"id":449},[174,1107,1108,457,1112,462,1114,374],{},[177,1109,1111],{"href":1110},"what-is-shadow-ai","What is shadow AI",[177,1113,816],{"href":674},[177,1115,422],{"href":421},[218,1117,468],{"id":467},[223,1119,1120,1126,1132,1138],{},[226,1121,1122],{},[177,1123,1125],{"href":887,"rel":1124},[181],"OpenClaw documentation",[226,1127,1128],{},[177,1129,1131],{"href":904,"rel":1130},[181],"OpenClaw on GitHub",[226,1133,1134],{},[177,1135,1137],{"href":957,"rel":1136},[181],"UK NCSC, Guidelines for secure AI system development",[226,1139,1140],{},[177,1141,1143],{"href":963,"rel":1142},[181],"CISA and UK NCSC joint guidelines for secure AI system development",{"title":155,"searchDepth":156,"depth":156,"links":1145},[1146,1147,1148,1149,1150,1160,1161],{"id":220,"depth":156,"text":221},{"id":292,"depth":156,"text":293},{"id":1001,"depth":156,"text":1002},{"id":353,"depth":156,"text":354},{"id":377,"depth":156,"text":378,"children":1151},[1152,1153,1154,1155,1156,1157,1158,1159],{"id":1048,"depth":503,"text":1049},{"id":1055,"depth":503,"text":1056},{"id":1062,"depth":503,"text":1063},{"id":1069,"depth":503,"text":1070},{"id":1078,"depth":503,"text":1079},{"id":1085,"depth":503,"text":1086},{"id":1092,"depth":503,"text":1093},{"id":1099,"depth":503,"text":1100},{"id":449,"depth":156,"text":450},{"id":467,"depth":156,"text":468},"OpenClaw is a self-hosted agent you message from WhatsApp or Telegram; Nimbus is the company workspace where a CRM write waits for a named person.","/blog/nimbus-vs-openclaw",{"title":877,"description":1162},"blog/nimbus-vs-openclaw",[517,1167,1168,1169,302],"openclaw","clawdbot","self-hosted-agents","R2AG8WRzElJpkIZT-mTrXwUibawfvKwSz-PJQiq-YgU",{"enabled":149,"message":1172,"linkLabel":78,"linkHref":79,"id":1173,"title":1174,"archived":149,"authors":150,"badge":150,"body":1175,"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":1179,"relatedHeading":150,"seo":1180,"series":150,"sitemap":115,"status":150,"stem":1181,"subhead":150,"tags":150,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":1182},"We're hiring! Join the team building the Sentient Enterprise.","content/shared/hiring.md","Hiring banner",{"type":152,"value":1176,"toc":1177},[],{"title":155,"searchDepth":156,"depth":156,"links":1178},[],"/shared/hiring",{"title":1174,"description":155},"shared/hiring","-6bioYD7lKYokGUVU3ff4hHTvB-sDyOMuCptKHnojfk",{"fold":1184,"id":1188,"title":1189,"archived":149,"authors":150,"badge":150,"body":1190,"date":150,"department":150,"description":155,"extension":158,"eyebrow":150,"faqHeader":150,"faqs":150,"footerBand":1194,"headline":150,"image":150,"industry":150,"jobType":150,"listed":149,"location":150,"navigation":115,"openRoles":150,"pageLayout":150,"path":1198,"relatedHeading":150,"seo":1199,"series":150,"sitemap":115,"status":150,"stem":1200,"subhead":150,"tags":150,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":1201},{"headline":1185,"description":1186,"primaryLabel":8,"primaryTo":1187,"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":1191,"toc":1192},[],{"title":155,"searchDepth":156,"depth":156,"links":1193},[],{"headline":1195,"description":1196,"primaryLabel":8,"primaryTo":1187,"secondaryLabel":1197,"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":1189,"description":155},"shared/cta","YHK6Fb8AvCPR1zZq7R_xiXUG0hwhP5UxHA8Ix52JQp4",1787194071309]