[{"data":1,"prerenderedAt":1230},["ShallowReactive",2],{"site-nav-content":3,"hiring-banner-content":163,"blog:/blog/nimbus-vs-perplexity":175,"blog-index-copy":538,"blog:/blog/nimbus-vs-perplexity:surround":559,"site-cta-content":1211},{"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",{"enabled":149,"message":164,"linkLabel":78,"linkHref":79,"id":165,"title":166,"archived":149,"authors":150,"badge":150,"body":167,"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":171,"relatedHeading":150,"seo":172,"series":150,"sitemap":115,"status":150,"stem":173,"subhead":150,"tags":150,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":174},"We're hiring! Join the team building the Sentient Enterprise.","content/shared/hiring.md","Hiring banner",{"type":152,"value":168,"toc":169},[],{"title":155,"searchDepth":156,"depth":156,"links":170},[],"/shared/hiring",{"title":166,"description":155},"shared/hiring","-6bioYD7lKYokGUVU3ff4hHTvB-sDyOMuCptKHnojfk",{"id":176,"title":177,"archived":149,"authors":150,"badge":178,"body":183,"date":527,"department":150,"description":528,"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":529,"relatedHeading":150,"seo":530,"series":531,"sitemap":115,"status":150,"stem":532,"subhead":150,"tags":533,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":537},"content/blog/nimbus-vs-perplexity.md","Nimbus vs Perplexity: Cited Answers from the Web, or Running the Work the Answer Implies?",{"label":179,"10|authors":180},"Comparisons",[181],{"name":182,"to":120},"Nimbus Research",{"type":152,"value":184,"toc":507},[185,196,199,219,224,282,286,294,313,316,324,331,334,338,341,344,347,350,354,365,376,383,389,393,398,401,405,408,412,415,419,422,426,432,436,439,443,446,450,453,457,460,464,478,482],[186,187,188,195],"p",{},[189,190,194],"a",{"href":191,"rel":192},"https://www.perplexity.ai/enterprise",[193],"nofollow","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.",[186,197,198],{},"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.",[186,200,201,206,207,212,213,218],{},[189,202,205],{"href":203,"rel":204},"https://www.perplexity.ai/hub/blog/perplexity-launches-enterprise-pro",[193],"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 ",[189,208,211],{"href":209,"rel":210},"https://www.perplexity.ai/hub/blog/how-perplexity-enterprise-pro-keeps-your-data-secure",[193],"security write-up"," is where those promises live in more detail. ",[189,214,217],{"href":215,"rel":216},"https://www.perplexity.ai/help-center/en/articles/10672063-introduction-to-perplexity-connectors-for-enterprise-orgs",[193],"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.",[220,221,223],"h2",{"id":222},"words-youll-hear","Words you’ll hear",[225,226,227,235,241,247,253,259,265,271],"ul",{},[228,229,230,234],"li",{},[231,232,233],"strong",{},"Answer engine."," You ask; you get a synthesis with links, not a blue list of pages. Perplexity trained a generation to expect that.",[228,236,237,240],{},[231,238,239],{},"Enterprise Pro."," Perplexity’s B2B workspace: team management, SSO, SOC 2, and a promise not to train on enterprise customer data.",[228,242,243,246],{},[231,244,245],{},"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.",[228,248,249,252],{},[231,250,251],{},"Deep research / Computer."," Longer browse-and-assemble loops — memos, decks, dashboards — still orbiting the thread that answers a question.",[228,254,255,258],{},[231,256,257],{},"Workstream."," In Nimbus, a shared workspace for one job — not another search thread.",[228,260,261,264],{},[231,262,263],{},"Wiki."," Official playbooks: how we change assortment, who signs, what “done” means.",[228,266,267,270],{},[231,268,269],{},"Write-back."," Changing a live system. You do not want an answer engine holding production credentials.",[228,272,273,276,277,281],{},[231,274,275],{},"Perception."," Asking Nimbus in ordinary language over ",[278,279,280],"em",{},"your"," graph, wiki, and scoped systems — with the next step being a workstream, not another search.",[220,283,285],{"id":284},"why-the-difference-matters","Why the difference matters",[186,287,288,289,293],{},"It is also not workplace search. ",[189,290,292],{"href":291},"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.",[186,295,296,297,300,301,304,305,308,309,312],{},"Perplexity’s trust story is provenance of ",[278,298,299],{},"claims",": links, snippets, a trail a human can click. That is the right standard for web research. Limits: memory of ",[278,302,303],{},"decisions"," is still thread-shaped unless you file the answer somewhere else. Nimbus’s trust story is provenance of ",[278,306,307],{},"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 ",[189,310,23],{"href":311},"what-is-a-lifecycle-graph"," is.",[186,314,315],{},"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.",[186,317,318,319,323],{},"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 ",[189,320,322],{"href":321},"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.",[186,325,326,327,330],{},"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 ",[278,328,329],{},"production credentials"," in any research agent, not necessarily block Perplexity itself.",[186,332,333],{},"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.",[220,335,337],{"id":336},"when-perplexity-is-a-better-fit","When Perplexity is a better fit",[186,339,340],{},"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.",[186,342,343],{},"Do not choose Perplexity because “we need to show up in answer engines.” Getting found is marketing. Running the company is operations.",[186,345,346],{},"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.",[186,348,349],{},"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.",[220,351,353],{"id":352},"how-this-shows-up-in-nimbus","How this shows up in Nimbus",[186,355,356,357,360,361,364],{},"A ",[189,358,359],{"href":32},"workstream"," is the job after the brief. ",[189,362,363],{"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.",[186,366,367,368,371,372,375],{},"Nimbus can look like an answer box when you ask the business a question. It is not Perplexity. See ",[189,369,370],{"href":36},"Perception"," and the ",[189,373,374],{"href":12},"overview",". 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.",[186,377,378,379,382],{},"A research-shaped ",[189,380,381],{"href":20},"agent team"," is grounded in wiki playbooks plus connectors, then a human release, then a graph record you can query next quarter.",[186,384,385,386,388],{},"See ",[189,387,39],{"href":40},".",[220,390,392],{"id":391},"questions-people-actually-ask","Questions people actually ask",[394,395,397],"h3",{"id":396},"does-nimbus-replace-perplexity","Does Nimbus replace Perplexity?",[186,399,400],{},"No. Keep an answer engine for public-web research if it helps. Nimbus Perception is for company graph, wiki, and scoped systems.",[394,402,404],{"id":403},"does-perplexity-replace-nimbus","Does Perplexity replace Nimbus?",[186,406,407],{},"Only if “ask the web” is the entire AI programme. It does not replace workstreams, agent teams, or write gates.",[394,409,411],{"id":410},"is-asking-nimbus-just-perplexity-on-internal-data","Is asking Nimbus just Perplexity on internal data?",[186,413,414],{},"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.",[394,416,418],{"id":417},"perplexity-vs-glean-vs-nimbus","Perplexity vs Glean vs Nimbus?",[186,420,421],{},"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.",[394,423,425],{"id":424},"should-we-block-perplexity-if-we-buy-nimbus","Should we block Perplexity if we buy Nimbus?",[186,427,428,429,431],{},"Not by default. Block ",[278,430,329],{}," in any research agent. Allow cited research. Route execution to Nimbus. That is a data-handling rule plus an operating model, not a ban.",[394,433,435],{"id":434},"can-we-paste-perplexity-answers-into-salesforce","Can we paste Perplexity answers into Salesforce?",[186,437,438],{},"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.",[394,440,442],{"id":441},"who-should-own-perplexity-vs-nimbus","Who should own Perplexity vs Nimbus?",[186,444,445],{},"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.",[394,447,449],{"id":448},"do-perplexity-connectors-mean-it-is-now-a-work-os","Do Perplexity connectors mean it is now a work OS?",[186,451,452],{},"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.",[394,454,456],{"id":455},"what-should-a-procurement-pack-actually-compare","What should a procurement pack actually compare?",[186,458,459],{},"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.",[220,461,463],{"id":462},"related-reading","Related reading",[186,465,466,470,471,474,475,388],{},[189,467,469],{"href":468},"what-is-enterprise-rag","What is enterprise RAG",", ",[189,472,473],{"href":321},"What is write-back governance",", and ",[189,476,477],{"href":291},"Nimbus vs Glean",[220,479,481],{"id":480},"sources","Sources",[225,483,484,489,495,501],{},[228,485,486],{},[189,487,194],{"href":191,"rel":488},[193],[228,490,491],{},[189,492,494],{"href":203,"rel":493},[193],"Perplexity launches Enterprise Pro",[228,496,497],{},[189,498,500],{"href":209,"rel":499},[193],"How Perplexity Enterprise Pro keeps your data secure",[228,502,503],{},[189,504,506],{"href":215,"rel":505},[193],"Introduction to Perplexity connectors for enterprise orgs",{"title":155,"searchDepth":156,"depth":156,"links":508},[509,510,511,512,513,525,526],{"id":222,"depth":156,"text":223},{"id":284,"depth":156,"text":285},{"id":336,"depth":156,"text":337},{"id":352,"depth":156,"text":353},{"id":391,"depth":156,"text":392,"children":514},[515,517,518,519,520,521,522,523,524],{"id":396,"depth":516,"text":397},3,{"id":403,"depth":516,"text":404},{"id":410,"depth":516,"text":411},{"id":417,"depth":516,"text":418},{"id":424,"depth":516,"text":425},{"id":434,"depth":516,"text":435},{"id":441,"depth":516,"text":442},{"id":448,"depth":516,"text":449},{"id":455,"depth":516,"text":456},{"id":462,"depth":156,"text":463},{"id":480,"depth":156,"text":481},"2026-08-17","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":177,"description":528},"comparisons","blog/nimbus-vs-perplexity",[531,128,534,535,536],"answer-engines","research","enterprise-ai","AD-SW40-t5d7q34OguIcefVqwVmAvBbykPz2ZwxI1Q4",{"hero":539,"id":541,"title":542,"archived":149,"authors":150,"badge":150,"body":543,"date":150,"department":150,"description":547,"extension":158,"eyebrow":548,"faqHeader":150,"faqs":150,"footerBand":549,"headline":150,"image":150,"industry":150,"jobType":150,"listed":149,"location":150,"navigation":115,"openRoles":150,"pageLayout":150,"path":60,"relatedHeading":555,"seo":556,"series":150,"sitemap":115,"status":150,"stem":557,"subhead":150,"tags":150,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":558},{"filename":540},"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":544,"toc":545},[],{"title":155,"searchDepth":156,"depth":156,"links":546},[],"Deep dives into pre-cognitive intelligence, sentient enterprises, and the evolving landscape of AI-driven business transformation.","Latest Research",{"headline":550,"description":551,"primaryLabel":552,"primaryTo":553,"secondaryLabel":554,"secondaryTo":12},"Stay at the frontier.","Subscribe for product updates and new insights.","Subscribe","/newsletter","Explore the platform","More research",{"title":542,"description":547},"blog/index","eK1RCXdDW8nfLSyKRXGB1mJm9FAmhAO6GWXwNKOMNVE",[560,889],{"id":561,"title":562,"archived":149,"authors":150,"badge":563,"body":566,"date":527,"department":150,"description":880,"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":881,"relatedHeading":150,"seo":882,"series":531,"sitemap":115,"status":150,"stem":883,"subhead":150,"tags":884,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":888},"content/blog/nimbus-vs-salesforce-agentforce.md","Nimbus vs Salesforce Agentforce: The Right Agent Inside Salesforce, or Work Across the Company?",{"label":179,"10|authors":564},[565],{"name":182,"to":120},{"type":152,"value":567,"toc":862},[568,580,583,586,588,639,641,662,665,671,685,688,703,706,716,719,723,726,729,732,734,741,748,755,757,761,764,768,771,775,778,782,785,789,792,796,804,808,815,819,822,824,835,837],[186,569,570,575,576,579],{},[189,571,574],{"href":572,"rel":573},"https://www.salesforce.com/agentforce/",[193],"Salesforce Agentforce"," is the right agent ",[278,577,578],{},"inside Salesforce",". Nimbus is for work that also involves Drive, legal, and finance — with a lasting record of who signed off.",[186,581,582],{},"Nimbus will call Salesforce. It does not try to be Salesforce. That is the point. CRM platforms that pretend to be the only operating layer become unmaintainable outside the org. Operating layers that pretend to be CRM become untrustworthy on pipeline. Customer and pipeline truth live in Salesforce. Cross-department jobs that also live in Drive and legal email need a place that is not only field history on the opportunity.",[186,584,585],{},"Agentforce (including Agentforce 360) is Salesforce’s agent product family sitting on Sales, Service, Marketing, Commerce, and related clouds. The 2026 shape that matters to operators: a reasoning engine that can follow scripted, reliable steps and call a model only where judgment is required; a builder where admins put conditionals and hand-offs in a readable script, not only in a prompt; Data 360 (formerly Data Cloud) as the profile fabric; and actions that update records, launch flows, call APIs, and behave the way your industry cloud already behaves. Model choice inside Salesforce is expanding (OpenAI, Anthropic on Amazon’s cloud, Google’s Gemini among options). Service-grade voice and channels come with Salesforce-shaped auditability. The buyer is usually the Salesforce platform owner, RevOps, or customer service.",[220,587,223],{"id":222},[225,589,590,596,602,608,613,618,627,633],{},[228,591,592,595],{},[231,593,594],{},"Agentforce / Agentforce 360."," Salesforce’s agent product family sitting on Sales, Service, Marketing, Commerce, and related clouds.",[228,597,598,601],{},[231,599,600],{},"Data 360."," Formerly Data Cloud. The layer that unifies customer profiles and unstructured context inside Salesforce.",[228,603,604,607],{},[231,605,606],{},"Einstein Trust Layer."," Grounding in CRM data, masking of sensitive fields, toxicity detection, an audit trail, and zero data retention with LLM partners. CRM-native trust. Not a company-wide work ledger.",[228,609,610,612],{},[231,611,257],{}," In Nimbus, a shared workspace for one job that can include Drive, legal, and finance on the same canvas as CRM.",[228,614,615,617],{},[231,616,263],{}," Official playbooks — including when a discount is an exception.",[228,619,620,622,623,626],{},[231,621,269],{}," Changing a live system. Writes to Salesforce are first-class in Agentforce. In Nimbus they are ",[278,624,625],{},"not"," default-on. They are gated, quoted, and recorded.",[228,628,629,632],{},[231,630,631],{},"Lifecycle Graph."," A lasting record of the programme, not only the field history on the opportunity.",[228,634,635,638],{},[231,636,637],{},"Agent graph (Agentforce)."," A reasoning map for a turn. Not the same as Nimbus’s operational ledger.",[220,640,285],{"id":284},[186,642,643,644,649,650,655,656,661],{},"Success looks like: a service agent resolves a case, a sales agent updates opportunity fields, a flow still fires, the admin can preview what the agent did on the record. Grounding is strongest where Data 360 and the org are clean. It is weakest where the work is not a Salesforce object. Trust inside that org is the ",[189,645,648],{"href":646,"rel":647},"https://developer.salesforce.com/docs/ai/agentforce/guide/trust.html",[193],"Einstein Trust Layer",". Salesforce’s ",[189,651,654],{"href":652,"rel":653},"https://www.salesforce.com/artificial-intelligence/trusted-ai/",[193],"Trusted AI"," pages and the ",[189,657,660],{"href":658,"rel":659},"https://trailhead.salesforce.com/content/learn/modules/the-einstein-trust-layer/meet-the-einstein-trust-layer",[193],"Trailhead Trust Layer module"," describe the same stack: grounding in CRM data, masking of sensitive fields, toxicity detection, an audit trail, and zero data retention with LLM partners. That is CRM-native trust. It is not a company-wide work ledger.",[186,663,664],{},"Two jobs get conflated in every Agentforce demo.",[186,666,667,670],{},[231,668,669],{},"Update the next step on the opportunity."," Agentforce is the native answer. A sales agent with actions on Opportunity, maybe a flow, maybe a Slack ping via Salesforce. Ideal if the work already lives in Salesforce. Writes to Salesforce are first-class. Sharing rules are the permission model. That is the product working as designed.",[186,672,673,676,677,680,681,684],{},[231,674,675],{},"Write the pricing-exception memo, involve legal, update CRM, and file what happened."," You can script pieces in Agentforce. Legal, Drive, and the memo are someone else’s system unless you pipe everything into Data 360. In Nimbus, this is a ",[189,678,359],{"href":679},"what-is-an-ai-workstream",": connector scopes, a person on the write, Salesforce still the official home of the opportunity, Nimbus the place the cross-department job ran. The Trust Layer is how Salesforce keeps CRM data from leaking into LLM partners and how it logs prompts, toxicity scores, and user feedback ",[278,682,683],{},"on the record",". A pricing exception that also lives in Drive and legal email is a cross-function workflow. Do not ask the Trust Layer to be the memo, the legal comment, and the named signer outside the org.",[186,686,687],{},"A healthy split:",[689,690,691,694,697],"ol",{},[228,692,693],{},"Customer and pipeline truth live in Salesforce (plus Data 360 if you have paid for unification).",[228,695,696],{},"Agentforce handles in-CRM actions where Salesforce sharing rules are the product.",[228,698,699,700,388],{},"Nimbus agents read Salesforce under connector scope, operate across the rest of the stack, and write back only through ",[189,701,702],{"href":40},"governance",[186,704,705],{},"Skipping (1) and asking any operating layer to “just know ARR” is how you ship two pipelines. Dual write without a field-level policy is how you get sync fights. Default: Agentforce for interactive, in-CRM actions; Nimbus for batched, cross-system, approval-heavy programmes. Read-only Nimbus plus Agentforce writes is a valid starting posture. Agree the fields.",[186,707,708,709,712,713,388],{},"Role by role: a Salesforce platform owner, RevOps, or customer-service lead wants an agent on a Salesforce object — Agentforce is the fit, including service voice and in-app sales agents. Legal and finance sitting on a pricing exception need a canvas that is not only the org. Security will like the Trust Layer for CRM data and LLM partners, and still want a ledger of releases that is not only field history. A CIO who already paid for Einstein or Agentforce credits should ",[278,710,711],{},"use"," Agentforce where it is strong, not stretch it into an operating layer because the credits are sunk. Credits on CRM turns do not buy you model choice across the rest of the business, or a graph of non-CRM decisions. See ",[189,714,715],{"href":45},"models",[186,717,718],{},"Both mention graphs. They are not the same. Agentforce’s agent graph is a reasoning map for a turn. Nimbus’s Lifecycle Graph is an operational ledger of work, agents, and releases. Collapsing the terms is how you buy a CRM agent and think you bought institutional memory.",[220,720,722],{"id":721},"when-agentforce-is-a-better-fit","When Agentforce is a better fit",[186,724,725],{},"Choose Agentforce when the job is an agent on a Salesforce object, sharing rules are the permission model you need, and Data 360 is (or will be) the profile fabric. Choose it for service voice, in-app sales agents, and any workflow that should never leave the org.",[186,727,728],{},"Do not choose Agentforce as a stealth company operating layer. You will spend a year on Data 360 and agent scripts and still lack workstreams for everything that is not a Salesforce record.",[186,730,731],{},"Some organisations will run both. That is coherent if you do not pretend Agentforce’s turn-by-turn reasoning graph is a Lifecycle Graph. Attach Salesforce as a connector, keep Nimbus read-only at first, open writes through governance where the programme is batched and cross-system. Agentforce plus Data 360 is the Salesforce-platform path. They can coexist.",[220,733,353],{"id":352},[186,735,736,737,740],{},"Nimbus’s knowledge is wiki plus ",[189,738,739],{"href":51},"connectors"," plus Lifecycle Graph. Wiki is how we run the business. Connectors are live systems — Salesforce is one of them, not the universe. The graph is what we decided after we saw the account.",[186,742,743,744,747],{},"You can ",[189,745,746],{"href":12},"set Nimbus up yourselves"," and attach Salesforce as a connector. Agentforce at scale is a Salesforce implementation: Data 360, sharing, agent scripts, often a partner. That is rational inside CRM. It is not how you stand up cross-company AI work. You do not need a Salesforce consulting partner to use Nimbus with Salesforce. Attach it, keep it read-only, open writes through governance.",[186,749,385,750,371,753,388],{},[189,751,752],{"href":32},"workstreams",[189,754,23],{"href":24},[220,756,392],{"id":391},[394,758,760],{"id":759},"does-nimbus-replace-agentforce","Does Nimbus replace Agentforce?",[186,762,763],{},"Not inside Salesforce-native service and sales motions. Nimbus can read and update Salesforce through governed connectors. It should not be the official home of opportunities and cases.",[394,765,767],{"id":766},"does-agentforce-replace-nimbus","Does Agentforce replace Nimbus?",[186,769,770],{},"Not as a place departments finish cross-system work. You can script impressive agents in the builder. You still need a company wiki, specialist teams for non-CRM work, and a ledger of releases that is not only field history.",[394,772,774],{"id":773},"do-we-need-a-salesforce-consulting-partner-to-use-nimbus-with-salesforce","Do we need a Salesforce consulting partner to use Nimbus with Salesforce?",[186,776,777],{},"No. Attach Salesforce as a connector, keep it read-only, open writes through governance. That is the self-service path. Agentforce plus Data 360 is the Salesforce-platform path. They can coexist.",[394,779,781],{"id":780},"both-mention-graphs-are-they-the-same","Both mention graphs. Are they the same?",[186,783,784],{},"No. Agentforce’s agent graph is a reasoning map for a turn. Nimbus’s Lifecycle Graph is an operational ledger of work, agents, and releases. Collapsing the terms is how you buy a CRM agent and think you bought institutional memory.",[394,786,788],{"id":787},"should-nimbus-write-to-salesforce-or-should-agentforce","Should Nimbus write to Salesforce, or should Agentforce?",[186,790,791],{},"Default: Agentforce for interactive, in-CRM actions; Nimbus for batched, cross-system, approval-heavy programmes. Agree the fields. Start read-only on the Nimbus side if you need a clean split.",[394,793,795],{"id":794},"we-already-paid-for-einstein-agentforce-credits-why-add-nimbus","We already paid for Einstein / Agentforce credits. Why add Nimbus?",[186,797,798,799,801,802,388],{},"Because credits on CRM turns do not buy you model choice across the rest of the business, or a graph of non-CRM decisions. Sunk cost on Agentforce is a reason to ",[278,800,711],{}," Agentforce where it is strong, not a reason to stretch it into an operating layer. See ",[189,803,715],{"href":45},[394,805,807],{"id":806},"who-owns-agentforce-vs-nimbus","Who owns Agentforce vs Nimbus?",[186,809,810,811,814],{},"The Salesforce platform owner, RevOps, or customer service typically own Agentforce: sharing rules, Data 360, agent scripts. Line operators outside the org — legal, finance, teams living in Drive — own Nimbus workstreams for those jobs. Security reviews the Trust Layer ",[278,812,813],{},"and"," Nimbus write gates. Do not give one “CRM AI” owner both products and expect them to notice the job split.",[394,816,818],{"id":817},"can-we-start-with-read-only-nimbus-and-agentforce-writes","Can we start with read-only Nimbus and Agentforce writes?",[186,820,821],{},"Yes. That is a valid starting posture. Salesforce remains the system of record for the opportunity. Nimbus reads under connector scope. Writes that are interactive and in-CRM stay in Agentforce. Promote Nimbus writes later only where the programme is batched, cross-system, and approval-heavy — and only after you agree the fields.",[220,823,463],{"id":462},[186,825,826,470,828,474,831,388],{},[189,827,473],{"href":321},[189,829,830],{"href":311},"What is a lifecycle graph",[189,832,834],{"href":833},"what-is-human-in-the-loop-ai","What is human-in-the-loop AI",[220,836,481],{"id":480},[225,838,839,844,850,856],{},[228,840,841],{},[189,842,574],{"href":572,"rel":843},[193],[228,845,846],{},[189,847,849],{"href":646,"rel":848},[193],"Agentforce Trust Layer",[228,851,852],{},[189,853,855],{"href":652,"rel":854},[193],"Salesforce Trusted AI",[228,857,858],{},[189,859,861],{"href":658,"rel":860},[193],"Trailhead: Meet the Einstein Trust Layer",{"title":155,"searchDepth":156,"depth":156,"links":863},[864,865,866,867,868,878,879],{"id":222,"depth":156,"text":223},{"id":284,"depth":156,"text":285},{"id":721,"depth":156,"text":722},{"id":352,"depth":156,"text":353},{"id":391,"depth":156,"text":392,"children":869},[870,871,872,873,874,875,876,877],{"id":759,"depth":516,"text":760},{"id":766,"depth":516,"text":767},{"id":773,"depth":516,"text":774},{"id":780,"depth":516,"text":781},{"id":787,"depth":516,"text":788},{"id":794,"depth":516,"text":795},{"id":806,"depth":516,"text":807},{"id":817,"depth":516,"text":818},{"id":462,"depth":156,"text":463},{"id":480,"depth":156,"text":481},"Agentforce is the right agent layer inside Salesforce; Nimbus is for jobs that also involve Drive, legal, finance, and a lasting record of who signed off.","/blog/nimbus-vs-salesforce-agentforce",{"title":562,"description":880},"blog/nimbus-vs-salesforce-agentforce",[531,885,886,887,536],"salesforce","agentforce","crm","d6V391GhZVmfVq-GDzAlC7Xdi-6EMvlHgUjSv9K3h08",{"id":890,"title":891,"archived":149,"authors":150,"badge":892,"body":895,"date":527,"department":150,"description":1202,"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":1203,"relatedHeading":150,"seo":1204,"series":531,"sitemap":115,"status":150,"stem":1205,"subhead":150,"tags":1206,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":1210},"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":179,"10|authors":893},[894],{"name":182,"to":120},{"type":152,"value":896,"toc":1184},[897,905,916,937,939,1000,1002,1005,1011,1023,1026,1029,1036,1040,1047,1050,1053,1056,1058,1061,1070,1075,1077,1081,1084,1088,1091,1095,1098,1102,1105,1109,1121,1125,1130,1134,1137,1141,1144,1146,1157,1159],[186,898,899,904],{},[189,900,903],{"href":901,"rel":902},"https://paperclip.ing/",[193],"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.",[186,906,907,908,911,912,915],{},"Paperclip is multiplayer for ",[278,909,910],{},"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 ",[278,913,914],{},"in",", not the scheduler that wakes them.",[186,917,918,919,924,925,930,931,936],{},"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 ",[189,920,923],{"href":921,"rel":922},"https://github.com/paperclipai/paperclip",[193],"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. ",[189,926,929],{"href":927,"rel":928},"https://docs.crewai.com/",[193],"CrewAI"," and ",[189,932,935],{"href":933,"rel":934},"https://arxiv.org/abs/2308.00352",[193],"MetaGPT"," are the research-and-builder names for that orchestration category. Paperclip is that category as a product you hire into.",[220,938,223],{"id":222},[225,940,941,951,964,970,975,981,986,995],{},[228,942,943,946,947,950],{},[231,944,945],{},"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 ",[189,948,923],{"href":921,"rel":949},[193]," is public; you can run it yourself.",[228,952,953,956,957,930,960,963],{},[231,954,955],{},"Orchestration."," Coordinating several agents. ",[189,958,929],{"href":927,"rel":959},[193],[189,961,935],{"href":933,"rel":962},[193]," are the research-and-builder names for that category. Paperclip is that category as a product you hire into.",[228,965,966,969],{},[231,967,968],{},"Agent budget."," Cap the worker, warn at 80%, pause at 100%. Necessary cost control. Not the same as stopping a bad write.",[228,971,972,974],{},[231,973,257],{}," In Nimbus, a shared workspace for one job — the ticket a non-engineer can actually run.",[228,976,977,980],{},[231,978,979],{},"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.",[228,982,983,985],{},[231,984,263],{}," Official playbooks those teams must respect.",[228,987,988,990,991,994],{},[231,989,269],{}," Changing a live system. Paperclip’s FAQ is frank: it governs what agents do ",[278,992,993],{},"to Paperclip"," (hiring, strategy). Your agents are your own, and you secure them however you want.",[228,996,997,999],{},[231,998,631],{}," What ran, who approved, and what changed — so next quarter’s team does not relitigate the exception from Slack archaeology.",[220,1001,285],{"id":284},[186,1003,1004],{},"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.",[186,1006,1007,1008,1010],{},"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 ",[189,1009,702],{"href":40},". Cap-at-100% is necessary. It is not the same as stopping a bad write.",[186,1012,1013,1014,1016,1017,1019,1020,1022],{},"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 ",[189,1015,739],{"href":51}," plus the ",[189,1018,23],{"href":311}," 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 ",[278,1021,993],{}," (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.",[186,1024,1025],{},"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.",[186,1027,1028],{},"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.",[186,1030,1031,1032,1035],{},"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 ",[278,1033,1034],{},"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.",[220,1037,1039],{"id":1038},"when-paperclip-is-a-better-fit","When Paperclip is a better fit",[186,1041,1042,1043,1046],{},"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 ",[278,1044,1045],{},"is"," building an agent OS and you need that scheduler while you build the rest.",[186,1048,1049],{},"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.",[186,1051,1052],{},"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.",[186,1054,1055],{},"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.",[220,1057,353],{"id":352},[186,1059,1060],{},"Nimbus is the application layer a Head of Ops opens without assembling a roster of third-party bots on day one.",[186,1062,1063,1064,930,1067,1069],{},"You attach connectors under a read-only default. Humans release writes. You get specialist teams and a canvas, then you attach systems. See ",[189,1065,1066],{"href":20},"agent teams",[189,1068,752],{"href":32},". Spend is capped in NTUs so a long-running job cannot silently burn the month — and the write still waits for a signer.",[186,1071,1072,1073,388],{},"Start at the ",[189,1074,374],{"href":12},[220,1076,392],{"id":391},[394,1078,1080],{"id":1079},"is-nimbus-paperclip-with-a-nicer-screen","Is Nimbus “Paperclip with a nicer screen”?",[186,1082,1083],{},"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.",[394,1085,1087],{"id":1086},"can-paperclip-orchestrate-nimbus","Can Paperclip orchestrate Nimbus?",[186,1089,1090],{},"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.",[394,1092,1094],{"id":1093},"open-source-vs-a-hosted-product-which-lock-in-is-worse","Open source vs a hosted product — which lock-in is worse?",[186,1096,1097],{},"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.",[394,1099,1101],{"id":1100},"do-we-need-paperclip-if-we-only-have-one-agent","Do we need Paperclip if we only have one agent?",[186,1103,1104],{},"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.",[394,1106,1108],{"id":1107},"how-does-paperclip-relate-to-openclaw-and-hermes","How does Paperclip relate to OpenClaw and Hermes?",[186,1110,1111,1112,930,1116,1120],{},"OpenClaw and Hermes are employees. Paperclip is the org chart. Nimbus is the company plus the office. See ",[189,1113,1115],{"href":1114},"nimbus-vs-openclaw","Nimbus vs OpenClaw",[189,1117,1119],{"href":1118},"nimbus-vs-hermes","Nimbus vs Hermes",". Buying all three still does not give you a Lifecycle Graph.",[394,1122,1124],{"id":1123},"can-we-migrate-from-paperclip-to-nimbus","Can we migrate from Paperclip to Nimbus?",[186,1126,1127,1128,1035],{},"Treat the workers as prototypes. Recreate the ",[278,1129,1034],{},[394,1131,1133],{"id":1132},"does-a-budget-cap-replace-write-back-governance","Does a budget cap replace write-back governance?",[186,1135,1136],{},"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.",[394,1138,1140],{"id":1139},"who-should-run-paperclip-if-we-keep-it","Who should run Paperclip if we keep it?",[186,1142,1143],{},"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.",[220,1145,463],{"id":462},[186,1147,1148,470,1152,474,1155,388],{},[189,1149,1151],{"href":1150},"what-is-multi-agent-ai","What is multi-agent AI",[189,1153,1154],{"href":679},"What is an AI workstream",[189,1156,1115],{"href":1114},[220,1158,481],{"id":480},[225,1160,1161,1166,1172,1178],{},[228,1162,1163],{},[189,1164,903],{"href":901,"rel":1165},[193],[228,1167,1168],{},[189,1169,1171],{"href":921,"rel":1170},[193],"Paperclip on GitHub",[228,1173,1174],{},[189,1175,1177],{"href":927,"rel":1176},[193],"CrewAI documentation",[228,1179,1180],{},[189,1181,1183],{"href":933,"rel":1182},[193],"Hong et al., MetaGPT (arXiv:2308.00352)",{"title":155,"searchDepth":156,"depth":156,"links":1185},[1186,1187,1188,1189,1190,1200,1201],{"id":222,"depth":156,"text":223},{"id":284,"depth":156,"text":285},{"id":1038,"depth":156,"text":1039},{"id":352,"depth":156,"text":353},{"id":391,"depth":156,"text":392,"children":1191},[1192,1193,1194,1195,1196,1197,1198,1199],{"id":1079,"depth":516,"text":1080},{"id":1086,"depth":516,"text":1087},{"id":1093,"depth":516,"text":1094},{"id":1100,"depth":516,"text":1101},{"id":1107,"depth":516,"text":1108},{"id":1123,"depth":516,"text":1124},{"id":1132,"depth":516,"text":1133},{"id":1139,"depth":516,"text":1140},{"id":462,"depth":156,"text":463},{"id":480,"depth":156,"text":481},"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":891,"description":1202},"blog/nimbus-vs-paperclip",[531,1207,1208,1209,702],"paperclip","multi-agent","orchestration","9v34C0UEdjpM1myjS2p6Ck-9_OOxTapIYCAT9v4fM2I",{"fold":1212,"id":1216,"title":1217,"archived":149,"authors":150,"badge":150,"body":1218,"date":150,"department":150,"description":155,"extension":158,"eyebrow":150,"faqHeader":150,"faqs":150,"footerBand":1222,"headline":150,"image":150,"industry":150,"jobType":150,"listed":149,"location":150,"navigation":115,"openRoles":150,"pageLayout":150,"path":1226,"relatedHeading":150,"seo":1227,"series":150,"sitemap":115,"status":150,"stem":1228,"subhead":150,"tags":150,"video":150,"whyJoin":150,"workplaceType":150,"__hash__":1229},{"headline":1213,"description":1214,"primaryLabel":8,"primaryTo":1215,"secondaryLabel":554,"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":1219,"toc":1220},[],{"title":155,"searchDepth":156,"depth":156,"links":1221},[],{"headline":1223,"description":1224,"primaryLabel":8,"primaryTo":1215,"secondaryLabel":1225,"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":1217,"description":155},"shared/cta","YHK6Fb8AvCPR1zZq7R_xiXUG0hwhP5UxHA8Ix52JQp4",1787194064857]