Cohere North vs Perplexity Assistant for Android

“The primitive here is: a packaged RAG-plus-retrieval stack running inside your VPC, with Cohere's models baked in rather than bolted on. That's a real thing engineers actually want — avoiding the "pipe everything to OpenAI" conversation with legal. The DX bet is that platform teams would rather configure a turnkey deployment than wire together a vector DB, an embedding service, and a completion API separately. That's the right bet for enterprise environments where the alternative is a six-month procurement cycle, not a weekend script. What I can't verify without getting my hands on it is whether the RAG pipeline is genuinely composable or just a black box with YAML knobs — that distinction matters enormously for teams who have non-standard retrieval logic. If the pipelines expose clean interfaces and don't force you into Cohere's opinionated chunking strategy, this ships confidently; if it's a wizard that spits out an iframe, it's a different story.”

“The primitive here is a hybrid inference router — compressed model runs locally, routes to cloud when the query exceeds local capability. That's a real engineering decision, not a marketing one, and the tradeoff is honest: you lose fidelity on hard questions but gain offline availability on simple ones. The DX for end users is cleaner than I expected — no configuration, the routing is invisible. What I can't verify is the boundary: Perplexity hasn't published the model architecture, compression ratio, or the heuristic for when it escalates to cloud, so the 'offline reasoning' claim is partially a black box. Ships because the hybrid routing pattern is the right bet; would ship harder if they opened the model card.”

“Category: enterprise AI deployment platform, direct competitors are Azure OpenAI on Your Data, AWS Bedrock with VPC isolation, and Google Vertex AI. Cohere's actual differentiation is that they're model-provider-agnostic from a corporate alignment standpoint — you're not also handing your data strategy to Microsoft or Google's ecosystem. That's a real wedge for regulated-industry buyers who are genuinely scared of co-mingling. The scenario where this breaks: mid-market companies who think they want on-prem but actually need a managed service — they'll buy North, understaff the deployment, and blame Cohere when the RAG pipeline hallucinate-retrieves. The kill scenario in 12 months isn't a competitor — it's that AWS and Azure finish hardening their sovereign cloud offerings, and the "not a hyperscaler" positioning becomes "also not as good." What would have to be true for me to be wrong: regulated-industry procurement cycles are long enough that Cohere locks in enough logos before hyperscalers catch up, and the model quality gap closes faster than the distribution gap opens.”

“This is the first assistant play that actually has a coherent wedge: Perplexity's web-grounded answers are genuinely better than Google Assistant's stale knowledge base, and on-device actions close the gap that made Perplexity a tab-switcher instead of a daily driver. The scenario where this breaks is anything requiring deep calendar management, smart home ecosystems, or third-party app integrations beyond the basics — that's still a Siri/Google Assistant moat that takes years to erode. Prediction: Google ships a meaningfully better Gemini Assistant integration within 18 months and recaptures the Android default, but Perplexity survives as the power-user choice because their search quality creates real loyalty among people who've already switched.”

“The buyer is the CISO and the CTO jointly, and the budget comes from the enterprise software line item, not the AI experiment fund — that's a meaningful distinction because it means North is competing for budget that already exists. The moat here is genuine: on-prem deployment creates switching costs that are operational, not contractual, and compliance certifications that Cohere accumulates compound over time against new entrants. The pricing architecture is a classic enterprise land-and-expand play — contact sales means they're pricing to the value of data-residency compliance, not to model usage, which is the right call because a bank doesn't care what a token costs, they care what a data breach costs. The stress test: Cohere is still dependent on staying ahead of hyperscaler sovereign cloud offerings, and if their model quality plateaus relative to GPT or Gemini, enterprises will tolerate the data-residency trade-off less. The specific business decision that makes this viable is the on-prem option — that's not a feature, it's a separate market that the big API providers structurally cannot serve without cannibalizing their own cloud revenue.”

“The buyer here is a consumer on the free tier who converts to $20/month Pro, which means Perplexity is running a consumer subscription business on Android where Google controls the default assistant setting, the app store, and the OS update cycle — that's three choke points owned by the primary competitor. The moat question is brutal: Perplexity's answer quality is real, but Google can close that gap faster than Perplexity can build the integration depth that makes switching costs sticky. When Gemini's on-device actions reach parity in 12-18 months, the 'better answers' differential shrinks, and Perplexity is left competing on brand loyalty with a company that has a trillion-dollar distribution advantage. This earns a skip not because the product is bad, but because the unit economics of converting free Android users to $20/month subscribers against a free and pre-installed competitor is a math problem that doesn't work at scale without an enterprise or B2B story that isn't visible yet.”

“The job-to-be-done is "deploy enterprise AI without sending data to a third-party cloud" — that's coherent and real, but North tries to do that job AND be a RAG platform AND handle access controls AND serve as a compliance solution, and that's four jobs, not one. The onboarding for an enterprise platform like this isn't two minutes — it's a six-month procurement cycle, and I can't evaluate the actual product experience from what's publicly available, which is itself a signal that the product is incomplete or the team doesn't want it stress-tested publicly yet. The completeness problem: prebuilt RAG pipelines sound great until your documents are PDFs with scanned tables and your retrieval needs multi-hop reasoning, at which point "prebuilt" becomes "pre-broken." What would flip this to a ship is a credible technical sandbox where a platform engineer can actually test the RAG pipeline against their own document corpus before signing a contract — the absence of that path suggests North is a sales-led product, not a product-led one.”

“The job-to-be-done is clear and singular: replace the default Android assistant for people who find Google Assistant too shallow and Gemini too incomplete. Onboarding lives or dies on whether setting Perplexity as the default assistant is a three-tap flow or a settings-archaeology expedition — if it's the latter, the vast majority of potential users bounce before they ever see the value. The product earns its ship on persistent follow-up context, which is the one feature that actually changes behavior rather than just competing on answer quality; 'remember what we talked about last Tuesday' is the unlock that makes this an assistant rather than a fancier search box. The gap is third-party app depth — until 'order me an Uber to where I'm going on Friday' works end-to-end, power users will keep the old assistant as a backup, and dual-wielding is a skip signal.”

“The thesis here is that the phone assistant layer — long ceded to Google and Apple as untouchable defaults — becomes genuinely contestable once LLM answer quality exceeds the default assistant's by a wide enough margin that users tolerate the friction of switching. Perplexity is betting that web-grounded, citation-backed answers compound into a behavior change where people stop typing into search bars entirely and start talking to a context-aware agent that remembers the last three conversations. The second-order effect that matters: if persistent cross-session context actually works at scale, Perplexity becomes the place where intent accumulates — a dataset about what people are trying to do day-to-day that no search index currently captures. The dependency that has to hold is that Google doesn't flip Gemini Live into a true default on Pixel and Samsung devices before Perplexity builds enough habit; that clock is running, and Perplexity is on-time but not early to this trend.”