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.

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.

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 security write-up is where those promises live in more detail. 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.

Words you’ll hear

Answer engine. You ask; you get a synthesis with links, not a blue list of pages. Perplexity trained a generation to expect that.
Enterprise Pro. Perplexity’s B2B workspace: team management, SSO, SOC 2, and a promise not to train on enterprise customer data.
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.
Deep research / Computer. Longer browse-and-assemble loops — memos, decks, dashboards — still orbiting the thread that answers a question.
Workstream. In Nimbus, a shared workspace for one job — not another search thread.
Wiki. Official playbooks: how we change assortment, who signs, what “done” means.
Write-back. Changing a live system. You do not want an answer engine holding production credentials.
Perception. Asking Nimbus in ordinary language over your graph, wiki, and scoped systems — with the next step being a workstream, not another search.

Why the difference matters

It is also not workplace search. 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.

Perplexity’s trust story is provenance of claims: links, snippets, a trail a human can click. That is the right standard for web research. Limits: memory of decisions is still thread-shaped unless you file the answer somewhere else. Nimbus’s trust story is provenance of 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 Lifecycle Graph is.

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.

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 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.

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 production credentials in any research agent, not necessarily block Perplexity itself.

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.

When Perplexity is a better fit

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.

Do not choose Perplexity because “we need to show up in answer engines.” Getting found is marketing. Running the company is operations.

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.

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.

How this shows up in Nimbus

A workstream is the job after the brief. 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.

Nimbus can look like an answer box when you ask the business a question. It is not Perplexity. See Perception and the 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.

A research-shaped agent team is grounded in wiki playbooks plus connectors, then a human release, then a graph record you can query next quarter.

See Governance.

Questions people actually ask

Does Nimbus replace Perplexity?

No. Keep an answer engine for public-web research if it helps. Nimbus Perception is for company graph, wiki, and scoped systems.

Does Perplexity replace Nimbus?

Only if “ask the web” is the entire AI programme. It does not replace workstreams, agent teams, or write gates.

Is asking Nimbus just Perplexity on internal data?

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.

Perplexity vs Glean vs Nimbus?

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.

Should we block Perplexity if we buy Nimbus?

Not by default. Block production credentials in any research agent. Allow cited research. Route execution to Nimbus. That is a data-handling rule plus an operating model, not a ban.

Can we paste Perplexity answers into Salesforce?

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.

Who should own Perplexity vs Nimbus?

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.

Do Perplexity connectors mean it is now a work OS?

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.

What should a procurement pack actually compare?

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.

What is enterprise RAG, What is write-back governance, and Nimbus vs Glean.

Nimbus vs Perplexity: Cited Answers from the Web, or Running the Work the Answer Implies?